[Bug 1085844] [NEW] update-manager uses subprocess.Popen incorrectly when calling dpkg
Steve Kowalik
stevenk at debian.org
Mon Dec 3 09:59:25 UTC 2012
Public bug reported:
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"
** Affects: update-manager (Ubuntu)
Importance: Undecided
Status: New
** Tags: dist-upgrade
** Tags added: dist-upgrade
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to update-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1085844
Title:
update-manager uses subprocess.Popen incorrectly when calling dpkg
Status in “update-manager” package in Ubuntu:
New
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/update-manager/+bug/1085844/+subscriptions
More information about the foundations-bugs
mailing list