I’ve just dnf system-upgrad
ed from F28 to F30. The upgrade process completed without errors and rebooted the system, and now /etc/fedora-release
shows that I’m running F30. Yay! But out of 3842 packages installed on the system, over 1000 of them are still stuck at the .f28
version.
There was some sort of conflict between the readline-7.0 and readline-8.0 packages; I was able to resolve that by explicitly removing the existing packages with rpm -e --nodeps
and then running yum install readline
, and a dnf upgrade
after that brought the number of .f28
packages down to 900.
Running dnf upgrade --refresh
results in:
Problem 1: cannot install both coreutils-8.31-2.fc30.x86_64 and coreutils-8.29-7.fc28.x86_64
- package jdk-10.0.1-2000:10.0.1-ga.x86_64 requires /bin/basename, but none of the providers can be installed
- cannot install the best update candidate for package coreutils-8.29-7.fc28.x86_64
- problem with installed package jdk-10.0.1-2000:10.0.1-ga.x86_64
Problem 2: package ekiga-4.0.1-42.fc29.x86_64 requires libboost_signals.so.1.66.0()(64bit), but none of the providers can be installed
- package boost-1.69.0-8.fc30.x86_64 obsoletes boost-signals < 1.69.0 provided by boost-signals-1.66.0-8.fc28.x86_64
- cannot install the best update candidate for package ekiga-4.0.1-42.fc29.x86_64
- cannot install the best update candidate for package boost-1.66.0-8.fc28.x86_64
Problem 3: cannot install both python2-matplotlib-data-2.2.4-1.fc30.noarch and python2-matplotlib-data-2.2.4-2.fc30.noarch
- cannot install the best update candidate for package python2-matplotlib-data-2.2.4-2.fc30.noarch
- cannot install the best update candidate for package python-matplotlib-data-2.2.3-1.fc28.noarch
Problem 4: cannot install both python2-matplotlib-data-fonts-2.2.4-1.fc30.noarch and python2-matplotlib-data-fonts-2.2.4-2.fc30.noarch
- cannot install the best update candidate for package python2-matplotlib-data-fonts-2.2.4-2.fc30.noarch
- cannot install the best update candidate for package python-matplotlib-data-fonts-2.2.3-1.fc28.noarch
Problem 5: cannot install both python3-3.7.3-3.fc30.x86_64 and python3-3.6.8-3.fc28.x86_64
- package watchman-python3-4.9.0-2.fc27.x86_64 requires python(abi) = 3.6, but none of the providers can be installed
- cannot install the best update candidate for package python3-3.6.8-3.fc28.x86_64
- problem with installed package watchman-python3-4.9.0-2.fc27.x86_64
Problem 6: package sflphone-daemon-1.4.1-32.fc29.x86_64 requires libccrtp.so.0()(64bit), but none of the providers can be installed
- cannot install both ccrtp-2.1.2-2.fc30.x86_64 and ccrtp-2.0.5-18.fc28.x86_64
- cannot install the best update candidate for package sflphone-daemon-1.4.1-32.fc29.x86_64
- cannot install the best update candidate for package ccrtp-2.0.5-18.fc28.x86_64
Problem 7: package watchman-python3-4.9.0-2.fc27.x86_64 requires python(abi) = 3.6, but none of the providers can be installed
- package python3-devel-3.7.3-3.fc30.x86_64 conflicts with python3 < 3.7.3-3.fc30 provided by python3-3.6.8-3.fc28.x86_64
- cannot install the best update candidate for package watchman-python3-4.9.0-2.fc27.x86_64
- cannot install the best update candidate for package python3-devel-3.6.8-3.fc28.x86_64
Problem 8: package coreutils-8.29-7.fc28.x86_64 requires coreutils-common = 8.29-7.fc28, but none of the providers can be installed
- cannot install both coreutils-common-8.31-2.fc30.x86_64 and coreutils-common-8.29-7.fc28.x86_64
- package jre-1.7.0_80-fcs.x86_64 requires /bin/basename, but none of the providers can be installed
- cannot install the best update candidate for package coreutils-common-8.29-7.fc28.x86_64
- problem with installed package jre-1.7.0_80-fcs.x86_64
Problem 9: problem with installed package ekiga-4.0.1-42.fc29.x86_64
- package ekiga-4.0.1-42.fc29.x86_64 requires libboost_signals.so.1.66.0()(64bit), but none of the providers can be installed
- package boost-1.69.0-8.fc30.x86_64 obsoletes boost-signals < 1.69.0 provided by boost-signals-1.66.0-8.fc28.x86_64
- cannot install the best update candidate for package boost-signals-1.66.0-8.fc28.x86_64
Problem 10: package sflphone-gnome-1.4.1-32.fc29.x86_64 requires sflphone-daemon(x86-64) = 1.4.1-32.fc29, but none of the providers can be installed
- package sflphone-daemon-1.4.1-32.fc29.x86_64 requires libccrtp.so.0()(64bit), but none of the providers can be installed
- cannot install both ccrtp-2.1.2-2.fc30.x86_64 and ccrtp-2.0.5-18.fc28.x86_64
- package libzrtpcpp-4.6.6-7.fc30.x86_64 requires libccrtp.so.3()(64bit), but none of the providers can be installed
- cannot install the best update candidate for package sflphone-gnome-1.4.1-32.fc29.x86_64
- cannot install the best update candidate for package libzrtpcpp-4.6.6-5.fc28.x86_64
Problem 11: package sflphone-common-1.4.1-32.fc29.noarch requires sflphone-daemon = 1.4.1-32.fc29, but none of the providers can be installed
- package sflphone-daemon-1.4.1-32.fc29.x86_64 requires libccrtp.so.0()(64bit), but none of the providers can be installed
- cannot install both ccrtp-2.1.2-2.fc30.x86_64 and ccrtp-2.0.5-18.fc28.x86_64
- package twinkle-1.10.2-2.fc30.x86_64 requires libccrtp.so.3()(64bit), but none of the providers can be installed
- cannot install the best update candidate for package twinkle-1.10.1-7.fc28.x86_64
- cannot install the best update candidate for package sflphone-common-1.4.1-32.fc29.noarch
- nothing provides libccrtp.so.0 needed by sflphone-daemon-1.4.1-32.fc29.i686
Problem 12: package python2-matplotlib-2.2.4-2.fc30.x86_64 requires python2-matplotlib-data = 2.2.4-2.fc30, but none of the providers can be installed
- cannot install both python2-matplotlib-data-2.2.4-1.fc30.noarch and python2-matplotlib-data-2.2.4-2.fc30.noarch
- problem with installed package python-matplotlib-data-2.2.3-1.fc28.noarch
- package python3-matplotlib-data-3.0.3-1.fc30.noarch obsoletes python-matplotlib-data < 2.2.3-2 provided by python-matplotlib-data-2.2.3-1.fc28.noarch
- package python3-matplotlib-3.0.3-1.fc30.x86_64 requires python3-matplotlib-data = 3.0.3-1.fc30, but none of the providers can be installed
- cannot install the best update candidate for package python3-matplotlib-2.2.3-1.fc28.x86_64
- cannot install the best update candidate for package python2-matplotlib-2.2.4-2.fc30.x86_64
Problem 13: problem with installed package python2-matplotlib-data-fonts-2.2.4-2.fc30.noarch
- cannot install both python2-matplotlib-data-fonts-2.2.4-1.fc30.noarch and python2-matplotlib-data-fonts-2.2.4-2.fc30.noarch
- problem with installed package python-matplotlib-data-fonts-2.2.3-1.fc28.noarch
- package python-matplotlib-data-fonts-2.2.3-1.fc28.noarch requires python-matplotlib-data = 2.2.3-1.fc28, but none of the providers can be installed
- package python3-matplotlib-data-3.0.3-1.fc30.noarch obsoletes python-matplotlib-data < 2.2.3-2 provided by python-matplotlib-data-2.2.3-1.fc28.noarch
- package python3-matplotlib-3.0.3-1.fc30.x86_64 requires python3-matplotlib-data = 3.0.3-1.fc30, but none of the providers can be installed
- package mu-1.0.2-1.fc30.noarch requires python3.7dist(matplotlib) >= 2.2, but none of the providers can be installed
- cannot install the best update candidate for package mu-0.9.13-2.fc28.noarch
I imagine some of this is due to packages from third-party repositories, but is there any easy way to clean it up? Can I ask dnf
to remove conflicting packages, rather than letting them block the upgrade?