I ran sudo dnf offline-upgrade download --refresh in a Fedora 41 KDE installation with updates-testing enabled. The following problem with rpmdistro-repoquery prevented it from being updated. Problem: cannot install the best update candidate for package rpmdistro-repoquery-0^20231102git539d4c0-4.fc41.noarch - nothing provides dnf4 needed by rpmdistro-repoquery-0^20241122git5c26eb4-2.fc41.noarch from updates-testing Reproducible: Always Steps to Reproduce: 1. Boot a Fedora 41 KDE installation with rpmdistro-repoquery installed 2. Log in to Plasma 3. Start Konsole 4. Run sudo dnf offline-upgrade download --refresh with updates-testing enabled in Konsole Actual Results: nothing provides dnf4 needed by rpmdistro-repoquery-0^20241122git5c26eb4-2.fc41.noarch Expected Results: No problem should've happened.
This is a problem in the dnf package, as the dnf4 provides is supposed to be present. Switching to the right package.
dnf package is obsolete by dnf5 <https://fedoraproject.org/wiki/Changes/SwitchToDnf5>. But DNF5 is not DNF4. Hence it does not provide dnf4. rpmdistro-repoquery-0^20231102git539d4c0-4.fc41.noarch should not depend on "dnf4". It should either depend on "dnf5" if it wants DNF5, or on "python3-dnf" if it wants DNF4.
`/usr/bin/dnf4` exists on my request as part of that change to dnf5. All I'm saying is that "dnf4" as a virtual package name should exist too.
(In reply to Neal Gompa from comment #3) > `/usr/bin/dnf4` exists on my request as part of that change to dnf5. Yes. > All I'm saying is that "dnf4" as a virtual package name should exist too. Why? I cannot see any recommendation like that in Fedora packaging guidelines. What does make /usr/bin/dnf4 so special comparing to other /usr/bin/* files? The original bug report is about a wrong dependency. Using python3-dnf, the real package name, is the best the user should do.
(In reply to Petr Pisar from comment #4) > (In reply to Neal Gompa from comment #3) > > `/usr/bin/dnf4` exists on my request as part of that change to dnf5. > > Yes. > > > All I'm saying is that "dnf4" as a virtual package name should exist too. > > Why? I cannot see any recommendation like that in Fedora packaging > guidelines. > > What does make /usr/bin/dnf4 so special comparing to other /usr/bin/* files? > > The original bug report is about a wrong dependency. Using python3-dnf, the > real package name, is the best the user should do. Since we're now being told we shouldn't use file deps, I would like a dnf4 provides.
> Since we're now being told we shouldn't use file deps Where? Who says that?
FEDORA-2025-5c933872b6 (dnf-4.22.0-2.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2025-5c933872b6
FEDORA-2025-0ce22a0a2c (dnf-4.22.0-2.fc40) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2025-0ce22a0a2c
FEDORA-2025-5c933872b6 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-5c933872b6` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-5c933872b6 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-0ce22a0a2c has been pushed to the Fedora 40 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-0ce22a0a2c` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-0ce22a0a2c See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-5c933872b6 (dnf-4.22.0-2.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-0ce22a0a2c (dnf-4.22.0-2.fc40) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.