Hello Matthias, or anyone else affected, Accepted python2.7 into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/python2.7/2.7.13-2ubuntu0.2 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-zesty to verification-done-zesty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-zesty. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: python2.7 (Ubuntu Zesty) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1734109 Title: Avoid symbol conflicts with `md5_*' symbols in third party extensions Status in python2.7 package in Ubuntu: Fix Released Status in python2.7 source package in Xenial: New Status in python2.7 source package in Zesty: Fix Committed Status in python2.7 source package in Artful: Fix Released Bug description: SRU We link most extensions as built-ins into the python binary. the md5_* symbols cause a conflict with external libs/extensions. So just use the _Py-* namespace for these. See the Debian report for details. These are internal functions for the md5 module. Renaming them to the _Py_* namespace avoids the conflict. There should not be any case where these are intentionally referenced. At least in the archive there are no known references, so the regression potential is limited to external binaries, and there it should be minimal to non-existing as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1734109/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp