[Bug 1591895] Re: SRU: backport python 2.7.12 to 16.04 LTS

[Łukasz Zemczak]

Hello Matthias, or anyone else affected,

Accepted python-defaults into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/python-
defaults/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 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: python-defaults (Ubuntu Xenial)
       Status: New => Fix Committed

-- 
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/1591895

Title:
  SRU: backport python 2.7.12 to 16.04 LTS

Status in python-defaults package in Ubuntu:
  Fix Released
Status in python-stdlib-extensions package in Ubuntu:
  Fix Released
Status in python2.7 package in Ubuntu:
  Fix Released
Status in python-defaults source package in Xenial:
  Fix Committed
Status in python-stdlib-extensions source package in Xenial:
  Fix Committed
Status in python2.7 source package in Xenial:
  Fix Released
Status in python-defaults source package in Zesty:
  New

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1591895/+subscriptions