ServerUpgradeTool
Please check the status of this specification in Launchpad before editing it. If it is Approved, contact the Assignee or another knowledgeable person before making changes.
Launchpad entry: none yet
Packages affected:
BrainDump
* we should consider using the same daemon approach as for the GUI to protect against network failures * no "new-release"/"end-of-support notification mail by default (optional) * support tasks/meta-packages by looking if all packages of a tasks are installed
- (minimal,standard) but if it no metapackage is installed do not force to reinstall it - we may pop up a message about this (too much sh**).
* if it runs over ssh, we could prompt asking about starting a additional ssh
- daemon on a random port (ask because of FW issues) so that there is a backup available if the world explodes
* we should probably check for new/changes messages in
- /var/lib/update-notifier/user.d
* All questions (conffiles, package descisions) should be recordable so that it
- can be replayed [maybemaybembaybe offer droping to single user, put no value]
* no 3rd party sources.list modifying on the servers because of custom
- packages
Summary
Rationale
Use cases
Scope
We need to add a text based frontend for the ReleaseUpgrader. There needs to be commandline options to overwrite the frontend and the default configuration. For the server upgrade the rules are a bit different than for a desktop upgrade because e.g. we do not want to enforce certain packages (like ubuntu-desktop on the desktop).
Design
Implementation
Code
Data preservation and migration
Unresolved issues