Fedup troubles

KDE Auto Login

Window manager problems

Beartooth

Monday, 29 December 2014 Mon, 29 Dec '14

3:55 p.m.

There must be something obvious here that I don't see : Complete! [i.e., machine had just been fully updated.] [root@localhost ~]# fedup --network 21 --product=nonproduct setting up repos... getting boot images... .treeinfo.signed | 2.1 kB 00:00:00 setting up update... fedup.yum WARNING: nothing added for fedora-release-nonproduct finding updates 100% [===========================================================================] verify local files 100% [========================================================================] warning: /var/cache/system-upgrade/rpmfusion-nonfree/packages/rpmfusion- nonfree-release-21-1.noarch.rpm: Header V3 RSA/SHA256 Signature, key ID a668b376: NOKEY Importing GPG key 0xA668B376: Userid : "RPM Fusion nonfree repository for Fedora (21) <rpmfusion- buildsys(a)lists.rpmfusion.org>" Fingerprint: e160 058e f06f a4c3 c15d 0f86 0174 46d1 a668 b376 Package : rpmfusion-nonfree-release-20-1.noarch (@/rpmfusion-nonfree- release-20.noarch/20) From : /etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-nonfree-fedora-21 Downloading failed: Didn't install any keys [root@localhost ~]# Clue, please? -- Beartooth Staffwright, Not Quite Clueless Power User Remember I know little (precious little!) of where up is.

Show replies by date

Greg Woods

Monday, 29 December Mon, 29 Dec

4:03 p.m.

...

Downloading failed: Didn't install any keys [root@localhost ~]# Clue, please?

I never could get the GPG part of the Rpmfusion repo to work with fedup. I ended up using --nogpgcheck (yes I am aware of the risks of doing that) so that I could get fedup to complete. Once I had done the upgrade, I had to manually correct some of the symlinks in /etc/pki/rpm-gpg to get further updates to work properly without --nogpgcheck. There is a point during the upgrade process where the generic symlink RPM-GPG-KEY-fedora-x86_64 has to be changed from pointing to the F20 key to pointing to the F21 key, and this isn't working right. This seems like more of an rpmfusion problem than a Fedora problem. So I ran with --nogpgcheck, then manually fixed the symlink afterwards. My updates work fine now. --Greg

Beartooth

Tuesday, 30 December Tue, 30 Dec

12:49 p.m.

On Mon, 29 Dec 2014 15:03:07 -0700, Greg Woods wrote:

...

> > > Downloading failed: Didn't install any keys [root@localhost ~]# > > Clue, please? > > I never could get the GPG part of the Rpmfusion repo to work with fedup. I ended up using --nogpgcheck (yes I am aware of the risks of doing that) so that I could get fedup to complete. Once I had done the upgrade, I had to manually correct some of the symlinks in /etc/pki/rpm-gpg to get further updates to work properly without --nogpgcheck. There is a point during the upgrade process where the generic symlink RPM-GPG-KEY-fedora-x86_64 has to be changed from pointing to the F20 key to pointing to the F21 key, and this isn't working right. This seems like more of an rpmfusion problem than a Fedora problem. So I ran with --nogpgcheck, then manually fixed the symlink afterwards. My updates work fine now.

That did it : the machine is running F21 now. Many many thanks! I don't completely understand the caveat, though. I follow the need to fix the symlink, but I don't know how to do it. Iiuc, the fault is a bug in Fedora somewhere, which I was lucky enough to hit only on the last machine I fed up; if that's so, there must be more of us -- and, I hope, maybe, a nice clear mini-tutorial already posted somewhere explaining how to accomplish the fix. Anybody know? -- Beartooth Staffwright, Not Quite Clueless Power User Remember I know little (precious little!) of where up is.

Paul W. Frields

Monday, 5 January Mon, 5 Jan

4:03 p.m.

On Tue, Dec 30, 2014 at 06:49:48PM +0000, Beartooth wrote:

...

On Mon, 29 Dec 2014 15:03:07 -0700, Greg Woods wrote: >> >> >> Downloading failed: Didn't install any keys [root@localhost ~]# >> >> Clue, please? >> >> > I never could get the GPG part of the Rpmfusion repo to work with fedup. > I ended up using --nogpgcheck (yes I am aware of the risks of doing > that) so that I could get fedup to complete. Once I had done the > upgrade, I had to manually correct some of the symlinks in > /etc/pki/rpm-gpg to get further updates to work properly without > --nogpgcheck. > > There is a point during the upgrade process where the generic symlink > RPM-GPG-KEY-fedora-x86_64 has to be changed from pointing to the F20 key > to pointing to the F21 key, and this isn't working right. This seems > like more of an rpmfusion problem than a Fedora problem. So I ran with > --nogpgcheck, then manually fixed the symlink afterwards. My updates > work fine now. That did it : the machine is running F21 now. Many many thanks! I don't completely understand the caveat, though. I follow the need to fix the symlink, but I don't know how to do it. Iiuc, the fault is a bug in Fedora somewhere, which I was lucky enough to hit only on the last machine I fed up; if that's so, there must be more of us -- and, I hope, maybe, a nice clear mini-tutorial already posted somewhere explaining how to accomplish the fix. Anybody know?

I ran into a similar bug. From the fedup author(s) I understand they are aware of why this situation happens, and are working on a fix so it won't occur in future releases. -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ The open source story continues to grow: http://opensource.com

Richard England

Friday, 2 January Fri, 2 Jan

8:05 p.m.

On 12/30/14 14:51, Robin Laing wrote:

...

On 2014-12-29 15:03, Greg Woods wrote: >> >> >> >> Downloading failed: Didn't install any keys >> [root@localhost ~]# >> >> Clue, please? >> > > I never could get the GPG part of the Rpmfusion repo to work with > fedup. I > ended up using --nogpgcheck (yes I am aware of the risks of doing > that) so > that I could get fedup to complete. Once I had done the upgrade, I > had to > manually correct some of the symlinks in /etc/pki/rpm-gpg to get further > updates to work properly without --nogpgcheck. > > There is a point during the upgrade process where the generic > symlink RPM-GPG-KEY-fedora-x86_64 has to be changed from pointing to the > F20 key to pointing to the F21 key, and this isn't working right. This > seems like more of an rpmfusion problem than a Fedora problem. So I ran > with --nogpgcheck, then manually fixed the symlink afterwards. My > updates > work fine now. > > --Greg > > > I installed the gpg keys before running fedup using something similar to this for the various rpmfusion repos. rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-nonfree-fedora-21

+1 When I encountered that I, too, updated the keys then restarted fedup and it was successful. ~~R

Robin Laing

Tuesday, 30 December Tue, 30 Dec

4:51 p.m.

On 2014-12-29 15:03, Greg Woods wrote:

...

> > > > Downloading failed: Didn't install any keys > [root@localhost ~]# > > Clue, please? > I never could get the GPG part of the Rpmfusion repo to work with fedup. I ended up using --nogpgcheck (yes I am aware of the risks of doing that) so that I could get fedup to complete. Once I had done the upgrade, I had to manually correct some of the symlinks in /etc/pki/rpm-gpg to get further updates to work properly without --nogpgcheck. There is a point during the upgrade process where the generic symlink RPM-GPG-KEY-fedora-x86_64 has to be changed from pointing to the F20 key to pointing to the F21 key, and this isn't working right. This seems like more of an rpmfusion problem than a Fedora problem. So I ran with --nogpgcheck, then manually fixed the symlink afterwards. My updates work fine now. --Greg

I installed the gpg keys before running fedup using something similar to this for the various rpmfusion repos. rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-nonfree-fedora-21

3396

days inactive

3403

days old

users@lists.fedoraproject.org

Manage subscription

5 comments

5 participants

tags (0)

participants (5)

Beartooth
Greg Woods
Paul W. Frields
Richard England
Robin Laing