This is a tracking bug for Change: RPM 6.0 For more details, see: https://fedoraproject.org/wiki/Changes/RPM-6.0 Update RPM to the upcoming 6.0 major release. If you encounter a bug related to this Change, please do not comment here. Instead create a new bug and set it to block this bug.
Rpm 6.0 alpha is in rawhide since April 14th.
Dear change owner, this is a reminder that your change is required to be 100% code complete by August 26, which is the start of beta freeze. Please provide a status update on your change in the Incomplete Changes Report if you are not able to move your change to 'ON_QA' before this date. If you need to defer your change to the next Fedora release, please let me know and I will reassign this bug and the change page. Thank you kindly.
We consider it's code complete as of since beta1 in early July. There will be further updates to bring it up to 6.0 final release of course. BUT, there has been a (so far unannounced) scope change in that Fedora 43 will NOT have enforcing signature checking enabled by default despite this being the upstream default. The necessary bits and pieces (in rpm and dnf) landed too late in the cycle for the change, at a time when the team bandwidth is all taken up by PQC matters.
FEDORA-2025-49f58ee388 (rpm-6.0.0-1.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2025-49f58ee388
FEDORA-2025-49f58ee388 has been pushed to the Fedora 43 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-49f58ee388` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-49f58ee388 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-49f58ee388 (rpm-6.0.0-1.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.