https://bugzilla.novell.com/show_bug.cgi?id=373279 User joe@ugh.de added comment https://bugzilla.novell.com/show_bug.cgi?id=373279#c8 Joachim Gleissner <joe@ugh.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |joe@ugh.de --- Comment #8 from Joachim Gleissner <joe@ugh.de> 2008-11-02 14:30:59 MDT --- Hi guys, sorry for the huge delay. System updates are quite a nightmare from scpm's point of view. After a system update, SuSEconfig.scpm should have been run, which detects a system update and tries to update the configuration data saved in the profiles. This might fail, especially in case of a rather sophisticated setup. James, since scpm refused to do anything (it does that to prevent data loss), I suspect that may have been the case. If you still got your /var/log/scpm of that date, could you attach it to this bug? Maybe it reveals something. Apart from that, I can try to reproduce it, but I cannot promise anything. And a few tips: scpm creates backups of all resources. They can be restored via the 'scpm backup' command (see 'info scpm' for documentation), the GUI front-end 'sumf' also has support for it, IIRC. After an update (not a re-initialisation), the backups should be still there. Also, for valuable configuration data, it can be a good idea to export the profiles before updating for extra backup. Even if the configuration scheme in the new system changed in an incompatible way, the old data will be accessible for manual migration in that case. Profile can be exported with the scpm's database tool, e.g. 'scpm db export profile ~/profilebaks/default default'. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.