Description of problem: I found out that when I search for changes performed in a certain package, it doesn't include a system-upgrade transaction I performed lately. Here I list all changes to Zim: $ sudo dnf history Zim ID | Command line | Date and time | Action(s) | Altered -------------------------------------------------------------------------------------------------------- 78 | system-upgrade upgrade | 2022-01-10 08:59 | C, D, E, I, U | 230 < 22 | install ShellCheck Zim ansible | 2021-11-05 13:29 | Install | 20 > But I know for a fact that I upgraded to F36 just last month, which must've changed Zim. I found out that it's transaction 130: $ sudo dnf history | grep 130 130 | system-upgrade upgrade | 2022-04-14 10:59 | C, D, E, I, O, | 2263 >< And of course it changed Zim: $ sudo dnf history info 130 | grep Zim Upgrade Zim-0.74.3-2.fc36.noarch @fedora Upgraded Zim-0.74.3-1.fc35.noarch @@System I can demonstrate the same problem using e.g. gimp: $ sudo dnf history gimp ID | Command line | Date and time | Action(s) | Altered -------------------------------------------------------------------------------------------------------- 83 | system-upgrade upgrade | 2022-01-19 10:17 | C, E, I, U | 61 < 24 | install fd-find fedora-easy-karma fedpkg flatpak- | 2021-11-05 13:32 | Install | 114 > $ sudo dnf history info 130 | grep gimp Upgrade gimp-2:2.10.30-1.fc36.1.x86_64 @fedora Upgraded gimp-2:2.10.30-1.fc35.x86_64 @@System Upgrade gimp-libs-2:2.10.30-1.fc36.1.x86_64 @fedora Upgraded gimp-libs-2:2.10.30-1.fc35.x86_64 @@System So it seems that changes during system-upgrade transactions are not searched properly, when I search for a single package-related changes. Version-Release number of selected component (if applicable): dnf-4.12.0-1.fc36.noarch How reproducible: always, at least in my case Steps to Reproduce: 1. make some transactions 2. perform a system-upgrade to a higher release 3. search "dnf history PKG" and see that PKG transactions are listed in general, but don't contain the system-upgrade transaction (even though PKG update was involved)
Thank you for the report, I did manage to reproduce it in a virtual machine doing a system upgrade from 35 -> 36. Given that this isn't a critical issue we have decided to postpone the fix to dnf5.
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. 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 '36'. 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 36 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.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle. Changing version to 39.