On 5/1/19 8:08 PM, SternData wrote:
Wait a day or ???
No. Take note of the errors, then do as suggested. Add --allowerasing and --skip-broken
to the update commands.
Then take note of what was erased and/or skipped and deal with them after the upgrade.
I've had issues like that in the past and they are fairly easy to overcome after the
upgrade.
Problem 1: package python2-hawkey-0.31.0-2.fc29.x86_64 requires
libdnf(x86-64) = 0.31.0-2.fc29, but none of the providers can be installed
- libdnf-0.31.0-2.fc29.x86_64 does not belong to a distupgrade repository
- problem with installed package python2-hawkey-0.31.0-2.fc29.x86_64
Problem 2: package system-config-services-0.111.4-2.fc24.noarch
requires python-slip >= 0.1.11, but none of the providers can be installed
- python2-slip-0.6.4-12.fc29.noarch does not belong to a distupgrade
repository
- problem with installed package
system-config-services-0.111.4-2.fc24.noarch
Problem 3: problem with installed package
system-config-firewall-1.2.29-21.fc29.noarch
- package system-config-firewall-1.2.29-21.fc29.noarch requires
python2-slip-dbus >= 0.2.7, but none of the providers can be installed
- python2-slip-dbus-0.6.4-12.fc29.noarch does not belong to a
distupgrade repository
Problem 4: package python3-hawkey-0.28.1-1.fc30.x86_64 requires
libdnf(x86-64) = 0.28.1-1.fc30, but none of the providers can be installed
- cannot install both libdnf-0.28.1-1.fc30.x86_64 and
libdnf-0.31.0-2.fc29.x86_64
- problem with installed package python3-hawkey-0.31.0-2.fc29.x86_64
- package python2-libdnf-0.31.0-2.fc29.x86_64 requires libdnf(x86-64)
= 0.31.0-2.fc29, but none of the providers can be installed
- python3-hawkey-0.31.0-2.fc29.x86_64 does not belong to a distupgrade
repository
- problem with installed package python2-libdnf-0.31.0-2.fc29.x86_64
(try to add '--allowerasing' to command line to replace conflicting
packages or '--skip-broken' to skip uninstallable packages)
--
Right: I dislike the default color scheme Wrong: What idiot picked the default color
scheme