diff options
| author | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
|---|---|---|
| committer | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
| commit | 1be510f9529cb082f802408b472a77d074b394c0 (patch) | |
| tree | b175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-dev/2012-December/020734.html | |
| parent | fa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff) | |
| download | archives-master.tar archives-master.tar.gz archives-master.tar.bz2 archives-master.tar.xz archives-master.zip | |
Diffstat (limited to 'zarb-ml/mageia-dev/2012-December/020734.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-December/020734.html | 170 |
1 files changed, 170 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-December/020734.html b/zarb-ml/mageia-dev/2012-December/020734.html new file mode 100644 index 000000000..6169e5804 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-December/020734.html @@ -0,0 +1,170 @@ +<!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=%3C201212102151.53094.thomas%40btspuhler.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="020697.html"> + <LINK REL="Next" HREF="020737.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] ANN: Upgrading from Mageia 2 via urpmi</H1> + <B>Thomas Spuhler</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=%3C201212102151.53094.thomas%40btspuhler.com%3E" + TITLE="[Mageia-dev] ANN: Upgrading from Mageia 2 via urpmi">thomas at btspuhler.com + </A><BR> + <I>Tue Dec 11 05:51:52 CET 2012</I> + <P><UL> + <LI>Previous message: <A HREF="020697.html">[Mageia-dev] ANN: Upgrading from Mageia 2 via urpmi +</A></li> + <LI>Next message: <A HREF="020737.html">[Mageia-dev] ANN: Upgrading from Mageia 2 via urpmi +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#20734">[ date ]</a> + <a href="thread.html#20734">[ thread ]</a> + <a href="subject.html#20734">[ subject ]</a> + <a href="author.html#20734">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Sunday, December 09, 2012 11:55:13 AM Colin Guthrie wrote: +><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> +OK, I started all over again from a completed mga 2 with all updates. +The requires are: Pizza and beer +install mageia-prepare-upgrade +change sources to cauldron +reboot with mageia-prepare-ugrade + +eat pizza and drink beer, it takes a lot of time to pass all the time-outs + +(it will boot into a none graphic shell) +login as root ans then startx + create /var/run and then start the network +after network runs, remove the /var/run (otherwise filesystem will not install) + +then use urpmi --auto-update + +( got the message "/" is mount read-only a few times and had to re-boot and go throught the +/var/run cycle as desribed above) + +This got me a full up-to-date cauldron + + +-- +Best regards +Thomas Spuhler +</PRE> + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="020697.html">[Mageia-dev] ANN: Upgrading from Mageia 2 via urpmi +</A></li> + <LI>Next message: <A HREF="020737.html">[Mageia-dev] ANN: Upgrading from Mageia 2 via urpmi +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#20734">[ date ]</a> + <a href="thread.html#20734">[ thread ]</a> + <a href="subject.html#20734">[ subject ]</a> + <a href="author.html#20734">[ 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> |