On Jan 12, 2017 7:42 PM, "Paolo Galtieri" <pgaltieri@xxxxxxxxx> wrote:
>
> I decided today to upgrade one of my systems to F25. I upgraded 2 others a few weeks ago to F25 without issues. On this system, however, after it downloads all the packages I get this error:
>
> warning: /var/lib/dnf/system-upgrade/adobe-source-han-sans-tw-fonts-1.004-3.fc24.noarch.rpm: Header V3 RSA/SHA256 Signature, key ID fdb19c98: NOKEY
> Curl error (37): Couldn't read a file:// file for file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-25-x86_64 [Couldn't open file /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-25-x86_64]
> The downloaded packages were saved in cache until the next successful transaction.
> You can remove cached packages by executing 'dnf clean packages'.
>
> I tried the download twice with the same error.
>
> If I try to run:
>
> sudo dnf system-upgrade reboot
>
> I get:
>
> Error: system is not ready for upgrade
>
> I'm upgrading from F22. Here are the steps I followed:
>
The day after Fedora 25 was released I also tried to upgrade my laptop from fc22 to fc25, but I had some errors messages when dnf tried to solve some dependencies related to Python.
So then tried upgrading to fc23, the process what smooth and without issues. So upgrading from this old EOLifed version to the close its closest release is possible, if no, try upgrading to the closest stable release which is fc24.
Porfirio.
> sudo dnf upgrade --refresh
>
> sudo dnf install dnf-plugin-system-upgrade
>
> sudo dnf system-upgrade download --allowerasing --refresh --releasever=25
>
> sudo dnf system-upgrade reboot
>
> It appears the package:
>
> fedora-repos-25-1.noarch
>
> is not getting installed.
>
> Anyone know what I should do next?
>
> Any help is appreciated.
>
> Paolo
> _______________________________________________
> users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
