On Fri, Sep 1, 2017 at 3:10 PM, Hedayat Vatankhah <hedayat.fwd@gmail.com> wrote:

Hi,

Igor Gnatenko wrote on Fri, 01 Sep 2017 19:01:49 +0200:
<..>
Do you still have some critical missing functionality in DNF? And let
us know reasons why would you like to keep YUM available (hopefully
there are no)!
I've not tried 'dnf remove --duplicates' yet, but if it behaves similar to 'dnf remove --assumeno $(dnf -C repoquery --duplicated --latest-limit -1 -q)', then there is still no 'sane' way to remove duplicated packages, which might be needed if 'dnf upgrade' is terminated half-way. There is also a RFE at [1] for such scenarios, but it would be enough is 'dnf remove --duplicates' doesn't try to remove other packages as dependencies of duplicated packages, or even better, if 'dnf upgrade' is able to 'sanely' continue a terminated 'dnf upgrade' operation instead of complaining about conflicts and being unable to proceed. Currently, the user must know that the problem is duplicated packages, and learn how to safely remove them without removing other required stuff.

I have to agree here... It happened to me with an upgrade. I got bit by some bug where the screen was blank but the upgrade was actually happening. I didn't see much in the way of disk activity so I force rebooted the machine. It actually booted but I had a bunch of duplicate packages since most of the f26 packages had installed but the f25 (and 24) packages didn't get cleaned up.

I tried using 'dnf repoquery --duplicated > duplicates.log' and then cat'ing that to dnf remove with xargs (grepping for fc25) but it wanted to remove a bunch of dependent packages.

I ended up having the use 'rpm -e --nodeps' to get rid of the duplicate packages and then a 'dnf distro-sync' got me pretty much fixed up.

On a side note, I also updated an old laptop and I did not interrupt the upgrade process but I still ended up with a lot of duplicate packages... Not sure how that happened.

Thanks,

Richard