3:55 p.m.
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 saw on some lists that things have changed and I should be using the
"branched" rpmfusion repositories now... like so:
sudo yum localinstall --nogpgcheck
http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-branche...
http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-b...
But when I try that, I get:
=================================
--> Running transaction check
---> Package rpmfusion-free-release.noarch 0:19-0.3 will be installed
--> Processing Dependency: system-release >= 19 for package:
rpmfusion-free-release-19-0.3.noarch
---> Package rpmfusion-nonfree-release.noarch 0:19-0.3 will be installed
--> Processing Dependency: system-release >= 19 for package:
rpmfusion-nonfree-release-19-0.3.noarch
--> Finished Dependency Resolution
Error: Package: rpmfusion-free-release-19-0.3.noarch
(/rpmfusion-free-release-branched.noarch)
Requires: system-release >= 19
Installed: fedora-release-17-2.noarch (@updates)
system-release = 17-2
Available: fedora-release-17-1.noarch (fedora)
system-release = 17-1
Available: generic-release-17-1.noarch (fedora)
system-release = 17-1
Error: Package: rpmfusion-nonfree-release-19-0.3.noarch
(/rpmfusion-nonfree-release-branched.noarch)
Requires: system-release >= 19
Installed: fedora-release-17-2.noarch (@updates)
system-release = 17-2
Available: fedora-release-17-1.noarch (fedora)
system-release = 17-1
Available: generic-release-17-1.noarch (fedora)
system-release = 17-1
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
===========================
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?
4:05 p.m.
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 saw on some lists that things have changed and I should be using the
"branched" rpmfusion repositories now... like so:
sudo yum localinstall --nogpgcheck
http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-branche...
http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-b...
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
8:19 p.m.
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.
9:04 p.m.
2013/3/16 Andrew Sturgess <59nn9wjvjw(a)snkmail.com>
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
There is a known issue that need yet to be determined, this should have
workaround the problem:
yum --releasever=18 --disableplugin=presto distro-sync --nogpgcheck
But I wonder if someone can test with:
yum --releasever=18 --disableplugin=presto update \*-release (--nogpgcheck)
yum distro-sync
The reported bug has even less information, please follow there:
https://bugzilla.rpmfusion.org/show_bug.cgi?id=2644
I saw on some lists that things have changed and I should be using the
"branched" rpmfusion repositories now... like so:
sudo yum localinstall --nogpgcheck
http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-branche...
http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-b...
.
Error: Package: rpmfusion-free-release-19-0.3.noarch
(/rpmfusion-free-release-branched.noarch)
Requires: system-release >= 19
Installed: fedora-release-17-2.noarch (@updates)
That's on purpose, branched is f19 nowadays. (since last friday).
Nicolas (kwizart)
9:08 p.m.
Am 18.03.2013 22:04, schrieb Nicolas Chauvet:
2013/3/16 Andrew Sturgess <59nn9wjvjw(a)snkmail.com
<mailto:59nn9wjvjw@snkmail.com>>
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
There is a known issue that need yet to be determined, this should have workaround the
problem:
yum --releasever=18 --disableplugin=presto distro-sync --nogpgcheck
But I wonder if someone can test with:
yum --releasever=18 --disableplugin=presto update \*-release (--nogpgcheck)
yum distro-sync
works too, done long ago while upgrade to F18
but i wonder that this has passed QA
9:11 p.m.
2013/3/18 Reindl Harald <h.reindl(a)thelounge.net>
Am 18.03.2013 22:04, schrieb Nicolas Chauvet:
> 2013/3/16 Andrew Sturgess <59nn9wjvjw(a)snkmail.com <mailto:
59nn9wjvjw(a)snkmail.com>>
>
> 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
>
> There is a known issue that need yet to be determined, this should have
workaround the problem:
> yum --releasever=18 --disableplugin=presto distro-sync --nogpgcheck
>
> But I wonder if someone can test with:
> yum --releasever=18 --disableplugin=presto update \*-release
(--nogpgcheck)
> yum distro-sync
works too, done long ago while upgrade to F18
With or without the nogpgcheck option ?
but i wonder that this has passed QA
You can build a QA test matrice for RPM Fusion and run it for Fedora 19,
you are very welcomed to do so.
Nicolas (kwizart)
9:17 p.m.
Am 18.03.2013 22:11, schrieb Nicolas Chauvet:
> But I wonder if someone can test with:
> yum --releasever=18 --disableplugin=presto update \*-release (--nogpgcheck)
> yum distro-sync
works too, done long ago while upgrade to F18
With or without the nogpgcheck option ?
with --nogpgcheck
but i wonder that this has passed QA
You can build a QA test matrice for RPM Fusion and run it for Fedora 19, you are very
welcomed to do so.
it doe sreally not need a large QA to test a simple dist-upgrade
and since 10 out of 10 machines suffered the same key-problem
this is nothing which happens only in few cases
11:36 p.m.
2013/3/18 Reindl Harald <h.reindl(a)thelounge.net>
Am 18.03.2013 22:11, schrieb Nicolas Chauvet:
> > But I wonder if someone can test with:
> > yum --releasever=18 --disableplugin=presto update \*-release
(--nogpgcheck)
> > yum distro-sync
>
> works too, done long ago while upgrade to F18
>
> With or without the nogpgcheck option ?
with --nogpgcheck
OK, I think I got the root answear.
I've missed the symlinks for anything newer than Fedora release n
So the symlink should allow to upgrade with the already provided GPG keys
to Fedora n+2
The Fix was not related to the "last change" I made to the
rpmfusion-*-release for F-18, but an issue with the same package from
fedora-17 and inherited to the others fedora releases.
but i wonder that this has passed QA
>
> You can build a QA test matrice for RPM Fusion and run it for Fedora 19,
you are very welcomed to do so.
it doe sreally not need a large QA to test a simple dist-upgrade
and since 10 out of 10 machines suffered the same key-problem
this is nothing which happens only in few case
It might be "simple", but still requires time to get to the root cause.
People going to the root cause of issues at still so much rare.
Nicolas (kwizart)
4055
days inactive
4057
days old
rpmfusion-users@lists.rpmfusion.org
7 comments
3 participants
participants (3)
-
Andrew Sturgess -
Nicolas Chauvet -
Reindl Harald