Comment 5 for bug 976159
Revision history for this message
|
|
#5 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Ah, well, bug 285787 was half of it. The other half is that when you try to mark a single package for upgrade when it has dependencies that will need upgraded that need other dependencies upgraded (basically a 2 or 3-deep "need upgraded" chain), APT will fail to upgrade the package and puts an error on its error stack.
The method that Muon uses to tell the QApt Worker which packages to commit uses a single-mark system for each of the packages being changed, which unfortunately uncovers this bug.
In the case of upgrades, the APT functions for marking upgrades resolve the dependency issues when we hit the upgrade button in Muon, so the other I updated the problem resolution for marking individual upgrades to match that of the APT upgrade functions. (Basically, if marking everything in the list of upgrades sent to the QApt worker resolves the problem manually, then delete the error of APT's error stack.