On Mon, 30 Dec 2013 19:47:30 +0100, Michael Schwendt wrote:
So, there are no repos that offer updates for those three packages? Or is fedup unable to handle 3rd party repos?
Other than that, please don't add my name to the mail's subject line in such a misleading/ambiguous way. Thank you.
My apologies for leaving your name in the Subject line. It was a copy paste error that has been perpetuated as others have replied.
The RPMFusion repos do have the proper VirtualBox packages, so it seems that fedup is not looking at the 3rd party repos that I have configured.
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.
Brian
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 12/30/2013 3:08 PM, Brian Hanks wrote:
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.
I had this same issue. For me, I just removed those repos then added them back in after the upgrade. I have very little from the RPMFusion repo so it didn't mess up my system to leave the F19 packages on their until I finished the upgrade and reinstalled the repo RPMs. Everything worked fine after that.
- -- Mark Haney Network Administrator/IT Support Practichem W:919-714-8428
On Mon, Dec 30, 2013 at 8:08 PM, Brian Hanks bhanks@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.
-
Brian Hanks -
Mark Haney -
Tom H