- #FEDORA 23 DNF UPDATE XSCREENSAVER CONFLICTS UPGRADE#
- #FEDORA 23 DNF UPDATE XSCREENSAVER CONFLICTS DOWNLOAD#
It should have been sudo dnf reinstall \* or sudo dnf reinstall '*' so dnf saw the * instead of the current directory content. I made an error in the reinstall command. Qemu-common.x86_64 2:7.0.0-11.fc37 could run the same dnf list installed commands for each of those packages and see what your system tells you before doing anything else. Last metadata expiration check: 0:06:13 ago on Fri 10:03:28 AM CST. Last metadata expiration check: 0:05:40 ago on Fri 10:03:28 AM CST. Last metadata expiration check: 0:05:07 ago on Fri 10:03:28 AM CST. Last metadata expiration check: 0:03:41 ago on Fri 10:03:28 AM CST. Last metadata expiration check: 0:02:34 ago on Fri 10:03:28 AM CST. Last metadata expiration check: 0:08:12 ago on Fri 10:03:28 AM CST. sudo dnf reinstall gettext-libs for Problem 1 and similar for each of the additional noted Problems. One possible fix would be to do a reinstall of each of the listed packages. In all cases it seems to me the rpm database may be out of sync. I listed the packages for each of the noted problems in these segments below.
It may even be possible to remove cinnamon-calendar-server then reinstall it
#FEDORA 23 DNF UPDATE XSCREENSAVER CONFLICTS UPGRADE#
The error was on the cinnamon packages so first do the remaining updates with sudo dnf upgrade -exclude=cinnamon-calendar-server or if that fails sudo dnf upgrade -exclude=cinnamon* so the other packages are updated then work on cinnamon separately. In past versions I never had this problem, but it seems upgrading to version 37 may be more problematic after seeing the number of reported upgrade errors. It may fail and leave you in limbo as the graphical packages are upgraded which may cause a crash in the middle of the upgrade. I had over 2000 fc36 packages that remained to be removed by the distro-sync at that point.ĭo not do a release version upgrade from within a graphical environment!! Once I fixed the errors about the protected packages then the distro-sync for releasever=37 was able to properly complete and the system was fully updated. The ultimate fix was to manually identify the packages that were related to python and dnf that it refused to upgrade then use rpm -e on the fc36 version of those packages after verifying the fc37 version was already installed to remove the need for them to be updated. It turned out that the rpm database showed a lot of f37 packages installed alongside the same F36 packages. dnf distro-sync and dnf distro-sync -releasever=37 both failed with the same messages. I then did a dnf upgrade -releasever=37 which gave me an error because of replacing protected packages.
#FEDORA 23 DNF UPDATE XSCREENSAVER CONFLICTS DOWNLOAD#
I wound up redoing the system-upgrade download steps with no progress. I had to log in to a terminal session (ctrl-alt-F3) then fix the issue. It segfaulted somewhere and the next morning although the reboot worked it was stuck between F36 & F37, having never properly completed. I had a similar error when I upgraded using the dnf system-upgrade method when done in a GUI terminal.
0 kommentar(er)
