<div dir="ltr"><br><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Adam Williamson</b> <span dir="ltr"><<a href="mailto:awilliam@redhat.com">awilliam@redhat.com</a>></span><br>
Date: Wed, Dec 18, 2013 at 1:57 AM<br>Subject: [Test-Announce] PSA: Use fedup 0.8 for upgrades to Fedora 20! (was Re: Should a working fedup in Fedora N's stable repository be a release criterion for N+1?)<br>To: <a href="mailto:test-announce@lists.fedoraproject.org">test-announce@lists.fedoraproject.org</a>, <a href="mailto:users@lists.fedoraproject.org">users@lists.fedoraproject.org</a><br>
<br><br>On Tue, 2013-12-17 at 21:47 -0800, Adam Williamson wrote:<br>
> On Tue, 2013-12-17 at 15:16 -0800, Andrew Lutomirski wrote:<br>
> > I have a tendency to upgrade to a new Fedora release as soon as it's<br>
> > final, and I sometimes upgrade even sooner. ISTM that the official<br>
> > upgrade process is almost always broken, often for known reasons.<br>
> > Should one of the criteria for releasing Fedora N+1 be that a<br>
> > fully-updated Fedora N must be able to successfully complete 'fedup'<br>
> > or whatever the current preferred upgrade program is?<br>
> ><br>
> > (FWIW, the current bug is particularly nasty -- fedup 0.7.0 apparently<br>
> > can't actually update anything, and the sequence:<br>
> ><br>
> > - Install fedup 0.7.0<br>
> > - Try it and watch it fail or hang<br>
> > - Update to fedup 0.8.0 from updates-testing<br>
> > - Run fedup<br>
> ><br>
> > ends up downloading all rpms *twice* a sucking up a correspondingly<br>
> > immense amount of disk space.<br>
><br>
> Um, I'm fairly sure it doesn't. It only re-downloads stuff that's<br>
> different from the previous run.<br>
><br>
> We did test upgrades to F20 with 0.7, and they did work in testing, and<br>
> quite a lot of people reported success with fedup in the last two weeks<br>
> when at least some of them likely used 0.7.<br>
><br>
> You have to bear in mind it's release day today, and there's always<br>
> weirdness on release day, and people who have success generally don't<br>
> report it while those who hit failure almost always do. I've been<br>
> advising people to upgrade to 0.8 and retry just as a kind of generic<br>
> piece of advice; for many of them, it'd probably work if they just<br>
> retried with 0.7. 0.8 does fix several bugs compared to 0.7, but 0.7<br>
> wasn't entirely broken.<br>
<br>
Eh, that'll teach me to talk before thoroughly testing: these words are<br>
delicious! Om nom nom.<br>
<br>
I just poked it a bit and it sure seems like upgrades with fedup 0.7 to<br>
F20 are busted. They definitely worked when we tested shortly before<br>
release, though. I can only think that using fedup 0.7 against upgrade<br>
kernel/image built with fedup-dracut 0.8 doesn't work.<br>
<br>
FranciscoD also points out that the location of files downloaded by<br>
fedup changed between 0.7 and 0.8, so if you do a run with 0.7 then try<br>
with 0.8, it'll re-download all the updates, which is a waste of space<br>
and bandwidth.<br>
<br>
So, here's the news: do your upgrades to F20 with fedup 0.8, yo. It's in<br>
updates-testing for F18 and F19 at present, but will go to stable for<br>
F19 tomorrow. If you're upgrading from F18, you'll need to pass<br>
'--nogpgcheck' to fedup, because of<br>
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1040689" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1040689</a> .<br>
<br>
If you did an unsuccessful run with fedup 0.7, then you can do:<br>
<br>
mv /var/tmp/fedora-upgrade /var/tmp/system-upgrade<br>
mv /var/lib/fedora-upgrade /var/lib/system-upgrade<br>
<br>
before running fedup 0.8, to save it downloading all the packages again,<br>
and make sure it cleans up nicely when it's done. I've just tested this,<br>
and it works.<br>
<br>
If you've already done an unsuccessful run with fedup 0.7 and then a<br>
successful run with 0.8, you may have files from the 0.7 run hanging<br>
around in /var/lib/fedora-upgrade and /var/tmp/fedora-upgrade. It is<br>
entirely safe and, indeed, advised to rm -rf these directories.<br>
<br>
Sorry for the mess, folks!<br>
<span class="HOEnZb"><font color="#888888">--<br>
Adam Williamson<br>
Fedora QA Community Monkey<br>
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net<br>
<a href="http://www.happyassassin.net" target="_blank">http://www.happyassassin.net</a><br>
<br>
_______________________________________________<br>
test-announce mailing list<br>
<a href="mailto:test-announce@lists.fedoraproject.org">test-announce@lists.fedoraproject.org</a><br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/test-announce" target="_blank">https://admin.fedoraproject.org/mailman/listinfo/test-announce</a><br>
--<br>
devel mailing list<br>
<a href="mailto:devel@lists.fedoraproject.org">devel@lists.fedoraproject.org</a><br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/devel" target="_blank">https://admin.fedoraproject.org/mailman/listinfo/devel</a><br>
Fedora Code of Conduct: <a href="http://fedoraproject.org/code-of-conduct" target="_blank">http://fedoraproject.org/code-of-conduct</a></font></span></div><br></div>