diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2012-December/020737.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-December/020737.html | 241 |
1 files changed, 241 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-December/020737.html b/zarb-ml/mageia-dev/2012-December/020737.html new file mode 100644 index 000000000..297a26d7d --- /dev/null +++ b/zarb-ml/mageia-dev/2012-December/020737.html @@ -0,0 +1,241 @@ +<!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=%3C50C7115E.7080808%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="020734.html"> + <LINK REL="Next" HREF="020753.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=%3C50C7115E.7080808%40colin.guthr.ie%3E" + TITLE="[Mageia-dev] ANN: Upgrading from Mageia 2 via urpmi">mageia at colin.guthr.ie + </A><BR> + <I>Tue Dec 11 11:56:30 CET 2012</I> + <P><UL> + <LI>Previous message: <A HREF="020734.html">[Mageia-dev] ANN: Upgrading from Mageia 2 via urpmi +</A></li> + <LI>Next message: <A HREF="020753.html">[Mageia-dev] ANN: Upgrading from Mageia 2 via urpmi +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#20737">[ date ]</a> + <a href="thread.html#20737">[ thread ]</a> + <a href="subject.html#20737">[ subject ]</a> + <a href="author.html#20737">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>'Twas brillig, and Thomas Spuhler at 11/12/12 04:51 did gyre and gimble: +><i> On Sunday, December 09, 2012 11:55:13 AM Colin Guthrie wrote: +</I>>><i> 'Twas brillig, and Thierry Vignaud at 09/12/12 18:48 did gyre and gimble: +</I>>>><i> On 9 December 2012 13:18, Colin Guthrie <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">mageia at colin.guthr.ie</A>> wrote: +</I>>>>>>><i> So I've just pushed the package mageia-prepare-upgrade to mga2 +</I>>>>>>><i> core/updates_testing. +</I>>>>>>><i> +</I>>>>>>><i> This package, when installed will add a new menu option to your +</I>>>>>>><i> bootloader. Simply install this package, reboot, select the "Mageia 3 +</I>>>>>>><i> Upgrade Preparation" entry boot, wait while your FS is converted and +</I>>>>>>><i> then perform a urpmi upgrade as you would normally. +</I>>>>>>><i> +</I>>>>>>><i> I've not specifically tested the upgrade part, only the installation +</I>>>>>>><i> and creation of the initrd and bootloader entries in grub. I've also +</I>>>>>>><i> not done this on an mga2 machine yet but will do soon enough. +</I>>>>>>><i> +</I>>>>>>><i> I just wanted to get this package "out there" for anyone wanting to +</I>>>>>>><i> update their mga2 machines to mga3 a3 but not wanting to use the +</I>>>>>>><i> installer. +</I>>>>>>><i> +</I>>>>>>><i> At present there are a few limitations: +</I>>>>>>><i> +</I>>>>>>><i> 1. It requires kernel 3.3.8-2.mga2 to be installed (any flavour should +</I>>>>>>><i> work). A specific kernel version is not really 100% necessary but it +</I>>>>>>><i> does mean I can add hard requires to the package. This is only +</I>>>>>>><i> desirable to prevent the situation where users install this upgrade +</I>>>>>>><i> package but do not run it and later remove the kernel used to +</I>>>>>>><i> generate the initrd for the bootloader menu item, thus breaking it. +</I>>>>>>><i> Any smarter ideas on how to manage this welcome. +</I>>>>>>><i> +</I>>>>>>><i> 2. If you have /usr in a separate partition and have it mounted ro in +</I>>>>>>><i> your fstab, you will have to manually change the fstab to rw for the +</I>>>>>>><i> upgrade boot. +</I>>>>>>><i> +</I>>>>>>><i> +</I>>>>>>><i> Happy testing. Let me know if it kills any kittens. Please keep a +</I>>>>>>><i> backup etc. etc. +</I>>>>>>><i> +</I>>>>>>><i> Col +</I>>>>>><i> +</I>>>>>><i> Thanks Colin. +</I>>>>>><i> The conversion works. But then the problem shows, we have no network. +</I>>>>>><i> doing a urpmi --download-all --auto-update only downloads the fist 120+ +</I>>>>>><i> rpms (the ones needed before restart-urpmi +</I>>>>>><i> +</I>>>>>><i> What is needed is to add some directories and then the network will +</I>>>>>><i> start /var/run/netreport +</I>>>>>><i> /var/lock/subsystem/network +</I>>>>>><i> +</I>>>>>><i> I will check after the upgrade if they can be deleted +</I>>>>><i> +</I>>>>><i> Hmm, yes, I guess after doing the upgrade the various /var/run and +</I>>>>><i> /var/lock folders would be nuked. In mga3 they will be created by +</I>>>>><i> tmpfiles but not with a simple reboot on mga2... +</I>>>>><i> +</I>>>>><i> Hmm, I wonder how best to do this... perhaps we could ship updated +</I>>>>><i> packages for each of the packages which absolutely *need* this to do the +</I>>>>><i> download... or perhaps we could just ship some essential config tweaks +</I>>>>><i> in the this mageia-prepare-upgrade file. It shouldn't do any harm to do +</I>>>>><i> the latter and it's a bit easier on the QA folk. +</I>>>><i> +</I>>>><i> Humm we could just package mageia-prepare-upgrade in mga3 and add +</I>>>><i> it to urpmi priority list. +</I>>>><i> Thus it would also work for people who never apply updates... +</I>>>><i> My 2 cents +</I>>><i> +</I>>><i> Not sure it would help. I mean users have to install it, reboot and then +</I>>><i> install the rest... +</I>>><i> +</I>>><i> Also how does the urpmi priority list work? Does that not require that +</I>>><i> we install urpmi first? If so that likely won't work as there is a +</I>>><i> chicken and egg scenario that prevents the rpm+urpmi from mga3 being +</I>>><i> installed until the fs is updated. +</I>>><i> +</I>>><i> +</I>>><i> Basically, a fully up-to-date mga2 (including rpm package and the +</I>>><i> mageia-prepare-upgrade package) + reboot for preparation is needed for a +</I>>><i> urpmi-based upgrades to work. +</I>>><i> +</I>>><i> Col +</I>><i> +</I>><i> OK, I started all over again from a completed mga 2 with all updates. +</I> +><i> The requires are: Pizza and beer +</I> +:<i>D +</I> +><i> install mageia-prepare-upgrade +</I>><i> change sources to cauldron +</I> +No need to change sources yet, but no harm in it either. + +><i> reboot with mageia-prepare-ugrade +</I>><i> +</I>><i> eat pizza and drink beer, it takes a lot of time to pass all the time-outs +</I> +Hmm, this shouldn't take long... Especially if /usr is on the same +partition as / (it should take < 30s then really as it's "copying" using +hardlinks which are very quick). What kind of timeouts are you seeing here? + +Perhaps remove "silent" and "splash" here to get more verbose output. + +><i> (it will boot into a none graphic shell) +</I> +Hmm, interesting. It seems the kernel entry added does not honour the +vga= argument. Need to work out why that is not propagated from the +other kernel entries. + +><i> login as root ans then startx +</I>><i> create /var/run and then start the network +</I> +Hmm, you need to *create* /var/run? This definitely should not be +needed. Are you saying you have no /var/run symlink? + +This should have been added as part of the conversion process. + +Can I ask: + 1. Do you have /var on a separate partition? + 2. If so, did my updated package allow you to mount it OK in the initrd +(you can pass rd.break=mount and then check the /sysroot/var dir to see +if it's mounted - you will have to type "exit" once to actually do the +mount IIRC). + 3. If the conversion is done with rd.break=prepivot, does the +/sysroot/var/run symlink exist (again you may need to do "exit" once to +actually trigger the conversion). + +If so, then something is later on *removing* the /var/run symlink again. + +In my earlier tests it was mandriva-clean-var-run-lock.service that +killed the symlinks. I made sure to disable it by rm'ing the symlink: +/lib/systemd/system/sysinit.target.wants/mandriva-clean-var-run-lock.service + +I fear it is somehow still running for you and killing of /var/run. + +><i> after network runs, remove the /var/run (otherwise filesystem will not install) +</I> +No, /var/run should just be a symlink to /run then filesystem installs +fine - this is how it's meant to be, but something somewhere is going wrong! + +><i> then use urpmi --auto-update +</I>><i> +</I>><i> ( got the message "/" is mount read-only a few times and had to re-boot and go throught the +</I>><i> /var/run cycle as desribed above) +</I> +Something has to be nuking the /var/run symlink on your system. + +Does "systemctl status mandriva-clean-var-run-lock.service" indicate +it's been run? Does +[/usr]/lib/systemd/system/sysinit.target.wants/mandriva-clean-var-run-lock.service +still exist somehow? + + +><i> This got me a full up-to-date cauldron +</I> +Glad you made it! Certainly still a few rough edges to get filed down +tho' :) + + +Thank you very much for testing this!! + +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="020734.html">[Mageia-dev] ANN: Upgrading from Mageia 2 via urpmi +</A></li> + <LI>Next message: <A HREF="020753.html">[Mageia-dev] ANN: Upgrading from Mageia 2 via urpmi +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#20737">[ date ]</a> + <a href="thread.html#20737">[ thread ]</a> + <a href="subject.html#20737">[ subject ]</a> + <a href="author.html#20737">[ 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> |