1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
|
<!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=%3C201212112134.04632.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="020737.html">
<LINK REL="Next" HREF="020756.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=%3C201212112134.04632.thomas%40btspuhler.com%3E"
TITLE="[Mageia-dev] ANN: Upgrading from Mageia 2 via urpmi">thomas at btspuhler.com
</A><BR>
<I>Wed Dec 12 05:34:04 CET 2012</I>
<P><UL>
<LI>Previous message: <A HREF="020737.html">[Mageia-dev] ANN: Upgrading from Mageia 2 via urpmi
</A></li>
<LI>Next message: <A HREF="020756.html">[Mageia-dev] ANN: Upgrading from Mageia 2 via urpmi
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#20753">[ date ]</a>
<a href="thread.html#20753">[ thread ]</a>
<a href="subject.html#20753">[ subject ]</a>
<a href="author.html#20753">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On Tuesday, December 11, 2012 03:56:30 AM Colin Guthrie wrote:
><i> 'Twas brillig, and Thomas Spuhler at 11/12/12 04:51 did gyre and gimble:
</I>><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
</I>><i> >>>>>> 3 Upgrade Preparation" entry boot, wait while your FS is converted
</I>><i> >>>>>> and 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
</I>><i> >>>>>> should work). A specific kernel version is not really 100%
</I>><i> >>>>>> necessary but it does mean I can add hard requires to the package.
</I>><i> >>>>>> This is only desirable to prevent the situation where users install
</I>><i> >>>>>> this upgrade package but do not run it and later remove the kernel
</I>><i> >>>>>> used to generate the initrd for the bootloader menu item, thus
</I>><i> >>>>>> breaking it. 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
</I>><i> >>>>>> in your fstab, you will have to manually change the fstab to rw for
</I>><i> >>>>>> the 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
</I>><i> >>>>> 120+ 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
</I>><i> >>>> the download... or perhaps we could just ship some essential config
</I>><i> >>>> tweaks in the this mageia-prepare-upgrade file. It shouldn't do any
</I>><i> >>>> harm to do 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> >
</I>><i> > The requires are: Pizza and beer
</I>><i> :
</I>><i> :D
</I>><i> :
</I>><i> > install mageia-prepare-upgrade
</I>><i> > change sources to cauldron
</I>><i>
</I>><i> No need to change sources yet, but no harm in it either.
</I>><i>
</I>><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
</I>><i> > time-outs
</I>><i>
</I>><i> Hmm, this shouldn't take long... Especially if /usr is on the same
</I>><i> partition as / (it should take < 30s then really as it's "copying" using
</I>><i> hardlinks which are very quick). What kind of timeouts are you seeing here?
</I>><i>
</I>><i> Perhaps remove "silent" and "splash" here to get more verbose output.
</I>><i>
</I>><i> > (it will boot into a none graphic shell)
</I>><i>
</I>><i> Hmm, interesting. It seems the kernel entry added does not honour the
</I>><i> vga= argument. Need to work out why that is not propagated from the
</I>><i> other kernel entries.
</I>><i>
</I>><i> > login as root ans then startx
</I>><i> >
</I>><i> > create /var/run and then start the network
</I>><i>
</I>><i> Hmm, you need to *create* /var/run? This definitely should not be
</I>><i> needed. Are you saying you have no /var/run symlink?
</I>><i>
</I>><i> This should have been added as part of the conversion process.
</I>><i>
</I>><i> Can I ask:
</I>><i> 1. Do you have /var on a separate partition?
</I>no, same patition. I have / swap and /home
><i> 2. If so, did my updated package allow you to mount it OK in the initrd
</I>><i> (you can pass rd.break=mount and then check the /sysroot/var dir to see
</I>><i> if it's mounted - you will have to type "exit" once to actually do the
</I>><i> mount IIRC).
</I>><i> 3. If the conversion is done with rd.break=prepivot, does the
</I>><i> /sysroot/var/run symlink exist (again you may need to do "exit" once to
</I>><i> actually trigger the conversion).
</I>><i>
</I>><i> If so, then something is later on *removing* the /var/run symlink again.
</I>I only know its not there and that is why the network doesn't start. Also about for other services
need to timeout during boot because of the missing /var/run
><i>
</I>><i> In my earlier tests it was mandriva-clean-var-run-lock.service that
</I>><i> killed the symlinks. I made sure to disable it by rm'ing the symlink:
</I>><i> /lib/systemd/system/sysinit.target.wants/mandriva-clean-var-run-lock.servic
</I>><i> e
</I>><i>
</I>><i> I fear it is somehow still running for you and killing of /var/run.
</I>Could be but I don't know what. I know need the system to do some packaging.
><i>
</I>><i> > after network runs, remove the /var/run (otherwise filesystem will not
</I>><i> > install)
</I>><i>
</I>><i> No, /var/run should just be a symlink to /run then filesystem installs
</I>><i> fine - this is how it's meant to be, but something somewhere is going
</I>><i> wrong!
</I>><i>
</I>><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
</I>><i> > and go throught the /var/run cycle as desribed above)
</I>><i>
</I>><i> Something has to be nuking the /var/run symlink on your system.
</I>><i>
</I>><i> Does "systemctl status mandriva-clean-var-run-lock.service" indicate
</I>><i> it's been run? Does
</I>><i> [/usr]/lib/systemd/system/sysinit.target.wants/mandriva-clean-var-run-lock.
</I>><i> service still exist somehow?
</I>not anymore. Teh problem went away after about 1,000packges have been upgraded or maybe before.
I still have
mandriva-boot-links
mandriva-save-dmesg
><i>
</I>><i> > This got me a full up-to-date cauldron
</I>><i>
</I>><i> Glad you made it! Certainly still a few rough edges to get filed down
</I>><i> tho' :)
</I>><i>
</I>><i>
</I>><i> Thank you very much for testing this!!
</I>><i>
</I>><i> Col
</I>
--
Best regards
Thomas Spuhler
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="020737.html">[Mageia-dev] ANN: Upgrading from Mageia 2 via urpmi
</A></li>
<LI>Next message: <A HREF="020756.html">[Mageia-dev] ANN: Upgrading from Mageia 2 via urpmi
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#20753">[ date ]</a>
<a href="thread.html#20753">[ thread ]</a>
<a href="subject.html#20753">[ subject ]</a>
<a href="author.html#20753">[ 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>
|
