fedup f20->f21 kde broken deps

[Adam Williamson]

On Wed, 2014-12-03 at 16:38 +0100, Michael Schwendt wrote:
> On Wed, 03 Dec 2014 08:07:10 -0500, Neal Becker wrote:
> 
> > fedup gave me the following warnings:
> > 
> >    kde-runtime-libs-4.14.3-2.fc20.x86_64 requires exiv2-
> > libs-0.23-5.fc20.x86_64, 
> > OpenEXR-libs-1.7.1-6.fc20.x86_64, libgcrypt-1.5.3-2.fc20.x86_64, 
> > ilmbase-1.0.3-7.fc20.x86_64, libwebp-0.3.1-3.fc20.x86_64
> 
> Well, I have yet to hear good things about fedup, so take the following
> with a grain of salt.

Um. Where have you been reading? I hear good things about it all the
time. It's by far got better feedback than our previous mechanisms.

> # yum list kde-runtime-libs
> Loaded plugins: langpacks
> Available Packages
> kde-runtime-libs.i686                4.14.3-2.fc21               updates-testing
> kde-runtime-libs.x86_64              4.14.3-2.fc21               updates-testing
> 
> This only shows that a "higher" kde-runtime-libs package is available for
> F21, albeit only in the updates-testing repo. Does fedup upgrade to
> updates-testing or just F21 Beta release +/- updates repo?

fedup uses the same repos enabled for the source release. If you have
u-t enabled for whatever you're upgrading from, it's used for whatever
you're upgrading to. If you don't, it isn't.

This kind of situation isn't unusual during the milestone freezes,
because when a packager updates something in all releases, the update
can hit stable releases before it hits the frozen pending release. As
long as the updates have sufficient karma, they will go into the 0-day
update set, and so as soon as we push that initial 0-day update set -
that is, before the official release day - this will go away.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net