[Bug 205619] databases/pyspatialite: Unbreak and make fetchable again
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Sat Dec 26 09:11:01 UTC 2015
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205619
Bug ID: 205619
Summary: databases/pyspatialite: Unbreak and make fetchable
again
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: Individual Port(s)
Assignee: freebsd-ports-bugs at FreeBSD.org
Reporter: rhurlin at gwdg.de
CC: coder at tuxfamily.org
CC: coder at tuxfamily.org
Flags: maintainer-feedback?(coder at tuxfamily.org)
Created attachment 164658
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=164658&action=edit
patch for 3.0.1-alpha-0 to unbreak and make fetchable
For some days now, databases/spatialite is marked BROKEN, because it is not
able to fetch the distfile any more.
Looking for the reason, I found, that there is a small variation between, what
Mk/bsd.sites.mk wants and what the original website[1] has.
With the definition of the MASTERSITE from Mk/bsd.sites.mk via CHEESESHOP, the
port wants to fetch from here:
fetch
https://pypi.python.org/packages/source/p/pyspatialite-3.0.1-alpha/pyspatialite-3.0.1-alpha-0.tar.gz
The sources have a slightly different path (without '-3.0.1-alpha'):
https://pypi.python.org/packages/source/p/pyspatialite/pyspatialite-3.0.1-alpha-0.tar.gz
The problem seems to be, that CHEESESHOP uses DISTNAME also for building the
path, and DISTNAME is not needed in the first part, only something like
PORTNAME. The latest change to Mk/bsd.sites.mk[2] seems to be relevant:
CHEESESHOP:source/${DISTNAME:C/(.).*/\1/}/${DISTNAME:C/(.*)-[0-9].*/\1/}
Because I don't know and do not have the skills to check, if CHEESEPORT can be
corrected in a more general way, I made a patch only for databases/pyspatialite
and only for 'https://' to get it fetching again.
[1] https://pypi.python.org/pypi/pyspatialite/3.0.1-alpha-0
[2] http://svnweb.freebsd.org/changeset/ports/400105
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list