[Bug 1734109] Re: Avoid symbol conflicts with `md5_*' symbols in third party extensions

[Łukasz Zemczak]

Hello Matthias, or anyone else affected,

Accepted python2.7 into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/python2.7/2.7.12-1ubuntu0~16.04.3
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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. 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 Xenial)
       Status: New => Fix Committed

** Tags added: verification-needed-xenial

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, 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:
  Fix Committed
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