diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2013-March/023773.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2013-March/023773.html | 196 |
1 files changed, 196 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2013-March/023773.html b/zarb-ml/mageia-dev/2013-March/023773.html new file mode 100644 index 000000000..5166932e1 --- /dev/null +++ b/zarb-ml/mageia-dev/2013-March/023773.html @@ -0,0 +1,196 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] ANN: Upgrading from Mageia 2 via urpmi + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20ANN%3A%20Upgrading%20from%20Mageia%202%20via%20urpmi&In-Reply-To=%3C514EECD3.5050003%40colin.guthr.ie%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="023759.html"> + <LINK REL="Next" HREF="023784.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] ANN: Upgrading from Mageia 2 via urpmi</H1> + <B>Colin Guthrie</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20ANN%3A%20Upgrading%20from%20Mageia%202%20via%20urpmi&In-Reply-To=%3C514EECD3.5050003%40colin.guthr.ie%3E" + TITLE="[Mageia-dev] ANN: Upgrading from Mageia 2 via urpmi">mageia at colin.guthr.ie + </A><BR> + <I>Sun Mar 24 13:08:51 CET 2013</I> + <P><UL> + <LI>Previous message: <A HREF="023759.html">[Mageia-dev] ANN: Upgrading from Mageia 2 via urpmi +</A></li> + <LI>Next message: <A HREF="023784.html">[Mageia-dev] ANN: Upgrading from Mageia 2 via urpmi +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#23773">[ date ]</a> + <a href="thread.html#23773">[ thread ]</a> + <a href="subject.html#23773">[ subject ]</a> + <a href="author.html#23773">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Hi, + + +Thanks for detailing your tests :) + +'Twas brillig, and Luca Olivetti at 23/03/13 20:00 did gyre and gimble: +><i> Al 18/11/12 17:37, En/na Colin Guthrie ha escrit: +</I>><i> +</I>>><i> +</I>>><i> Happy testing. Let me know if it kills any kittens. Please keep a backup +</I>>><i> etc. etc. +</I>><i> +</I>><i> I prepared a virtual machine with the same set of packages I have in the +</I>><i> real one with mageia 2 to test the upgrade. +</I>><i> Once installed the mageia-prepare-upgrade package, I rebooted using the +</I>><i> "Mageia 3 Upgrade Preparation" entry. Since the instructions don't say +</I>><i> anything, I used that same entry to perform the upgrade (should I have +</I>><i> rebooted in the original, plain, mageia 2). +</I>><i> +</I>><i> Anyway, these are the issues I found: +</I>><i> +</I>><i> 0) In the "Mageia 3 Upgrade Preparation" NetworkManager stopped +</I>><i> working, in its place the network applet was used (after the upgrade +</I>><i> both worked). +</I> + +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 :) + +><i> 1) every other transaction complained with this message: +</I>><i> +</I>><i> p11-kit: invalid config filename, will be ignored in the future: +</I>><i> /etc/pkcs11/modules/gnome-keyring-module +</I>><i> +</I>><i> 2) with less frequency there were these messages (usually 13 in a row, +</I>><i> with different 'xxx'). +</I>><i> +</I>><i> warning: Schema 'xxx' has path 'xxx'. Paths starting with '/apps/', +</I>><i> '/desktop/' or '/system/' are deprecated. +</I> +Not really sure about these ones. + + +><i> 3) a handful of packages complained that they couldn't remove files in +</I>><i> /var/run (I suppose that's to be expected) +</I> +Yes to be expected, but if my generated tmpfiles config approach is +taken above then these errors will likely be reduced somewhat. + +><i> 4) some packages took a long time to execute the %post script +</I>><i> +</I>><i> /bin/systemctl --quiet --try-restart (package) +</I>><i> +</I>><i> which eventually failed +</I> +Yeah I'm not sure how to address this better :s + +><i> 5) rtkit hung on the %post script +</I>><i> dbus-send --system --type=method_call --dest=org.freedesktop.DBus / +</I>><i> org.freedesktop.DBus.ReloadConfig +</I>><i> +</I>><i> Eventually I had to kill dbus-send to go on with the upgrade +</I> +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? + +I'm also not 100% sure if this is absolutely needed either... will ask +upstream. + +><i> 6) some packages (e.g., cups, rpcbind, networkmanager and others) gave +</I>><i> this message +</I>><i> +</I>><i> Migrating sysvinit service 'xxx' to systemd native unit 'xxx.service' +</I>><i> via systemd install rules. +</I>><i> Failed to issue method call: File exists +</I> +Yeah possibly "safe" but I can maybe fix this better via different +arguments to systemctl enable in rpm-helper (i.e. passing --force). + +><i> 7) there was a file conflict between kipi-plugins and +</I>><i> kipi-plugins-htmlexport, I urpmed the latter. +</I> +Needs to be fixed by KDE people to add a conflict I guess. Possibly +worth a bug report or just ping neoclust or mikala + +><i> 8) I had some problem rebooting (I was using a konsole in kde), the kde +</I>><i> menu bar didn't work, trying to do an acpi shutdown didn't work, text +</I>><i> console didn't work. Eventually I just pulled the virtual plug. +</I> +Yeah one of the many problems related to online updates really :) the +"reboot" command should work, but.... :) + +><i> 9) plymouthd complained but I hadn't time to write down the message, it +</I>><i> eventually booted fine (but with no graphical menu, probably because the +</I>><i> initrd was generated running the "Mageia 3 Upgrade Preparation" entry). +</I> +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> Apart from these problems, it seems the upgrade went well, though I +</I>><i> didn't do any extensive testing (just booted it). +</I> +Thanks again for the tests :) + + +Col + +-- + +Colin Guthrie +colin(at)mageia.org +<A HREF="http://colin.guthr.ie/">http://colin.guthr.ie/</A> + +Day Job: + Tribalogic Limited <A HREF="http://www.tribalogic.net/">http://www.tribalogic.net/</A> +Open Source: + Mageia Contributor <A HREF="http://www.mageia.org/">http://www.mageia.org/</A> + PulseAudio Hacker <A HREF="http://www.pulseaudio.org/">http://www.pulseaudio.org/</A> + Trac Hacker <A HREF="http://trac.edgewall.org/">http://trac.edgewall.org/</A> +</PRE> + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="023759.html">[Mageia-dev] ANN: Upgrading from Mageia 2 via urpmi +</A></li> + <LI>Next message: <A HREF="023784.html">[Mageia-dev] ANN: Upgrading from Mageia 2 via urpmi +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#23773">[ date ]</a> + <a href="thread.html#23773">[ thread ]</a> + <a href="subject.html#23773">[ subject ]</a> + <a href="author.html#23773">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev +mailing list</a><br> +</body></html> |