FreeBSD ports tree https://cgit-dev.freebsd.org/ports/atom?h=2014Q3 2014-04-22T12:14:26Z 2014-04-22T12:14:26Z Kubilay Kocak koobs@FreeBSD.org 2014-04-22T12:14:26Z urn:sha1:aab3da8d2a0a8217ca1350b9d140834e2c7ed0ad Copy the second part of a change previously made to python27 [1], to python31, python32 and python33. This fixes staging and packaging of these ports by a non-root user by running ranlib on the archive prior to it being installed read-only. While I'm here: - python27: Add breadcrumbs and references to the patch header - python34: Update breadcrumbs and references to the patch header [1] https://svnweb.freebsd.org/ports?view=revision&revision=350207 Submitted by: antoine Reviewed by: kwm, sbz 2014-04-20T01:35:39Z Kubilay Kocak koobs@FreeBSD.org 2014-04-20T01:35:39Z urn:sha1:21c7eb29520ac1b037a61fad06cc3f6deb9d8fec Copy change committed to python27 [1] to python31, python32 and python33 to fix builds of some extensions with Clang 3.4. Also add breadcrumbs to the patch header in lang/python27 referencing the upstream issue. [2] The Python 3.4 port (lang/python34) already carries the patch. [1] https://svnweb.freebsd.org/ports?view=revision&revision=346428 [2] http://bugs.python.org/issue20767 2014-04-05T09:04:28Z Antoine Brodin antoine@FreeBSD.org 2014-04-05T09:04:28Z urn:sha1:7acf693fdfb55ef9133e1cf848f5b181785c51ad - pycompile only once, previously it would pycompile 3 imported modules (getopt, struct and py_compile) and make them read-only, and later try to pycompile them again and fail - ranlib before installing archive read-only With hat: portmgr 2014-03-01T14:10:13Z Antoine Brodin antoine@FreeBSD.org 2014-03-01T14:10:13Z urn:sha1:8376e278628c3123e4635346d5c06d15e01353e9 the patch was obtained from upstream (issue #20374) - Add missing USES=readline PR: ports/187174 Reported by: O. Hartmann Reviewed by: koobs Obtained from: python 2014-03-01T10:52:55Z Kubilay Kocak koobs@FreeBSD.org 2014-03-01T10:52:55Z urn:sha1:7a2c2ce6e780ec6a01f1de55c980810b9175edce A vulnerability was reported [1] in Python's socket module, due to a boundary error within the sock_recvfrom_into() function, which could be exploited to cause a buffer overflow. This could be used to crash a Python application that uses the socket.recvfrom_info() function or, possibly, execute arbitrary code with the permissions of the user running vulnerable Python code. This vulnerable function, socket.recvfrom_into(), was introduced in Python 2.5. Earlier versions are not affected by this flaw. This is fixed in upstream branches for version 2.7, 3.1, 3.2 and 3.3. [1] http://bugs.python.org/issue20246 MFH: 2014Q1 Security: 8e5e6d42-a0fa-11e3-b09a-080027f2d077 2014-02-28T03:04:19Z Sean Bruno sbruno@FreeBSD.org 2014-02-28T03:04:19Z urn:sha1:6de6c75db37892a8544085b70b4f3c3e357b4548 now disallowing the use of -R. Submitted by: antoine Reviewed by: gjb 2013-12-08T06:22:07Z Kubilay Kocak koobs@FreeBSD.org 2013-12-08T06:22:07Z urn:sha1:d536d1d88b8a10edd67366a4f34510a67d906962 The current FreeBSD/ARM __clear_cache() implementation does nothing #if __i386__ || __x86_64__ #else abort(); cognet@ advises this is an issue for anything !Apple that is using the libcompiler_rt provided by Clang on ARM, and requires upstreaming. This is the root cause of abort() on import for the ctypes module in Python, as they bundle libffi. [1] This change patches the bundled libffi library in all Python ports, even though it is a NOOP for the ports that use devel/libffi. These ports, currently python31, will get the fix via ports/184517 A huge shout out to cognet@ who helped diagnose the issue and created the patch to address it. Thank you! PR: ports/149167 [1] PR: ports/184517 Submitted by: cognet [3] Reviewed by: cognet, eadler, milki, ak 2013-12-05T13:33:17Z Kubilay Kocak koobs@FreeBSD.org 2013-12-05T13:33:17Z urn:sha1:a8610b8d32a91a7ad0296869dd48b3938f5f1730 lang/python26, lang/python27 and lang/python31 now add ac_cv_opt_olimit_ok=no to CONFIGURE_ENV to disable functionality that was removed in Python 3.2+ [1] Pending a backport of the commit [2] to 2.7, we can now remove the locally maintained patch to configure that disabled the functionality when CC = clang. Apart from being narrower in scope than ac_cv_opt_olimit_ok=no, the patch doesn't work for FreeBSD versions where clang *is* cc (eg: 10.0+) [1] http://hg.python.org/lookup/r85656 [2] http://bugs.python.org/issue877121 Reviewed by: antoine 2013-11-24T13:22:40Z Kubilay Kocak koobs@FreeBSD.org 2013-11-24T13:22:40Z urn:sha1:9c597eecc629439b2e1629f5d35707330bbe0ac5 - Update to 2.7.6 - Update pkg-plist - Temporarily override OPT:Olimit using CONFIGURE_ENV (ports/182952) [1] - Replace patch: extra-patch-configure-pth with CONFIGURE_ENV instead - Remove patch: patch-Modules-_ctypes-libffi_fficonfig.py.in [2] - QA: Clean up and group related USE_*, WRKSRC and CONFIGURE entries - QA: Whitespace alignment Changes: 2.7.6 - November 10, 2013 http://www.python.org/download/releases/2.7.6/ [1] Python removed OPT:Olimit in 3.2+, requested backport or alternative upstream patch: http://bugs.python.org/issue877121 [2] Upstreamed: http://bugs.python.org/issue18178 PR: ports/182952 PR: ports/156759 Reviewed by: antoine, mva 2013-11-13T09:42:04Z William Grzybowski wg@FreeBSD.org 2013-11-13T09:42:04Z urn:sha1:f451bf37d7e103f58ef22ca50b3c1da05c7b19d3 PR: ports/183884