touch-packages team mailing list archive

[Matthias Klose <doko@xxxxxxxxxx>]

it looks like LP: #1326707 is the only Python3 related issue in
ubiquity, but not backported to trusty, although python 3.4 is the
default.

I'm attaching a backport for it. How could we test this changed ubiquity
on the image?


** Patch added: "ubiquity.diff"
   https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1348954/+attachment/4435073/+files/ubiquity.diff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/1348954

Title:
  update Python3 for trusty

Status in python3-defaults package in Ubuntu:
  Confirmed
Status in python3-stdlib-extensions package in Ubuntu:
  Confirmed
Status in python3.4 package in Ubuntu:
  Confirmed
Status in python3-defaults source package in Trusty:
  Confirmed
Status in python3-stdlib-extensions source package in Trusty:
  Confirmed
Status in python3.4 source package in Trusty:
  Fix Committed
Status in ubiquity source package in Trusty:
  New

Bug description:
  update Python3 for trusty.

  Rationale: the LTS was released with 3.4.0, the first 3.4 release
  which certainly had some issues. The idea is to update the python3.4
  packages to the version found in 15.04 (vivid), which currently
  doesn't have any outstanding issues.  A test rebuild of the trusty
  main component was done without showing any regressions during the
  package builds.

  http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20150317-trusty.html
  http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20150501-updates-trusty.html

  To validate this SRU, I'm proposing to use the results from the test
  rebuild, plus evaluating the testsuite results of the python3.4
  package itself.

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