On Fri, Nov 6, 2015 at 6:30 AM, Sam Varshavchik <mrsam(a)courier-mta.com&gt; wrote: > One upgrade to F23 succeeded. The second server fails, repeatedly with > "dnf system-upgrade --releasever 23 download" resulting in: > > … > [SKIPPED] zukitwo-gtk3-theme-0.0.2-1.fc23.noarch.rpm: Already downloaded > [SKIPPED] zukitwo-gtk2-theme-0.0.2-1.fc23.noarch.rpm: Already downloaded > warning: > /var/lib/dnf/system-upgrade/kernel-core-4.2.5-300.fc23.x86_64.rpm: Header > V3 RSA/SHA256 Signature, key ID 34ec9cba: NOKEY > Curl error (37): Couldn't read a file:// file for > file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-x86_64 [Couldn't open file > /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-x86_64] > The downloaded packages were saved in cache till the next successful > transaction. > You can remove cached packages by executing 'dnf clean packages'. > I'm getting this exact same Curl error (37) trying to do a dnf system-upgrade. Except my warning is about libgudev-230-2.fc23.x86_64.rpm instead of kernel-core-4.2.5-300.fc23.x86_64.rpm as above. Does anyone have a fix??

On 12/18/2015 09:42 AM, Robert Arkiletian wrote: > On Fri, Dec 18, 2015 at 9:29 AM, Robert Arkiletian <robark(a)gmail.com > <mailto:robark@gmail.com>> wrote: > > > > On Fri, Nov 6, 2015 at 6:30 AM, Sam Varshavchik > <mrsam(a)courier-mta.com <mailto:mrsam@courier-mta.com>> wrote: > > One upgrade to F23 succeeded. The second server fails, > repeatedly with > "dnf system-upgrade --releasever 23 download" resulting in: > > … > [SKIPPED] zukitwo-gtk3-theme-0.0.2-1.fc23.noarch.rpm: Already > downloaded > [SKIPPED] zukitwo-gtk2-theme-0.0.2-1.fc23.noarch.rpm: Already > downloaded > warning: > /var/lib/dnf/system-upgrade/kernel-core-4.2.5-300.fc23.x86_64.rpm: > Header V3 RSA/SHA256 Signature, key ID 34ec9cba: NOKEY > Curl error (37): Couldn't read a file:// file for > file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-x86_64 [Couldn't open > file /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-x86_64] > The downloaded packages were saved in cache till the next > successful transaction. > You can remove cached packages by executing 'dnf clean packages'. > > > I'm getting this exact same Curl error (37) trying to do a dnf > system-upgrade. > > Except my warning is about libgudev-230-2.fc23.x86_64.rpm instead > of kernel-core-4.2.5-300.fc23.x86_64.rpm as above. > > Does anyone have a fix?? > > > going from f21 to f23 > > # dnf system-upgrade download --releasever=23 > ... > [SKIPPED] yum-utils-1.1.31-508.fc23.noarch.rpm: Already downloaded > [SKIPPED] zenity-3.18.1.1-1.fc23.x86_64.rpm: Already downloaded > warning: /var/lib/dnf/system-upgrade/libgudev-230-2.fc23.x86_64.rpm: > Header V3 RSA/SHA256 Signature, key ID 34ec9cba: NOKEY > Curl error (37): Couldn't read a file:// file for > file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-x86_64 [Couldn't open file > /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-x86_64] > Looks like a bug in the packaging of those RPMs. They should be specifying: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-23-x86_64 which is a symlink to: /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-23-primary (at least on my system it is). I'd bugzilla those RPMs (the libgudev and kernel-core RPMs). > >

On Fri, Dec 18, 2015 at 10:54 AM, Rick Stevens <ricks(a)alldigital.com <mailto:ricks@alldigital.com>> wrote: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-23-x86_64 which is a symlink to: /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-23-primary I have run into the situation where this symlink still points to the wrong place, which would cause any of the RPMs to fail the check. Look to see if the symlink is actually pointing where it should. I've also seen it try to use /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-x86_64, so check to see that this one points to the correct Fedora version's key. There are clearly some bugs in dnf system-upgrade where setting up the GPG keys isn't done correctly.

That's an issue, but what was scary to me was that the RPM was referencing a file or symlink that did NOT have the Fedora version in it--just "fedora-x86_64" rather than "fedora-23-x86_64". Something like a kernel that doesn't specify the version is a BAD thing (IMHO). In other words, I don't think this is a dnf issue, but rather an RPM packaging error (at least in these two cases).

> On Fri, Nov 6, 2015 at 6:30 AM, Sam Varshavchik > <<URL:mailto:mrsam@courier-mta.com>mrsam@courier-mta.com> wrote: > > One upgrade to F23 succeeded. The second server fails, repeatedly with > "dnf system-upgrade --releasever 23 download" resulting in:

You could use fedup to go from 20->21 and then dnf system-upgrade from there.

Or perhaps it would easier to just backup your data and do a clean F23 install and restore your data instead of upgrading all that way.

Re: Nvidia .... So, why does Nvidia not release their drivers source code to the O. S. community? Seems to me that Unix and Linux Heads should unite and boycott Nvidia and other computer device manufacturers with proprietary drivers (Broadcom comes to mind also).

On 12/18/2015 04:13 PM, Kevin Fenzi wrote: > You could use fedup to go from 20->21 and then dnf system-upgrade from > there. > Every time I've tried fedup on this box I've spent several days at a CLI cleaning things up just to get a GUI. > Or perhaps it would easier to just backup your data and do a clean F23 > install and restore your data instead of upgrading all that way. No working DVD drive, can't boot off of USB. Not an option. And, as I have nVidia graphics, and F23 has trouble with them, I'd rather not right now.

> You can do a netinstall. There needs to be one partition that is not reformatted for this to work.