[Mageia-dev] ANN: Upgrading from Mageia 2 via urpmi

Sun Mar 24 17:02:48 CET 2013

Al 24/03/13 13:08, En/na Colin Guthrie ha escrit:
+
+>>
+>> 0) In the "Mageia 3 Upgrade Preparation"  NetworkManager stopped
+>> working, in its place the network applet was used (after the upgrade
+>> both worked).
+> 
+> 
+> Yeah, this is due to various folders disappearing... I guess I should
+> probably do something clever in that package. Perhaps I could look at
+> the folders in /var/run and their respective owners etc., then write a
+> file in /etc/tmpfiles.d with them detailed.
+> 
+> Then when the package is removed again later (automatically as part of
+> the upgrade) this file would be removed. This should mask most of the
+> errors. It's not fool proof but it'll probably be enough to avoid
+> problems in this case. Will add to my TODO :)
+
+Maybe it's just enough to put it in the wiki, so that one knows what to
+expect.
+
+>> Eventually I had to kill dbus-send to go on with the upgrade
+> 
+> I guess I'll have to find a way to time this out... perhaps adding
+> --reply-timeout would work. It would be nice if your VM was in a state
+> to be able to test if this has any effect?
+
+Sure, I have a snapshot before the update just for that (i.e., I want to
+be absolutely sure that the upgrade to the final mageia 3 works smoothly
+before even attempting to upgrade the real machine). The only problem is
+that the update takes roughly 3 hours.
+Ping me when you want me to test again.
+
+>> 8) I had some problem rebooting (I was using a konsole in kde), the kde
+>> menu bar didn't work, trying to do an acpi shutdown didn't work, text
+>> console didn't work. Eventually I just pulled the virtual plug.
+> 
+> Yeah one of the many problems related to online updates really :) the
+> "reboot" command should work, but.... :)
+
+The problem is I already closed the working konsole (silly me) and at
+that point I couldn't do anything but pull the plug
+
+> 
+>> 9) plymouthd complained but I hadn't time to write down the message, it
+>> eventually booted fine (but with no graphical menu, probably because the
+>> initrd was generated running the "Mageia 3 Upgrade Preparation" entry).
+> 
+> It shouldn't really matter too much to be honest. The upgrade prep
+> option should be almost identical to a regular boot other than an
+> additional check will be done on each boot thereafter. But as
+> rpm-mageia-setup package is removed on upgrade and with it the menu
+> entry, it shouldn't get in the way too much.
+
+I performed the update under the "Mageia 3 Upgrade Preparation" and,
+since that had no graphical boot, the resulting new kernel also has no
+graphical boot. To restore it I had to manually run dracut once booted
+in mageia 3.
+Maybe I should have performed the update rebooting into the regular
+mageia 2? The wiki isn't clear about it.
+
+Bye
+-- 
+Luca
+