FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/pyt...@freebsd.org.html Port| Current version | New version +-+ audio/py-mutagen| 1.31| 1.32 +-+ devel/py-setuptools | 20.0| 21.0.0 +-+ devel/py-setuptools27 | 20.0| 21.0.0 +-+ devel/py-setuptools33 | 20.0| 21.0.0 +-+ devel/py-setuptools34 | 20.0| 21.0.0 +-+ devel/py-setuptools35 | 20.0| 21.0.0 +-+ www/py-django | 1.8.7 | 1.9.6 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. ___ freebsd-python@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-python To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
Re: pypi URL schema change
Roman Bogorodskiy wrote:
> Hi,
>
> Recently pypi has changed its URL schema for distfiles. Specifically,
> it was:
>
> /packages/{python version}/{name[0]}/{name}/{filename}
>
> and now it is:
>
> /packages/{hash[:2]}/{hash[2:4]}/{hash[4:]}/{filename} Where hash is
> blake2b(file_content, digest_size=32).hexdigest().lower()
>
> (copy/pasted from [1]).
>
> That means that if you have MASTER_SITES= CHEESESHOP it won't be able to
> fetch newer packages (however, it looks like it's still fine for the
> previously uploaded packages).
>
> As per [1], there's a fix applied on pypi.io that supports the old
> schema by redirection to a proper URL. However, it looks like fetch(1)
> is not quite happy about such a direct:
>
> => Attempting to fetch
> https://pypi.io/packages/source/p/positional/positional-1.1.0.tar.gz
> fetch:
> https://pypi.io/packages/source/p/positional/positional-1.1.0.tar.gz:
> Temporary Redirect
^^^
In additional to that, it looks like a bug in fetch(1) to me that I've
tried to address here:
https://reviews.freebsd.org/D6167
> => Attempting to fetch
> http://distcache.FreeBSD.org/ports-distfiles/positional-1.1.0.tar.gz
> fetch:
> http://distcache.FreeBSD.org/ports-distfiles/positional-1.1.0.tar.gz:
> Not Found
>
> For now I have to redefine SUBDIR manually with the hash, e.g.:
>
> MASTER_SITES= CHEESESHOP
> MASTER_SITE_SUBDIR=
> bf/a8/bc656a556a60b76c32830b57279f51714ab7c6366fd243d6ea86b6fcad46
>
> However, it feels a little awkward to keep a long hash like that in the
> Makefile.
>
> Any thoughts if there's a way to avoid that?
>
> 1:
> https://bitbucket.org/pypa/pypi/issues/438/backwards-compatible-un-hashed-package
>
> Roman Bogorodskiy
Roman Bogorodskiy
___
freebsd-python@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-python
To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
[Bug 209204] Changing default Python version unduly difficult
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209204 David Naylor changed: What|Removed |Added Status|New |In Progress CC||d...@freebsd.org --- Comment #3 from David Naylor --- The build logs would allow us to have a better understanding of what the problem is. In this particular case I suspect a warning message in the build logs would give a clue as to the solution. Also, I am able to reproduce the problem on my system: # cd /usr/ports/textproc/py-pygments # make -V PYTHON_VER 2.7 # make -V PYTHON_VER DEFAULT_VERSIONS=python=3.5 2.7 # make -V WARNING "Your requested default python version 3.5 is different from the installed default python interpreter version 2.7" The above warning is what should appear in your build logs. If not we can address that. The issue is you have already installed lang/python (i.e. the default) as version 2.7. This means your system is "hard-coded" to use python-2.7 as the default until you uninstall all ports that depend on lang/python, inclusive, and rebuild them all with the new default. The effect of "default" is stronger than what the word implies, it is more akin to choosing i386 and amd64 at install time. Once you have chosen it, that's it. Until you undo and redo. In other words, the choice of default is persistent and cannot be changed, only undone. I hope this clarifies the issue. -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-python@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-python To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
[Bug 209204] Changing default Python version unduly difficult
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209204 David Naylor changed: What|Removed |Added Assignee|port...@freebsd.org |d...@freebsd.org -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-python@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-python To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
