Created attachment 973850 [details] Full yum output Description of problem: "yum autoremove" command wants to remove all installed kernels, grub2 and some other packages. Version-Release number of selected component (if applicable): Fedora 21 kernel 3.17.7-300.fc21.x86_64, yum 3.4.3-153.fc21 Steps to Reproduce: 1. In terminal run "sudo yum autoremove" Actual results: ================================================================================ Package Arch Version Repository Size ================================================================================ Removing: filezilla x86_64 3.9.0.6-1.fc21 @updates 14 M gedit x86_64 2:3.14.2-1.fc21 @updates 13 M grub2 x86_64 1:2.02-0.13.fc21 @updates 16 M grub2-efi x86_64 1:2.02-0.13.fc21 @updates 4.5 M gstreamer1-libav x86_64 1.4.3-1.fc21 @rpmfusion-free 7.4 M gstreamer1-plugins-bad-freeworld x86_64 1.4.3-1.fc21 @rpmfusion-free 493 k gstreamer1-plugins-ugly x86_64 1.4.3-1.fc21 @rpmfusion-free 743 k kernel x86_64 3.17.4-302.fc21 @updates 0.0 kernel x86_64 3.17.6-300.fc21 @updates 0.0 kernel x86_64 3.17.7-300.fc21 @updates 0.0 libreoffice-emailmerge x86_64 1:4.3.4.1-10.fc21 @updates 57 k lohit-assamese-fonts noarch 2.91.1-1.fc21 @updates 141 k lohit-bengali-fonts noarch 2.91.1-1.fc21 @updates 141 k lohit-tamil-fonts noarch 2.91.1-1.fc21 @updates 58 k pyxdg noarch 0.25-5.fc21 @updates 326 k qemu-guest-agent x86_64 2:2.1.2-7.fc21 @updates 351 k Removing for dependencies: grub2-tools x86_64 1:2.02-0.13.fc21 @updates 35 M kernel-core x86_64 3.17.4-302.fc21 @updates 40 M kernel-core x86_64 3.17.6-300.fc21 @updates 40 M kernel-modules x86_64 3.17.4-302.fc21 @updates 17 M kernel-modules x86_64 3.17.6-300.fc21 @updates 17 M kernel-modules x86_64 3.17.7-300.fc21 @updates 17 M libmpg123 x86_64 1.19.0-2.fc21 @rpmfusion-free 433 k os-prober x86_64 1.58-11.fc21 @koji-override-0/$releasever 99 k wxBase3 x86_64 3.0.2-2.fc21 @fedora 3.4 M wxGTK3 x86_64 3.0.2-2.fc21 @fedora 21 M Transaction Summary ================================================================================ Remove 16 Packages (+10 Dependent packages) Installed size: 249 M Is this ok [y/N]: n Expected results: Not including kernel*, grub2* and filezilla packages. Filezilla was installed through Software App, so was one update (it was about two kernel updates ago, normally I use "sudo yum upgrade" to update my system)
I tried uninstalling Filezilla and installing it again. "yumdb info filezilla" shows "reason = dep" for Software-installed package, "reason = user" for yum installed package. All kernels are also "reason = dep" although they were installed through yum.
I can replicate this - package installed through yum shows 'reason = user', but same package installed through apper shows 'reason = dep', as well as having some other information missing from the yumdb. yum install kate-pate <snip> yumdb info kate-pate Loaded plugins: langpacks kate-pate-4.14.3-1.fc21.x86_64 checksum_data = 1118003d1eb837e1fcfe95f72dfc06e5da8ea3d38e3a1cbbf17d3553e46d5531 checksum_type = sha256 command_line = install kate-pate from_repo = fedora from_repo_revision = 1417769625 from_repo_timestamp = 1417770121 installed_by = 1000 origin_url = http://fedora.mirror.uber.com.au/fedora/linux/development/21/x86_64/os/Packages/k/kate-pate-4.14.3-1.fc21.x86_64.rpm reason = user releasever = 21 yum erase kate-pate <snip> *install with apper* yumdb info kate-pate Loaded plugins: langpacks kate-pate-4.14.3-1.fc21.x86_64 from_repo = fedora installed_by = 0 reason = dep releasever = 21
reinstalling with yum (`yum reinstall <package>`) updates the yumdb with missing information (including the install reason)
Any of the yum developers had a look at this? It makes autoremove very dangerous to use. Pretty much to the point of making it useless.
(In reply to Pierre Ossman from comment #4) > Any of the yum developers had a look at this? It makes autoremove very > dangerous to use. Pretty much to the point of making it useless. I don't think so and it is unlikely anyone will take a look. Since dnf is going to replace yum soon, almost all our effort is focused there.
This seems to be a problem with dnf as well. I also noticed that packages updated using gnome-software are candidates for autoremove where as packages installed from the command line do the right thing. This problem was never resolved in Fedora 22. Now that I fixed up my packages through reinstall I don't have any exact examples but I'll provide an update when it does happen again.
I just did a normal "Restart & Install" update in gnome-software and now I see the following: $ sudo dnf autoremove Last metadata expiration check performed 0:05:46 ago on Thu Jun 25 17:52:38 2015. Dependencies resolved. ================================================================================ Package Arch Version Repository Size ================================================================================ Removing: dracut-config-rescue x86_64 041-14.fc22 @System 3.9 k evince x86_64 3.16.1-2.fc22 @System 9.1 M evince-browser-plugin x86_64 3.16.1-2.fc22 @System 73 k evince-nautilus x86_64 3.16.1-2.fc22 @System 19 k rpm-sign x86_64 4.12.0.1-11.fc22 @System 13 k Transaction Summary ================================================================================ Remove 5 Packages Installed size: 9.3 M Is this ok [y/N]: n Operation aborted. Before updating "dnf autoremove" showed nothing. I've also noticed that gnome-software shows that there are updates while "dnf update" does not unless I clean the cache and refresh it. I get notifications for updates almost every time I boot up (about once per day). Probably all related to how gnome-software works with the package backend.
I can confirm what Eric Work is experiencing on Fedora 22. DNF attempts to remove a whole bunch of packages such as LibreOffice and Google Chrome. LibreOffice was installed by default and Google Chrome was installed via Gnome Software.
I should add that LibreOffice did get updates via Gnome Software so that might be why its being listed in autoremove.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.