dnf5 offers offline upgrades: sudo dnf5 upgrade --offline sudo dnf5 offline reboot However, doing this makes the upgraded packages lose their "From repository" metadata which is then replaced with the useless generic "@stored_transaction". At this point, the user than has to resort to other methods like "dnf info --available <packagename>" to find what repository that package likely came from. However even that might not be correct due to repository changes between the time of the offline transaction and the "dnf info --available...." was run. Expectation: Upgrading packages directly or offline should have the same result as far as the DNF database package metadata. Reproducible: Always Steps to Reproduce: 1. Use "dnf upgrade --offline" to safely upgrade 2. Use "dnf offline reboot" 3. use "dnf list --installed <package>" or "dnf history info <last-#>" Actual Results: All "From repository" information was lost for the packages upgraded offline by getting set to "@stored_transaction" Expected Results: All "From repository" information labels should be available in the same way for either offline or direct upgrades so packages can be tracked. I suspect the "@stored_transaction" is stuck in for the From repository label because the dnf general design makes it difficult to retain that information.
This is not that big of a deal, lowered to "low"
I see the repo information for each package is already in the /usr/lib/sysimage/libdnf5/offline/transaction.json file in the "repo_id" tags.
Could tell us what dnf5 version did you use for executing the offline upgrade? Be ware that it could be a previous version from what you have installed after the upgrade.
This as a known bug upstream <https://github.com/rpm-software-management/dnf5/issues/1851>.
> Could tell us what dnf5 version did you use for executing the offline upgrade? dnf5-5.2.10.0-2.fc42.x86_64
FEDORA-2025-823f6cb22a (dnf5-5.2.11.0-1.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-823f6cb22a
FEDORA-2025-823f6cb22a has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-823f6cb22a` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-823f6cb22a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-edc76bfa6e (dnf5-5.2.11.0-1.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2025-edc76bfa6e
FEDORA-2025-edc76bfa6e has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-edc76bfa6e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-edc76bfa6e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-edc76bfa6e (dnf5-5.2.11.0-1.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2025-823f6cb22a (dnf5-5.2.11.0-1.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.