> On Wed, 18 Oct 2017 09:49:07 -0000 > Marcin Zajączkowski <mszpak(a)wp.pl> wrote: > > > In the man page for yum2dnf, it lists the commands for cleanup as > follows. For your case, it is probably > > dnf repoquery --duplicated > > to find the dups. > > dnf repoquery --unsatisfied > > to find any problems. > > And > > dnf remove $(dnf repoquery --duplicated --latest-limit -1 -q) > > to remove duplicated packages. Thanks for your suggestion. I will try it as the another approach (hopefully it will not be needed) as in the meantime I removed all fc27 packages using "rpm -e $(cat list-of-fc27-packages)" to perform an update once again. However, it resulted in the fact that fc27 packages were removed (only fc26 packages remained), but applications started to complain that there is no gllibc in F26 version (only F27). "rpm -V" reports that files are corrupted. I suspect that "rpm -e" removed newer packages, but as the files were conflicted (and already upgraded to F27 at the filesystem) they remained. I needed to manually reinstall (rpm -U --force) the key packages to bring dnf to life again (e.g. issue with SSL certificated in curl). Do you think that "dnf remove" will be smarted? It would be better to make an upgrade to F27 packages (they are already downloaded and in addition can leverage system-upgrade plugin in chroot mode to do it) ignoring conflicting F26 packages and later on remove old F26 packages. Unfortunately I was able to force dnf to do that (before I manually removed old packages). Marcin _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
