[Bug 216953] devel/py-setuptools: egg_info fails under python 3.4.6 on nonexistent MANIFEST graft
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216953 Kubilay Kocak changed: What|Removed |Added Depends on||217044 Referenced Bugs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217044 [Bug 217044] devel/py-setuptools: Upgrade to 34.1.1 -- You are receiving this mail because: You are the assignee 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 217044] devel/py-setuptools: Upgrade to 34.1.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217044 Kubilay Kocak changed: What|Removed |Added Blocks||216953 --- Comment #16 from Kubilay Kocak --- For what it's worth, and albeit belatedly, I'm strongly -1 on using ensurepip to boostrap instead of the setuptools/pip ports for the same and additional reasons as John someone captures in comment 3 and comment 3. Namely: - static versions - per python port (currently 4, but at best 3 (the number of concurrently supported upstream bugfix branches at any one time) - that receive no bugfixes (unless we backport them) and - unless they are manually hacked/updated in the pythonXY ports by ourselves Instead I would have the pythonXY ports depend on the setuptools/pip ports so that they are guaranteed to be provided in a new installation (as PEP453 [1] recommends): "Ensure that whenever Python is installed pip is either installed or is otherwise made readily available to end users. " It appears that the only requirement here is that setuptools/pip is guaranteed to be available for the framework (USES=wheel or otherwise) to use. There is no apparent or explicitly mentioned requirement for that to happen via the private/vendored setuptools/pip (ensurepip) module. Further, having the framework utilise one version of setuptools/pip and other parts of a users environment (site-packages and/or virtual environments) potentially or actually use another is a major issue. Addressing that issue by manually upgrading private/vendored copies of pip/setuptools in lang/pythonXY ports with patches or framework in-place upgrades is also likely to cause issues. It also means multiple (one per python port) combinations of setuptools/pip to maintain, bug check, test and upgrade than one. Finally, setuptools/pip (the upstream separate PyPI packages) are intended to support all currently supported Python branches at once within the same version, and breakages are considered bugs/regressions. We should leverage that level of support by using them. [1] https://www.python.org/dev/peps/pep-0453/ Referenced Bugs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216953 [Bug 216953] devel/py-setuptools: egg_info fails under python 3.4.6 on nonexistent MANIFEST graft -- You are receiving this mail because: You are the assignee 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 217044] devel/py-setuptools: Upgrade to 34.1.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217044 --- Comment #17 from Kubilay Kocak --- Additionally, related to the removal of python33, id like that to be created as a blocking issue, so it can be dealt with and land separately (before this issue) so as to allow for announcing its removal (along with 3.4) as part of a new python policy (yet to propose) to only support those Python versions that upstream supports with bugfix/security backports/merges. Currently and for a long time this means 2.7 + 3.latest + 3.latest-1. I'm happy to create the issue for this, write up the (short) proposal, announce to list/users and take care of the removal of these ports in accordance with it. -- You are receiving this mail because: You are the assignee 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 217044] devel/py-setuptools: Upgrade to 34.1.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217044 --- Comment #18 from Martin Wilke --- Hi, Actually I was about to commit that wheel framework to ports the other day, but decided to keep it on hold, for 2 reasons, 1) flavors will enter the ports tree very soon, which will solve many problems in particular with multiple concurrent py versions which means bigger changes to the python framework is needed. 2) I agree with John that bundled pip/setuptools might be a step backwards in terms of security because if pip or setuptools got a security problem we will have to wait till pythonxX catches up on that. Which is most likely a bad idea. That all said I think it's better to wait till flavors enters the portstree and address this issue together with the needed changes to the python framework. - Martin -- You are receiving this mail because: You are the assignee 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 217974] sysutils/rdiff-backup: Limit to building with Python 2.x
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217974 Daniel Ylitalo changed: What|Removed |Added Flags|maintainer-feedback?(daniel |maintainer-feedback+ |@blodan.se) | -- 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"
maintainer-feedback requested: [Bug 218838] lang/pypy: is lang/pypy and lang/pypy3 in conflict?
Yunchih Chen has reassigned Bugzilla Automation 's request for maintainer-feedback to FreeBSD Python : Bug 218838: lang/pypy: is lang/pypy and lang/pypy3 in conflict? https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218838 --- Description --- I have a custom meta package that depends on both lang/pypy and lang/pypy3. After updating port tree to r438820, the build fails with the following messages: ===> local-217-2017.04.21 depends on package: pypy>=a - not found ===> Installing existing package /packages/All/pypy-5.7.1_1.txz [freebsd10-default-workstation-job-01] Installing pypy-5.7.1_1... [freebsd10-default-workstation-job-01] Extracting pypy-5.7.1_1: .. done ===> local-217-2017.04.21 depends on package: pypy>=a - found ===> Returning to build of local-217-2017.04.21 ===> local-217-2017.04.21 depends on package: pypy3>=a - not found ===> Installing existing package /packages/All/pypy3-5.7.1_1.txz [freebsd10-default-workstation-job-01] Installing pypy3-5.7.1_1... pkg-static: pypy3-5.7.1_1 conflicts with pypy-5.7.1_1 (installs files into the same place). Problematic file: /usr/local/pypy-5.7/LICENSE Failed to install the following 1 package(s): /packages/All/pypy3-5.7.1_1.txz *** Error code 70 It turns out that the %%PYPY_DIR%% variable in lang/pypy and lang/pypy3 both resolve to /usr/local/pypy-5.7/. Relevant commit: r438095 that might cause this: The DISTVERSION in Makefile is modified as lang/pypy: 5.6.0 --> 5.7.1 lang/pypy3: 5.5.0-alpha --> 5.7.1 ___ 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 218838] lang/pypy: is lang/pypy and lang/pypy3 in conflict?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218838 Bug ID: 218838 Summary: lang/pypy: is lang/pypy and lang/pypy3 in conflict? Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: pyt...@freebsd.org Reporter: yunc...@csie.ntu.edu.tw Flags: maintainer-feedback?(pyt...@freebsd.org) Assignee: pyt...@freebsd.org I have a custom meta package that depends on both lang/pypy and lang/pypy3. After updating port tree to r438820, the build fails with the following messages: ===> local-217-2017.04.21 depends on package: pypy>=a - not found ===> Installing existing package /packages/All/pypy-5.7.1_1.txz [freebsd10-default-workstation-job-01] Installing pypy-5.7.1_1... [freebsd10-default-workstation-job-01] Extracting pypy-5.7.1_1: .. done ===> local-217-2017.04.21 depends on package: pypy>=a - found ===> Returning to build of local-217-2017.04.21 ===> local-217-2017.04.21 depends on package: pypy3>=a - not found ===> Installing existing package /packages/All/pypy3-5.7.1_1.txz [freebsd10-default-workstation-job-01] Installing pypy3-5.7.1_1... pkg-static: pypy3-5.7.1_1 conflicts with pypy-5.7.1_1 (installs files into the same place). Problematic file: /usr/local/pypy-5.7/LICENSE Failed to install the following 1 package(s): /packages/All/pypy3-5.7.1_1.txz *** Error code 70 It turns out that the %%PYPY_DIR%% variable in lang/pypy and lang/pypy3 both resolve to /usr/local/pypy-5.7/. Relevant commit: r438095 that might cause this: The DISTVERSION in Makefile is modified as lang/pypy: 5.6.0 --> 5.7.1 lang/pypy3: 5.5.0-alpha --> 5.7.1 -- You are receiving this mail because: You are the assignee 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 217703] lang/python36: Remove BROKEN_SSL for openssl-devel
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217703 --- Comment #2 from Melvyn Sopacua --- 3.6.1 is currently the only official release that builds and works correctly (EC certs broken in 3.6.0 and 3.5-) with OpenSSL 1.1.0. For details see bpo 29697 [1]. Don't have the time to dink around with poudriere, but I'll attach build log and patch shortly. [1] http://bugs.python.org/issue29697 -- You are receiving this mail because: You are the assignee 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 217703] lang/python36: Remove BROKEN_SSL for openssl-devel
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217703 --- Comment #3 from Melvyn Sopacua --- Created attachment 182043 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=182043&action=edit Fix port -- You are receiving this mail because: You are the assignee 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 217703] lang/python36: Remove BROKEN_SSL for openssl-devel
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217703 --- Comment #4 from Melvyn Sopacua --- Created attachment 182044 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=182044&action=edit Buildlog -- You are receiving this mail because: You are the assignee 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"
