I tried many times with different scenarios, and I've never been able to
reproduce this in a schroot or manually upgrading in an up-to-date
precise VM. Until now, the referenced upgrade tests were run on a rather
outdated precise VM (from May 2013, 12.04.2), and I refreshed it now.
The upgrade test succeeds now.
Also, precise has python 2.7.3-0ubuntu2 which is >= 2.7.1-0ubuntu2, so
even if python does not get upgraded until later it ought to suffice. So
if anything, we need to backport said apt commit, but until we have some
stronger evidence that it is actually required and causes real upgrade
failures I'll close this bug.
** Changed in: ubuntu-release-upgrader (Ubuntu Trusty)
Status: Triaged => Invalid
** Changed in: apt (Ubuntu Precise)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1271237
Title:
precise → trusty upgrade: packages fail due to python:any dependency
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1271237/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
