Update Manager should time out on debconf questions
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Software Updater |
New
|
Undecided
|
Unassigned |
Bug Description
I think that the upgrade should have timeouts on the various debconf questions that might happen during an upgrade. In this way if someone (let's say me) were to start an install (and let's say go to lunch) they wouldn't come back with the install almost at the beginning.
Here's how I think it should work. I think that if asked a question, that question should have a 1 minute timeout. If the question is not responded to, update manager should fail the install of that package. Then it should continue to install packages that aren't dependent on that one pushing the current package as far back in the queue as possible. While this wouldn't allow for a complete install, but it would allow for it to get much more complete if it is unattended.
I would suggest adding command line options to do-release-upgrade; --force-yes and --force-current. This would allow do-release-upgrade to answer questions of this form:
"Configuration file `/etc/gdm/Xsession'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : background this process to examine the situation
The default action is to keep your current version."
Without interrupting the upgrade process.
Maybe there is already a way of doing this?