F20 Installs Fail From Every Angle

[Tom H]

On Mon, Dec 30, 2013 at 8:08 PM, Brian Hanks <bhanks at bhanks.net> wrote:
>
> Interestingly, I found this on the Fedora FedUp Wiki page:
>
> Will packages in third party repositories be upgraded?
>
> Yes, if they are set up like regular yum repositories and do not hard code
> the repository path. Commonly-used third party repositories usually work
> fine, but if you attempt to upgrade prior to or soon after an official
> Fedora release, they may not have updated their repository paths yet, and
> FedUp may be unable to find their packages. This will usually not prevent
> the upgrade running successfully, though, and you can update the packages
> from the third-party repository later.
>
> After reading this, I checked my RPMFusion repos and found that none are
> hard-coded. All are using the $releasever variable, and all resolve to
> valid repos with the proper packages available. My assumption is that
> something isn't working as described.

See the "related issues" section:

https://lists.fedoraproject.org/pipermail/devel/2013-December/193288.html

>From that section:

Post-release reports also make it clear that fedup will abort if GPG
keys for *any* repository fedup finds available for the target release
cannot be found. i.e., if you have RPM Fusion or another popular third
party repository configured, it's quite likely your upgrade will fail,
because third party repos didn't have the signing key issue lined up
(not surprising if we couldn't even entirely manage it ourselves). We
were not sufficiently aware of this behaviour before release, and did
not communicate it very well. The underlying causes of this are much the
same as the underlying causes of the main issue - the fedup which
enabled GPG checking landing very late, inadequate/incorrect test
procedures, and limited knowledge of the details of fedup operation
outside a small group of people.