people report bugs about update-manager thinking it still does dist upgrades

Bug #1071057 reported by Brian Murray
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Fix Released
Medium
Brian Murray
Quantal
Won't Fix
Medium
Unassigned
Saucy
Fix Released
Medium
Brian Murray

Bug Description

[Test Case]
1) Run ubuntu-bug update-manager (do not submit the bug report)

With the version of update-manager from -proposed you'll be asked if the issue you are reporting is one you encountered upgrading from one release of ubuntu to another. If you click Yes you'll be presented with an apport dialog regarding ubuntu-release-upgrader, if you click No you'll be presented with an apport dialog regarding update-manager.

[Regression Potential]
This only affects the apport hook for update-manager so very little.

I've seen a couple of cases where people using quantal have reported bugs about update-manager, regarding the distribution upgrade process they just went through, and it would be good to have the log files from /var/log/dist-upgrade. They should have reported the bug about ubuntu-release-upgrader-core but old habits die hard and its not obvious that these are two separate packages now.

Since ubuntu-release-upgrader was made a separate package the question regarding whether or not this is about a distribution upgrade was moved from the update-manager apport hook to the u-r-u apport hook. It seems to me that we could help people out and reduce back and forth if we were to ask this question again in the update-manager hook and change the package to ubuntu-release-upgrader-core so its hook gets run.

tags: added: quantal
Changed in update-manager (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
milestone: none → quantal-updates
Changed in update-manager (Ubuntu Quantal):
status: New → Triaged
importance: Undecided → Medium
milestone: none → quantal-updates
Changed in update-manager (Ubuntu):
milestone: quantal-updates → none
Changed in update-manager (Ubuntu):
status: Triaged → In Progress
assignee: nobody → Brian Murray (brian-murray)
Changed in update-manager (Ubuntu Quantal):
status: Triaged → Won't Fix
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package update-manager - 1:0.196.1

---------------
update-manager (1:0.196.1) trusty; urgency=low

  * debian/source_update_manager.py: Fix too long line (pep8 error).
 -- Brian Murray <email address hidden> Thu, 24 Oct 2013 13:31:42 -0700

Changed in update-manager (Ubuntu):
status: In Progress → Fix Released
description: updated
Changed in update-manager (Ubuntu Saucy):
status: New → In Progress
importance: Undecided → Medium
assignee: nobody → Brian Murray (brian-murray)
Revision history for this message
Brian Murray (brian-murray) wrote : Please test proposed package

Hello Brian, or anyone else affected,

Accepted update-manager into saucy-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/update-manager/1:0.194.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in update-manager (Ubuntu Saucy):
status: In Progress → Fix Committed
tags: added: verification-needed
Revision history for this message
Brian Murray (brian-murray) wrote :

I tested update-manager version 0.194.1 from saucy-proposed and confirm that it does ask me if the issue I am reporting is one that occurred when upgrading from one release to another.

tags: added: verification-done
removed: verification-needed
Revision history for this message
Stéphane Graber (stgraber) wrote : Update Released

The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.

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

This bug was fixed in the package update-manager - 1:0.194.1

---------------
update-manager (1:0.194.1) saucy-proposed; urgency=low

  * Add support for logind to the restart dialog. Thanks to Thaddaus
    Tintenfisch for the patch. (LP: #1232363)
  * In the apport hook ask if the bug is about upgrading from one release to
    another and send bug to ubuntu-release-upgrader. (LP: #1071057)
 -- Brian Murray <email address hidden> Fri, 25 Oct 2013 13:21:20 -0700

Changed in update-manager (Ubuntu Saucy):
status: Fix Committed → Fix Released
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.