Created attachment 1458996 [details] dnf-autoremove-fail-rep include the autoremove process, reinstall firefox and retry autoremove Description of problem: Info, the whole process of the autoremove is in the attachment document. By using 'dnf autoremove' it show a list of packages they are actually and are not twice. I was confused so I have make a reboot, because directly befor I have updated the system. After the reboot the list was the same, so I done that autoremove. After that process was all listed programs deleted. To try if it ever by the programs of the list which deleted, I reinstall firefox and start 'dnf autoremove' again. Now was the list empty, so it won't delete firefox again. Version-Release number of selected component (if applicable): dnf --version 2.7.5 Installiert: dnf-0:2.7.5-12.fc28.noarch am Di 01 Mai 2018 17:08:06 GMT Built : Fedora Project at Mi 18 Apr 2018 14:29:51 GMT Installiert: rpm-0:4.14.1-9.fc28.x86_64 am Mo 02 Jul 2018 20:27:41 GMT Built : Fedora Project at Do 24 Mai 2018 14:53:48 GMT uname -r 4.17.3-200.fc28.x86_64 How reproducible: I don't no. Actual results: After reinstalling the packages is the list of autoremove empty. Expected results: -- Additional info: The Fedora 28 is a upgrade from 27 and that from 26 and so on. The last autoremove should be on that upgrade from 27 to 28. The big things I do as yet was installing that Qt5-stuff, steam and nvidia. Firefox was installed from begin and for example qt5 I installed directly after the upgrade von Fedora 27 to 28. I see no dependence between the deleted programs. Firefox was installed from the installation ISO and Qt5 installed by my self with dnf.
Thanks for the report. I know that we have a problem with reason of obsoleted packages. I would recommend to you to use "dnf mark install <package>" to mark user installed packages as installed. Even information that reinstall of packages change they reason is strange.
Ok, I tested it with latest dnf (3.6.1) that will be available in f29+, but no issue discovered. I believed that your database was reason information was somehow damage. Please if you will find some additional information about your problem, don't hesitate to reopen the bug report.