[SOLVED] DNF system upgrade error report after completion?

zavmat · 01-25-2019, 06:08 PM

I'm running Fedora 22 and trying to upgrade to the latest kernal (did I use that right?). I'm following the instructions here: https://fedoraproject.org/wiki/DNF_s...tem_upgrade.3F
I did step 4 and this was the result:

[matt@localhost /]$ sudo dnf install dnf-plugin-system-upgrade
[sudo] password for matt:
Last metadata expiration check performed 0:39:27 ago on Fri Jan 25 15:42:48 2019.
Dependencies resolved.
================================================================================
Package Arch Version Repository
Size
================================================================================
Installing:
dnf-plugin-system-upgrade noarch 0.7.1-1.fc22 updates 49 k
python2-dnf-plugin-system-upgrade noarch 0.7.1-1.fc22 updates 31 k

Transaction Summary
================================================================================
Install 2 Packages

Total download size: 80 k
Installed size: 182 k
Is this ok [y/N]: y
Downloading Packages:
(1/2): python2-dnf-plugin-system-upgrade-0.7.1- 137 kB/s | 31 kB 00:00
(2/2): dnf-plugin-system-upgrade-0.7.1-1.fc22.n 177 kB/s | 49 kB 00:00
--------------------------------------------------------------------------------
Total 86 kB/s | 80 kB 00:00
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Installing : python2-dnf-plugin-system-upgrade-0.7.1-1.fc22.noarch 1/2
Installing : dnf-plugin-system-upgrade-0.7.1-1.fc22.noarch 2/2
Verifying : dnf-plugin-system-upgrade-0.7.1-1.fc22.noarch 1/2
Verifying : python2-dnf-plugin-system-upgrade-0.7.1-1.fc22.noarch 2/2

Installed:
dnf-plugin-system-upgrade.noarch 0.7.1-1.fc22
python2-dnf-plugin-system-upgrade.noarch 0.7.1-1.fc22

Complete!
[matt@localhost /]$ sudo dnf system-upgrade download --refresh --releasever=29
Fedora 29 - x86_64 246 kB/s | 62 MB 04:20
Fedora 29 - x86_64 - Updates 183 kB/s | 20 MB 01:54
Last metadata expiration check performed 0:01:26 ago on Fri Jan 25 16:30:36 2019.
Error: package python-libs-2.7.10-10.fc22.x86_64 requires libgdbm.so.4()(64bit), but none of the providers can be installed.
package abrt-addon-python-2.6.1-10.fc22.x86_64 requires abrt = 2.6.1-10.fc22, but none of the providers can be installed.
package abrt-python-2.6.1-10.fc22.x86_64 requires abrt = 2.6.1-10.fc22, but none of the providers can be installed.
package devassistant-cli-0.11.2-1.fc22.noarch requires python(abi) = 3.4, but none of the providers can be installed.
package devassistant-core-0.11.2-1.fc22.noarch requires python(abi) = 3.4, but none of the providers can be installed.
package libhif-0.2.0-5.fc22.x86_64 requires librpm.so.3()(64bit), but none of the providers can be installed.
package libreport-python-2.6.4-1.fc22.x86_64 requires libreport = 2.6.4-1.fc22, but none of the providers can be installed.
package devassistant-gui-0.11.2-1.fc22.noarch requires python(abi) = 3.4, but none of the providers can be installed.
package python3-dapp-0.3.0-1.fc22.noarch requires python(abi) = 3.4, but none of the providers can be installed.
package devassistant-0.11.2-1.fc22.noarch requires devassistant-cli = 0.11.2-1.fc22, but none of the providers can be installed.
package python3-3.4.2-8.fc22.x86_64 requires python3-libs(x86-64) = 3.4.2-8.fc22, but none of the providers can be installed.
package devassistant-dap-c-0.11-1.fc22.noarch requires devassistant-dap-vim, but none of the providers can be installed.
package devassistant-dap-cpp-0.11-1.fc22.noarch requires devassistant-dap-vim, but none of the providers can be installed.
package devassistant-dap-nodejs-0.11-1.fc22.noarch requires devassistant-dap-vim, but none of the providers can be installed.
package devassistant-dap-perl-0.11-1.fc22.noarch requires devassistant-dap-vim, but none of the providers can be installed.
package devassistant-dap-php-0.11-1.fc22.noarch requires devassistant-dap-vim, but none of the providers can be installed.
package devassistant-dap-python-0.11-1.fc22.noarch requires devassistant-dap-vim, but none of the providers can be installed.
package devassistant-dap-ruby-0.11-1.fc22.noarch requires devassistant-dap-vim, but none of the providers can be installed.
package devassistant-dap-devassistant-0.11-1.fc22.noarch requires devassistant-dap-python, but none of the providers can be installed.
package python3-3.4.2-8.fc22.x86_64 requires python3-libs(x86-64) = 3.4.2-8.fc22, but none of the providers can be installed.
package python3-3.4.2-8.fc22.x86_64 requires python3-libs(x86-64) = 3.4.2-8.fc22, but none of the providers can be installed.
package python3-3.4.2-8.fc22.x86_64 requires python3-libs(x86-64) = 3.4.2-8.fc22, but none of the providers can be installed.
package devassistant-dap-custom-0.10.0-7.fc22.noarch requires devassistant-dap-github, but none of the providers can be installed.
package devassistant-dap-dap-1.3-1.fc22.noarch requires devassistant-dap-github, but none of the providers can be installed.
package python3-3.4.2-8.fc22.x86_64 requires python3-libs(x86-64) = 3.4.2-8.fc22, but none of the providers can be installed.
package python3-3.4.2-8.fc22.x86_64 requires python3-libs(x86-64) = 3.4.2-8.fc22, but none of the providers can be installed.
package python3-3.4.2-8.fc22.x86_64 requires python3-libs(x86-64) = 3.4.2-8.fc22, but none of the providers can be installed.
package python3-3.4.2-8.fc22.x86_64 requires python3-libs(x86-64) = 3.4.2-8.fc22, but none of the providers can be installed
(try to add '--allowerasing' to command line to replace conflicting packages)

I'm worried about doing the --allowerasing command with so many unsatisfied dependencies.

Thanks in advance

snowday · 01-25-2019, 06:22 PM

You are getting these errors because Fedora 22 is unsupported since 2016.

My suggestion is to install the currently supported Fedora 29. (Or, get off the "upgrade every 6 months" treadmill and move to a distro with a slower release cycle.)

Or, you can try to upgrade from 22 to 29 experimentally, at your own risk (upgrading across more than two releases is not supported). If you have nothing to lose (there is no important data, and you don't need the computer for productivity) then it might be a fun experiment.

Quote:

�� Can I upgrade from an End of life release?

Note that Fedora strongly recommends against ever running an end-of-life release on any production system, or any system connected to the public internet, in any circumstances. You should never allow a production Fedora deployment to reach end-of-life in the first place.

With that in mind, if you do have an end-of-life release newer than Fedora 20 installed on a system you cannot just discard or re-deploy, you can attempt to upgrade it, though this is a less-tested and less-supported operation. You can try to upgrade through intermediate releases until you reach a currently-supported release, or try to upgrade to a currently-supported release in a single operation. It is not possible to state with certainty which approach is more likely to be successful.

If you attempt to upgrade across more than two releases in one operation, please also read the next answer.

If you have Fedora 20 or earlier installed, you cannot upgrade with DNF system upgrade alone. You must upgrade at least part of the way using bare dnf or yum. You can either upgrade to Fedora 21 that way and then upgrade the rest of the way using DNF system upgrade, or you can attempt the entire upgrade using bare dnf or yum. Note this method is in itself not an officially recommended upgrade mechanism. To be frank, any upgrade from Fedora 20 or earlier is very much done 'at your own risk'.

�� How many releases can I upgrade across at once?

The most common scenario is an upgrade across just one release (e.g. Fedora 28 to Fedora 29). However, for the first month or so after a new release comes out, upgrades from the last-but-one release to that release are 'supported', in the sense that we include this scenario in the Fedora Release Criteria, test it for at least clean installs of supported package sets, and will treat bugs discovered in such upgrades as significant. The Fedora Release Life Cycle is specifically designed to provide this approximate one month 'grace period' so you can choose to upgrade long-lived systems only once every two releases, rather than having to do it every release.

Around a month after the new release comes out, the last-but-one release goes End of life, at which point the previous question applies. Still, that upgrade is still pretty likely to work successfully for some time after the release goes end-of-life.

Upgrades across more than two releases are not 'supported', and issues encountered in such upgrades may not be considered significant bugs. Note that any upgrade across more than two releases must by definition be an upgrade from an end-of-life release, and so the previous question applies here too.

When upgrading across multiple releases, you may find you need to import the target release package signing key manually. Fedora releases usually only have the package signing keys for the next two releases installed (because they go end-of-life before the N+3 release is branched). Before Fedora 22, it was not consistently the case that every release had keys for the next two releases, either. If dnf complains about a missing key, this is what you must do.

PS The terminal output you copy & pasted starts at Step 3 of the instructions. Make sure you didn't skip Steps 1 and 2; they are both very important. Make sure you read the entire document, start to finish, including the FAQ's.

syg00 · 01-25-2019, 06:50 PM

Rescuing failed upgrades (in any distro) ceased being a "fun experiment" over a decade ago.
Do yourself a favour before you go any further - create a separate partition for your /home, and get that working first (on your current setup). Then do a F29 install keeping your /home, and create the same user(s)/password(s). You will have to re-install packages, but that generally isn't too much of a pain - dnf will even give you a list from your current system.

As a side note, the dnf system-upgrade is so much a better tool than everything that went before - I have yet to have one fail, but I certainly wouldn't try it across a gap that large.

zavmat · 01-25-2019, 08:57 PM

Where am I now in the installation process? As is am I in limbo with some aspects of 29 installed? Is it possible to remove Linux from my system and just install another version? I have a bunch of disks that were given to me, the one that I used to install fedora just says "Fedora Live OS x86.64" I'm familiar with computers but this is all one big experiment. This laptop has some issues that made it virtually unusable in windows 10, but Fedora more or less fixed them. After partitioning the disk is it possible to undo all that and start over?

Also, thanks for your help, I'm amazed at how responsive this community is.

snowday · 01-25-2019, 09:34 PM

Let's try baby steps and go to Fedora 23 instead of 29.

Code:

sudo dnf upgrade --refresh
sudo dnf system-upgrade download --refresh --releasever=23

syg00 · 01-25-2019, 09:45 PM

If this is just an experiment machine, simply pick another DVD and install that. It will offer to delete everything and install itself, just like Fedora did initially. Would be better to try and get something more current to start with though.

snowday · 01-25-2019, 09:51 PM

Quote:

Originally Posted by zavmat

Is it possible to remove Linux from my system and just install another version?

YES! If you want to wipe it (all your data is backed up) then you should totally just start fresh with a different Linux distribution or "distro."

You can make a Linux live USB or DVD from Windows, Mac OS, or Linux. In Fedora you can do this with Fedora Media Writer (installable through Fedora's Software application). Reboot your computer from your newly-created live USB or DVD. Test drive it for a while (in "live" or "try without installing" mode) to make sure you like it and it's compatible with your hardware. When you are ready to install, the default for most distros is to wipe the entire drive and install that Linux as the only operating system. (If you'd rather install side-by-side with an existing operating system, there is usually an option to do that instead.)

My recommendation is to test-drive Fedora 29 and/or Linux Mint 19.1. Or for older hardware especially, Antix is well worth a look. These are three personal favorite distros of mine. But the choice is yours. Visit www.distrowatch.com for a long list.

zavmat · 01-25-2019, 09:58 PM

Alright the ETA is 15 minutes

zavmat · 01-26-2019, 12:16 AM

Alright the upgrade to 23 worked. I'm assuming if I input sudo dnf system-upgrade download --refresh --releasever=24 it will upgrade to 24, and so on until 29.

I like the idea of just burning 29 to a CD (if that is big enough?) and installing it over the current build though, it just seems like it would be much faster.

About the command for the upgrade, how does the system find the right files to download from the internet, what site is it getting it from, the initial site?

Thanks!

snowday · 01-26-2019, 09:58 AM

The Fedora 29 installer is about 1.8gb. So it won't fit on a CD. You will need a DVD or a 2gb+ USB thumb drive. (I recommend the thumb drive method.)

Your "repositories" (the URL's from which Fedora downloads its software packages) are defined by the config files in /etc/yum/repos.d (for example /etc/yum/repos.d/fedora.repo is the main one).

zavmat · 01-26-2019, 09:28 PM

That brings me to another question, I can't figure out how to change to the computer directory where etc. is located. The files browser works fine, but I want to learn how to use the terminal more effectively. Edit. I have the Fedora-Workstation-live-x86_64-29-1.2.iso and a usb that's big enough for it, I just need to mount it.