Avoid symbol conflicts with `md5_*' symbols in third party extensions
Bug #1734109 reported by
Matthias Klose
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python2.7 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Zesty |
Fix Committed
|
Undecided
|
Unassigned | ||
Artful |
Fix Released
|
Undecided
|
Unassigned |
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 post a comment you must log in.
the change is already in artful and bionic