On Sun, Aug 06, 2017 at 10:33:49AM +0100, Russel Winder wrote: > If there are one or two I remove the newest version manually and then > do the upgrade again. For 835 I am not about to even start this > process. "dnf remove --duplicates" refused to work because some of the > duplicates were protected. dnf and systemd in particular. OK so I can > handle doing those manually using the "--setopt=protected_package=" > options so as to be able to remove the newest version. So dnf and > systemd fully up to date. I think this is a bug. The protected-packages thing shouldn't block dupes from being removed, just make sure there's at least one functional package (of the primary architecture!). > I am thinking that "dnf remove --duplicates" isn't actually the right > way of fixing this sort of problem, that there is a better way of > handling barfed upgrades. I think `dnf distro-sync` should do it. -- Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> Fedora Project Leader _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
