Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DNF needs to be reprotected #1982

Closed
eclipseo opened this issue Aug 24, 2023 · 5 comments
Closed

DNF needs to be reprotected #1982

eclipseo opened this issue Aug 24, 2023 · 5 comments
Assignees

Comments

@eclipseo
Copy link
Contributor

In 352b174

we unprotected DNF for DNF5 which was supposed to be coming in Fedora 39.

This ship has sailed and it will be delayed until Fedora 40, probably 41.

On Mastodon today, I have seen a user who accidentally removed DNF on his Pi by removing the LXQT group from his minimal installation. It seems safe to revert that change for now and re-enable it at the furthest time possible to avoid these kind of problems. Currently all users are vulnerable to such a problem.

@AdamWill
Copy link
Contributor

Beta FE proposal for F39: https://bugzilla.redhat.com/show_bug.cgi?id=2234628

@eclipseo
Copy link
Contributor Author

eclipseo commented Aug 25, 2023

This affects F37 and F38 too.

@AdamWill
Copy link
Contributor

Yes, but it only needs an FE for F39.

@inknos
Copy link
Contributor

inknos commented Aug 29, 2023

We are addressing the issue with these PRs. Thank you for the reports and for your patience with solving the issues that came from dnf5 being delayed.

rpm-software-management/libdnf#1619
#1983

@inknos
Copy link
Contributor

inknos commented Sep 4, 2023

done upstream. this fix will land in the next fedora release.

@inknos inknos closed this as completed Sep 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants