Up to [cvs.NetBSD.org] / pkgsrc / lang / python26
Request diff between arbitrary revisions
Keyword substitution: kv
Default branch: MAIN
Removing python26. EOL'd quite some ago and discussed a couple times on tech-pkg@ and pkgsrc-users@.
Pullup ticket #4256 - requested by spz lang/python26: security update Revisions pulled up: - lang/python26/Makefile 1.56 - lang/python26/PLIST.common 1.15 - lang/python26/buildlink3.mk 1.6 - lang/python26/dist.mk 1.4 - lang/python26/distinfo 1.52 - lang/python26/patches/patch-CVE-2013-4238 deleted - lang/python26/patches/patch-al 1.12 --- Module Name: pkgsrc Committed By: adam Date: Wed Nov 6 07:25:49 UTC 2013 Modified Files: pkgsrc/lang/python26: Makefile PLIST.common buildlink3.mk dist.mk distinfo pkgsrc/lang/python26/patches: patch-al Removed Files: pkgsrc/lang/python26/patches: patch-CVE-2013-4238 Log Message: Python 2.6.9 is a security-fix source-only release for Python 2.6.8, fixing several reported security issues: issue 16037, issue 16038, issue 16039, issue 16040, issue 16041, and issue 16042 (CVE-2013-1752, long lines consuming too much memory), as well as issue 14984 (security enforcement on $HOME/.netrc files), issue 16248 (code execution vulnerability in tkinter), and issue 18709 (CVE-2013-4238, SSL module handling of NULL bytes inside subjectAltName).
Python 2.6.9 is a security-fix source-only release for Python 2.6.8, fixing several reported security issues: issue 16037, issue 16038, issue 16039, issue 16040, issue 16041, and issue 16042 (CVE-2013-1752, long lines consuming too much memory), as well as issue 14984 (security enforcement on $HOME/.netrc files), issue 16248 (code execution vulnerability in tkinter), and issue 18709 (CVE-2013-4238, SSL module handling of NULL bytes inside subjectAltName).
Set BUILDLINK_ABI_DEPENDS correctly (with +=, not ?=) It turns out there were a lot of these.
recursive bump from gettext-lib shlib bump.
comment out BUILDLINK_INCDIRS/BUILDLINK_LIBDIRS/BUILDLINK_TRANSFORM definitions which do things behind the client pkgs back, in particular manipulate the library search path It is well possible that this causes some fallout, but I hope it will be small and can be dealt with on a per-pkg basis. (partly) suggested by Mark Davies on tech-pkg
bump PKGREVs for Python pkgs, as suggested by David Sainty -- at least on Linux one can't build some extensions against an old Python (with spurious -ldb4 linkage) anymore also sync the bl3 files of the non-default versions with python25 for consistency
Initial import of python26-2.6.2. Compiles, installs, and runs on NetBSD-5.99.10/amd64; no further tests done. Please test and fix on your platform! What's new in Python-2.6: The major theme of Python 2.6 is preparing the migration path to Python 3.0, a major redesign of the language. Whenever possible, Python 2.6 incorporates new features and syntax from 3.0 while remaining compatible with existing code by not removing older features or syntax. When it tries to do what it can, adding compatibility functions in a future_builtins module and a -3 switch to warn about usages that will become unsupported in 3.0. Some significant new packages have been added to the standard library, such as the multiprocessing and json modules, but there aren way. Python 2.6 also sees a number of improvements and bugfixes throughout the source. A search through the change logs finds there were 259 patches applied and 612 bugs fixed between Python 2.5 and 2.6. Both figures are likely to be underestimates. More details at http://docs.python.org/whatsnew/2.6.html
Initial revision