It's quite easy to remove dnf5 with dnf5. A Fedora 39+ system then has no package manager. Please ensure dnf5 is marked as protected. Reproducible: Always Steps to Reproduce: 1.# dnf remove dnf5 Actual Results: Transaction Summary: Removing: 32 packages ... [ 3/33] Erasing dnf5-0:5.0.15-3.fc39.x86_64 ... Expected Results: Failed to resolve the transaction: Problem: The operation would result in removing the following protected packages: dnf5 # dnf bash: dnf: command not found # yum bash: yum: command not found
I guess we need to add the "dnf5" package here: https://github.com/rpm-software-management/dnf5/blob/5.0.15/libdnf5/conf/config_main.cpp#L296. The "dnf" is not working now as it is only an alias.
just a +1 here. I noticed the dnf removal issue for the first time today. I've been running rawhide for over a month IIRC. I usually run: sudo dnf5 -y update --allowerasing --best, and it has worked without issues until today. I was able to get things back on track with `rpm -i $DOWNLOADED_DNF_RPM_FILE`
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle. Changing version to 39.
https://github.com/rpm-software-management/dnf5/pull/906 has been merged, which protects DNF 5 from uninstalling itself (without overriding the protected_packages option), but still lets DNF 4 uninstall DNF 5.
FEDORA-2023-a066057708 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-a066057708
FEDORA-2023-a066057708 has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-a066057708` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-a066057708 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-a066057708 has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.