Ubuntu
ubuntu-release-upgrader package

possible for some do-release-upgrade crashes to be unreportable

Bug #1067542 reported by Brian Murray
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
ubuntu-release-upgrader (Ubuntu)
Fix Released
High
Unassigned

Bug Description

Depending on when ubuntu-release-upgrader crashes it is possible for the bug to be unreportable because apport determines that the package is not an official package. This can happen if sources have been updated to the next release, e.g. quantal, and then ubuntu-release-upgrader crashes. I saw this in http://paste.ubuntu.com/1275147/. There we can see:

Package: update-manager-core 1:0.156.14.11
UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again.

I believe setting the environmental variable APPORT_DISABLE_DISTRO_CHECK would allow the bug to be reported. However, its odd that this is the first time this has been encountered / reported afaik.

Tags: quantal
Brian Murray (brian-murray)
Changed in ubuntu-release-upgrader (Ubuntu):
importance: Undecided → High
tags: added: quantal
Revision history for this message
Brian Murray (brian-murray) wrote :

If you look at all the ubuntu-release-upgrader apport-crash reports they are all about do-partial-upgrade which would be from systems already running 12.10.

Revision history for this message
Brian Murray (brian-murray) wrote :

And looking at all the apport-crash tagged update-manager bug reports all the ones with do-release-upgrade in the title are really about check-new-release so it certainly seems like this hasn't worked recently.

Brian Murray (brian-murray)
Changed in ubuntu-release-upgrader (Ubuntu):
status: New → Triaged
Revision history for this message
Martin Pitt (pitti) wrote :

The easiest way to work around the distro check is to add this to the package hook:

  self['CrashDB'] = 'ubuntu'

On IRC you also asked about "apport-bug ubuntu-release-upgrader". As this is not a (binary) package name, this won't work. If this is desired, apport-symptoms should get a new symptom with that name (and perhaps a few aliases like "release-upgrade" and "upgrade" while we are at it) which simply redirects the report to "ubuntu-release-upgrader-core"; see /usr/share/doc/apport/symptoms.txt .

Revision history for this message
Brian Murray (brian-murray) wrote :

The package hook is not installed yet when you are upgrading from precise to quantal as ubuntu-release-upgrader-core first appeared in quantal and you are just running the distribution upgrade from the dist-upgrader tarball.

However, this would work for upgrades from quantal to raring.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ubuntu-release-upgrader - 1:0.192.4

---------------
ubuntu-release-upgrader (1:0.192.4) raring; urgency=low

  * Ensure that partial upgrades are fully translated (LP: #1072828) thanks to
    Gabor Kelemen for the initial patch.
  * Remove code enabling apport since it is always running (LP: #1068874)
  * check-new-release-gtk: set the correct translation domain thanks to Gabor
    Kelemen for patch (LP: #1093697)
  * DistUpgradeController.py: call apport-bug with the binary package name not
    the source package name (LP: #1098001)
  * source_ubuntu-release-upgrader.py: set the crash database to Ubuntu to
    allow reporting of bugs even if the package does not seem to be official
    (LP: #1067542)
 -- Brian Murray <email address hidden> Fri, 11 Jan 2013 16:19:26 -0800

Changed in ubuntu-release-upgrader (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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