SRU: backport python 2.7.12 to 16.04 LTS
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-defaults (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Zesty |
New
|
Undecided
|
Unassigned | ||
python-stdlib-extensions (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
python2.7 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
SRU: backport python 2.7.12 to 16.04 LTS
The idea is to ship a released version with the first point release of 16.04 LTS. We updated python2.7 from the the 2.7 branch up to the final 2.7.12 release, and then made a test rebuild of the archive using the new python2.7 (and some other toolchain packages).
The test rebuild was done using the release candidate of 2.7.12, however the only changes between the rc and the final release are Windows related, and include one change in the idle lib. From my point of view we don't need another test rebuild.
The evaluation of the test rebuild is found in LP: #1586673. I'm pretty sure that none of the possible regressions can be attributed to the python2.7 update.
description: | updated |
no longer affects: | python2.7 (Ubuntu Zesty) |
Changed in python-defaults (Ubuntu): | |
status: | New → Fix Released |
Changed in python-stdlib-extensions (Ubuntu): | |
status: | New → Fix Released |
no longer affects: | python-stdlib-extensions (Ubuntu Zesty) |
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- 1~16.04 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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed. 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/ PerformingSRUVe rification . Thank you in advance!