Override "Phasing" When Crash Reporter Complains About Obsolete Packages
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| update-manager (Ubuntu) |
Triaged
|
Medium
|
Unassigned | ||
| Trusty |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
In Saucy 13.10, updates are being phased (http://
Unfortunately, this behaviour often conflicts with the Crash Reporter.
For example. Gitg crashed on me yesterday and I was given this error:
UnreportableR
You have some obsolete package versions installed. Please upgrade the following packages and check if the problem still occurs:
libavahi-
Naturally, I launched `update-manager` to fix the issue.
* Expected: Packages are available as stated by Crash Reporter
* Actual: Packages are not there, confusing the heck out of me...
Suggestion:
Crash reporter and update-manager should interact; turn off phasing until the obsolete package error is resolved.
Thank you for your consideration.
| Changed in update-manager (Ubuntu): | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| Brian Murray (brian-murray) wrote | #1 |
| Changed in update-manager (Ubuntu Trusty): | |
| milestone: | none → trusty-updates |
| Changed in update-manager (Ubuntu): | |
| milestone: | trusty-updates → none |
| tags: | added: rls-w-incoming |
This should actually be changed in apport and it should offer to install binary packages (if they are installed and from the source package in which the crash occurred) which are undergoing phasing on the system that encountered a crash.