do-release-upgrade needs a --force-yes option

[Jeff Lane ]

I completely understand why, when I run do-release-upgrade, I have to sit in front of a computer for hours waiting on the various prompts that stop the upgrade process... were I doing this on a production system, I'd welcome those stopping points to make sure nothing hinky was going on.

HOWEVER, I, and I'm sure a LOT of people do upgrade testing and so forth during the dev cycle and would love to have a --force-yes option in do-release-upgrade.

It is so very annoying to kick off the upgrade like this: $ do-release-upgrade -d

only to have it stop 4 or 5 or more times during the process... this usually happens after I've walked off, and forgotten that I have to come back and push buttons.

SO I'll kick off an upgrade, fully expecting it to be done by the time I'm done with dinner or whatever, only to return to the computer and learn that none of it is done becuase it is sitting at some prompt waiting on my to hit the 'y' key.

When I'm doing this testing, I KNOW the dangers and willingly accept them, so PLEASE give me the means to just set it and forget it so I can stop wasting time thinking an upgrade is in progress when it is actually not.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: ubuntu-release-upgrader-core 1:0.205
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
ApportVersion: 2.12.5-0ubuntu2
Architecture: amd64
CrashDB: ubuntu
Date: Tue Mar 25 10:07:01 2014
InstallationDate: Installed on 2013-10-18 (157 days ago)
InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016)
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: No upgrade log present (probably fresh install)

[rubo77 (rubo77)]

Another attempt: ask all questions at the start, before starting the upgrade process: bug 1309802

[Aleksey (evenfrost)]

Any update on this?