[Bug 994063] [NEW] do-release-upgrade can't be continued after drop to shell

[Mike]

Public bug reported:

I'm attempting to run an upgrade from 10.04 LTS to 12.04 LTS. I ran "do-
release-upgrade -d" and after some time the process reported a conflict
in a configuration file.

Selecting "drop to shell to examine differences" gave me a shell
alright, but there were some odd issues with the TTY - line breaks not
performing a carriage return and so on. Then typing "exit" to exit that
shell exited the entire install process (which is running in tmux or
screen or similar).

The end result is a half-installed system in an unknown state, with no
obvious means of recovery, and I'm going to have to revert to backup.
Consequently I can't give any useful information about version numbers,
except all packages had been updated to the most recent in Lucid prior
to upgrade.

I would STRONGLY suggest you provide an option to run "do-release-
upgrade" without tmux or whatever it is, and/or provide an additional
argument to "do-release-upgrade" which will allow you to reconnect to an
disconnected instance.


Incidentally this was also reported by someone else here:
http://ubuntuforums.org/showthread.php?t=1969849

** Affects: update-manager-core (Ubuntu)
     Importance: Undecided
         Status: New

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

Title:
  do-release-upgrade can't be continued after drop to shell

Status in “update-manager-core” package in Ubuntu:
  New

Bug description:
  I'm attempting to run an upgrade from 10.04 LTS to 12.04 LTS. I ran
  "do-release-upgrade -d" and after some time the process reported a
  conflict in a configuration file.

  Selecting "drop to shell to examine differences" gave me a shell
  alright, but there were some odd issues with the TTY - line breaks not
  performing a carriage return and so on. Then typing "exit" to exit
  that shell exited the entire install process (which is running in tmux
  or screen or similar).

  The end result is a half-installed system in an unknown state, with no
  obvious means of recovery, and I'm going to have to revert to backup.
  Consequently I can't give any useful information about version
  numbers, except all packages had been updated to the most recent in
  Lucid prior to upgrade.

  I would STRONGLY suggest you provide an option to run "do-release-
  upgrade" without tmux or whatever it is, and/or provide an additional
  argument to "do-release-upgrade" which will allow you to reconnect to
  an disconnected instance.


  
  Incidentally this was also reported by someone else here: http://ubuntuforums.org/showthread.php?t=1969849

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