It's not really subprocess.Popen that is being called rather
DistUpgradeVteTerminal in DistUpgradeViewGtk or DistUpgradeViewGtk3
which launches a terminal and may not properly set the path.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
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 VogtFri, 14 Dec 2012 14:44:49 +0100
** Changed in: ubuntu-release-upgrader (Ubuntu)
** Branch linked: lp:ubuntu/raring-proposed/ubuntu-release-upgrader
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1085844
Title:
update-manager uses subprocess.Popen incorrectly when calling dpkg
T
I searched all update-manager and ubuntu-release-upgrader bug
attachments and descriptions for tracebacks with 'dpkg: no such file or
directory' and did not find any.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
** Branch linked: lp:ubuntu-release-upgrader
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1085844
Title:
update-manager uses subprocess.Popen incorrectly when calling dpkg
To manage notifications
** Package changed: update-manager (Ubuntu) => ubuntu-release-upgrader
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1085844
Title:
update-manager uses subprocess.Popen incorrectly when cal
** Changed in: update-manager (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1085844
Title:
update-manager uses subprocess.Popen incorrectly when calling dpkg
I didn't save any, sadly. It should be fairly easy to test -- include a
package that calls exit 1 in its postinst during an distribution upgrade
ran by update-manager, and you should hit that block.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I found one instance in DistUpgradeController.py:
# installing the packages failed, can't be retried
cmd = ["dpkg","--configure","-a"]
if os.environ.get("DEBIAN_FRONTEND") == "noninteractive":
cmd.append("--force-confold")
Could you provide one of these tracebacks?
** Changed in: update-manager (Ubuntu)
Importance: Undecided => High
** Tags added: quantal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1085844
Title:
10 matches
Mail list logo
