Could not open RPM-GPG-KEY-rpmfusion-free-fedora-18-i386 (update fedora 17 -> 18)

[Andrew Sturgess]

Reindl Harald wrote at 17:05 +0100 on Mar 16, 2013:
 > Am 16.03.2013 16:55, schrieb Andrew Sturgess:
 > > I am trying to do a yum update from Fedora 17 to Fedora 18 and am
 > > getting this when I do 'sudo yum --releasever=18
 > > --disableplugin=presto distro-sync':
 > >
 > > GPG key retrieval failed: [Errno 14] Could not open/read file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-free-fedora-18-i386
....
 > > I could try to disable the rpmfusion repos during the f17->f18
 > > update (then manually update the rpmfusion packages afterwards),
 > > but this has worked fine in the past (f14->f15, f15->f16,
 > > f16->f17) to have the big yum update included the extra packages
 > > in rpmfusion from one major fedora release to the next.
 > >
 > > [I could also add --nogpgcheck, but I prefer not to use that unsafe option]
 > >
 > > I suppose I could also manually delete the current rpmfusion repo
 > > definition packages (rpmfusion-free-release-17.0.4-1.noarch and
 > > rpmfusion-nonfree-release-17.0.4-1.noarch) and force install the
 > > f18 rpmfusion ones (download and manually install using 'rpm
 > > -i').  But what's the right path now for including rpmfusion
 > > packages with the base fedora packages when doing a yum update
 > > from one major fedora version to the next?
 >
 > simply edit the repo-files and remove the ARCH-part from the path
 >
 > no idea why rpmfusion did such a invasive change but the
 > ARCH part was simply removed from the filename

Thanks for that.

What I wound up doing rather than editing the
yum.repos.d/rpmfusion*.repo files was to just create sym links
for my arch (i386) manually...

sudo ln -s RPM-GPG-KEY-rpmfusion-free-fedora-18-primary /etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-free-fedora-18-i386
sudo ln -s RPM-GPG-KEY-rpmfusion-nonfree-fedora-18-primary /etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-nonfree-fedora-18-i386

That's what the rpmfusion-*-release-18*.noarch packages have anyway, and it
let's me do the update from 17 to 18 seamlessly.

They should probably at least create those N + 1 sym links for the
rpmfusion-*-release-N*.noarch packages so upgrades using
'yum --releasever=N+1 ...' will work.

Hmm.. actually for the rpmfusion-*free-release-18-3.noarch.rpm
packages, that's exactly what they have done.