From Fedora Project Wiki
As someone who has used the liveupgrade process right back to RH7 (although not continuously on any single one machine) I can say that the main causes of pain are
- orphan packages with dependencies that can not be satisfied after the update
- other package repositories being present
- bespoke packages that have been installed but can't be automatically updated
- non-RPM software installed that depends on things that are not present after the update
- proprietary video drivers
I think that a combined text/gui 'wizard' for preparing a system for update would be a good thing:
- remove (and optionally repackage) orphan packages
- disable all unknown repositories
- enable rpm fusion or other well-known repositories if the user requests it
- perform the update
- capture data about the success or failure of a particular update, eg when the system successfully reboots.
Jpye 08:56, 20 November 2008 (UTC)