Override "Phasing" When Crash Reporter Complains About Obsolete Packages

Bug #1257784 reported by Dac Chartrand
This bug affects 1 person
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)

Bug Description

In Saucy 13.10, updates are being phased (http://www.murraytwins.com/blog/?p=127 )

Unfortunately, this behaviour often conflicts with the Crash Reporter.

For example. Gitg crashed on me yesterday and I was given this error:

    You have some obsolete package versions installed. Please upgrade the following packages and check if the problem still occurs:
    libavahi-client3, libavahi-common-data, libavahi-common3

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...

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
Revision history for this message
Brian Murray (brian-murray) wrote :

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.

Changed in update-manager (Ubuntu Trusty):
milestone: none → trusty-updates
Mathew Hodson (mhodson)
Changed in update-manager (Ubuntu):
milestone: trusty-updates → none
tags: added: rls-w-incoming
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.