[Bug 1097907] Re: Cannot upgrade from quantal (12.10) to raring (13.04)

[Brian Murray]

Hello Michael, or anyone else affected,

Accepted update-manager into quantal-proposed. The package will build
now and be available at http://launchpad.net/ubuntu/+source/update-
manager/1:0.174.4 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 Quantal)
       Status: Triaged => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to update-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1097907

Title:
  Cannot upgrade from quantal (12.10) to raring (13.04)

Status in “update-manager” package in Ubuntu:
  Fix Released
Status in “update-manager” source package in Quantal:
  Fix Committed

Bug description:
  [Impact]
  Users on Ubuntu 12.10 cannot upgrade to the development version of 13.04 (though, this bug does not stop them from upgrading to the released version of 13.04).

  [Reproduction Steps]
  0) Be on Ubuntu 12.10
  1) update-manager -d
  2) Notice that while it offers an upgrade choice, clicking upgrade does nothing.

  [Regression Potential]
  I can't think of any, but this patch only affects the release upgrade code path.

  [Analysis]
  This was caused by my refactoring during the quantal development cycle.  The "-d" is not being passed on to ubuntu-release-upgrader, causing it to do nothing when called (at least during raring development).

  I am looking into it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1097907/+subscriptions