[Bug 538839] Re: when "do-release-upgrade" aborts, no instructions are given for how to complete the upgrade

[kabsi]

Paul, you saved my day. Thanks!

I was stuck with  the error message and the problem reported in this
bug. Had I rebooted the system, I would have been stuck with a half-
updated non-bootable system. I followed your advice and got my system
updated and running.

Changes to your suggestions:
- I dropped step #1 and #2 as I already had updated my system this way before running do-release-upgraded.
- The URL in step #3 has changed to
  http://archive.ubuntu.com/ubuntu/dists/lucid/main/dist-upgrader-all/current/lucid.tar.gz
- I dropped step #5 as I did not have to comment out line 352. it worked anyway.
- In step #6, I  ran "sudo ./lucid --frontend=DistUpgradeViewText" as I prefer a text interface instead of a graphical view.

Step #6 failed due to some pakets. I deinstalled them and ran #6 again.
I repeated this process until installation went through and offered a
reboot.

-- 
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/538839

Title:
  when "do-release-upgrade" aborts, no instructions are given for how to
  complete the upgrade

Status in “update-manager” package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: update-manager

  I was recently running "do-release-upgrade -d" from the command line
  to upgrade to Lucid (from Hardy).

  After the command downloaded downloaded the "lucid.tar.gz" installer
  bundle followed by all the new .deb packages, and then
  installed/configured for a while, I got the following error message:

  ============================
  dpkg: subprocess installed post-installation script returned error exit status 1
  Exception during pm.DoInstall():  E:Sub-process /usr/bin/dpkg returned an error 
  code (2)

  Could not install the upgrades

  The upgrade is now aborted. Your system could be in an unusable 
  state. A recovery will run now (dpkg --configure -a). 
  ============================

  The system proceed with "Setting up" packages for a while, then finally, do-release-upgrade printed
  ============================
  Upgrade complete 

  The upgrade is completed but there were errors during the upgrade 
  process. 
  ============================
  , and then I was returned to the my shell prompt.

  After I resolved the issue that caused the "dpkg" error, I noticed that a number of packages were still back at their Hardy versions -- that is, that the upgrade hadn't actually "completed".  
  I tried running "do-release-upgrade -d" again in order to get the rest of the packages updated to their Lucid versions, but it aborted with the message "No new release found".

  So I am writing to suggest the following (related) changes to the
  messages printed by the do-release-upgrade process:

  1) In the cases where the upgrade is aborted due to a dpkg error, the
  two messages it prints out (which will often be many pages apart
  within the terminal session) should more consistent, or at least
  explained the exact status of the system more clearly (i.e. what has
  actually "completed" and what is still left unfinished).

  2)  The above-quoted "there were errors during the upgrade" message
  should include some more specific instructions about what the user is
  advised to do to recover from that situation.  (In my case I just used
  "aptitude" manually to upgrade the rest of the packages, but I wasn't
  sure if there was some "better" way to proceed.)

  (If such instructions can't be included into the "lucid" script for
  some reason, perhaps they could at least be included in the how-to-
  perform-an-upgrade instructions in the Lucid release notes.)

  Thanks.

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