Description of problem: Doing update of my system, grub2-tools-{efi,extra} are installed: ~~~ $ sudo dnf update -x kernel\* Last metadata expiration check: 4:50:42 ago on Sun Apr 25 17:08:54 2021. Dependencies resolved. =============================================================================== Package Arch Version Repo Size =============================================================================== Upgrading: ... snip ... Installing dependencies: grub2-tools-efi x86_64 1:2.06~rc1-6.fc35 rawhide 551 k grub2-tools-extra x86_64 1:2.06~rc1-6.fc35 rawhide 853 k libcloudproviders x86_64 0.3.1-3.fc34 rawhide 46 k Transaction Summary =============================================================================== Install 3 Packages Upgrade 114 Packages Total download size: 294 M Is this ok [y/N]: ~~~ According to the report above, they appears to be required by something. Lets try to exclude them: ~~~ $ sudo dnf update -x kernel\* -x grub2-tools-efi -x grub2-tools-extra Last metadata expiration check: 4:52:46 ago on Sun Apr 25 17:08:54 2021. Dependencies resolved. =============================================================================== Package Arch Version Repo Size =============================================================================== Upgrading: ... snip ... Installing dependencies: libcloudproviders x86_64 0.3.1-3.fc34 rawhide 46 k Transaction Summary =============================================================================== Install 1 Package Upgrade 114 Packages Total download size: 292 M Is this ok [y/N]: ~~~ Interestingly, the transaction is fine. So what requires them? ~~~ $ sudo dnf repoquery --whatdepends grub2-tools-extra Last metadata expiration check: 4:54:30 ago on Sun Apr 25 17:08:54 2021. kiwi-systemdeps-bootloaders-0:9.23.22-1.fc35.x86_64 $ sudo dnf repoquery --whatdepends grub2-tools-efi Last metadata expiration check: 4:54:58 ago on Sun Apr 25 17:08:54 2021. kiwi-systemdeps-bootloaders-0:9.23.22-1.fc35.x86_64 ~~~ Hm, not sure what the kiwi-systemdeps-bootloaders package is, but it does not appear to be part of the transaction. Version-Release number of selected component (if applicable): $ rpm -q dnf dnf-4.6.1-1.fc35.noarch How reproducible: Always Steps to Reproduce: 1. 2. 3. Actual results: grub2-tools-{efi,extra} are mysteriously pulled into the transaction. Expected results: grub2-tools-{efi,extra} are not pulled into the transaction, or it is obvious why they are there. Additional info: The funny thing is that this is the reason, why I don't have these packages on my system: ~~~ $ sudo dnf autoremove Last metadata expiration check: 5:00:33 ago on Sun Apr 25 17:08:54 2021. Dependencies resolved. ============================================================================== Package Arch Version Repository Size ============================================================================== Removing: grub2-tools-efi x86_64 1:2.06~rc1-6.fc35 @rawhide 2.7 M grub2-tools-extra x86_64 1:2.06~rc1-6.fc35 @rawhide 5.3 M Transaction Summary ============================================================================== Remove 2 Packages Freed space: 8.0 M Is this ok [y/N]: ~~~
I consider dnf behavior expected here (not clearly reported in the transaction table though). The thing is that all four packages grup2-tools, grub2-tools-efi, grub2-tools-minimal, and grub2-tools-extras obsolete `grub2-tools < {evr}`package. So in case `grub2-tools` package is part of an upgrade transaction dnf will also install all its "obsoleters" - it's basically a package split. I could reproduce the issue by installing an older version of grub2-tools from koji and then attemting to upgrade the system. # rpm -q grub2-tools grub2-tools-2.06~rc1-5.fc35.x86_64 # dnf list --obsoletes Last metadata expiration check: 1:03:23 ago on Mon Apr 26 06:54:06 2021. Obsoleting Packages grub2-tools.x86_64 1:2.06~rc1-6.fc35 rawhide grub2-tools.x86_64 1:2.06~rc1-5.fc35 @@commandline grub2-tools-efi.x86_64 1:2.06~rc1-6.fc35 rawhide grub2-tools.x86_64 1:2.06~rc1-5.fc35 @@commandline grub2-tools-extra.x86_64 1:2.06~rc1-6.fc35 rawhide grub2-tools.x86_64 1:2.06~rc1-5.fc35 @@commandline grub2-tools-minimal.x86_64 1:2.06~rc1-6.fc35 rawhide grub2-tools.x86_64 1:2.06~rc1-5.fc35 @@commandline # dnf upgrade Last metadata expiration check: 1:09:35 ago on Mon Apr 26 06:54:06 2021. Dependencies resolved. ============================================================================================================================== Package Architecture Version Repository Size ============================================================================================================================== Upgrading: grub2-common noarch 1:2.06~rc1-6.fc35 rawhide 934 k grub2-tools x86_64 1:2.06~rc1-6.fc35 rawhide 1.9 M grub2-tools-minimal x86_64 1:2.06~rc1-6.fc35 rawhide 612 k Installing dependencies: grub2-tools-efi x86_64 1:2.06~rc1-6.fc35 rawhide 551 k grub2-tools-extra x86_64 1:2.06~rc1-6.fc35 rawhide 853 k
(In reply to Marek Blaha from comment #1) Based on your explanation, which makes sense, this should be split into two issues: 1. If they are installed, then they should be marked as installed and should not be removed by "autoremove" 2. The report should make it obvious these are installed on purpose, because they obsolete something. The obsoletes are typically visible in the report, but this one is misreported IMO.
This bug appears to have been reported against 'rawhide' during the Fedora 35 development cycle. Changing version to 35.
This is still occuring on Fedora 36 and Fedora 37 for me.
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. 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 'version' of '35'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
I don't think this was resolved.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 38 development cycle. Changing version to 38.
This message is a reminder that Fedora Linux 38 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 38 on 2024-05-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 'version' of '38'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 38 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
I don't remember to notice this behavior recently, using dnf5. This might or might not be resolved.
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21. Fedora Linux 38 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 Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.