[Bug 1085844] Re: update-manager uses subprocess.Popen incorrectly when calling dpkg

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-release-upgrader - 1:0.192.3

---------------
ubuntu-release-upgrader (1:0.192.3) raring; urgency=low

  * fix FTBFS if there are no __pycache__ dirs
 -- Michael Vogt <michael.vogt at ubuntu.com>   Fri, 14 Dec 2012 14:44:49 +0100

** Changed in: ubuntu-release-upgrader (Ubuntu)
       Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubuntu-release-upgrader in
Ubuntu.
https://bugs.launchpad.net/bugs/1085844

Title:
  update-manager uses subprocess.Popen incorrectly when calling dpkg

Status in “ubuntu-release-upgrader” package in Ubuntu:
  Fix Released

Bug description:
  While upgrading a machine from Precise to Quantal, I had the upgrade
  bomb out at the end with initramfs-tools postinst exiting 1. This was
  handled nicely, in my opinion, with update-manager explaining the
  issue and saying it will run 'dpkg --configure -a'. However, when it
  does this, it does not give the full path to subprocess.Popen(), so
  Python gives a few tracebacks with "dpkg: no such file or directory"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1085844/+subscriptions