-
-
Notifications
You must be signed in to change notification settings - Fork 164
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
Remove usage of rpm-ostree #1946
Comments
Would this be as simple as replacing |
dnf is not an alias to dnf5 yet dnf has bindings to rpm-ostree layering mechanisms (not dnf5 yet) Maybe that's something to do in upstream ? Otherwise, probably to wait for upstream to make dnf5 reach feature-parity with rpm-ostree |
Yes, bsherman is testing in his custom image: https://github.com/bsherman/bos/tree/main/build_files We need to methodically replace rpm-ostree calls with dnf5, same with the copr calls. We should probably do it a little bit at a time, we need to ensure that replaced calls pull in the same packages as we're not sure if there's a behavioral difference. |
I'm happy to work on the user-facing scripts, once I've got a local registry setup to test on! |
I've been tinkering with and testing dnf5 for a while. Key items are: - ensuring cliwrap is properly unwound (checked rpm-ostree Rust code) - using normal (not wrapped) binaries, eg for dracut - and the more obvious, replacing "rpm-ostree install" with "dnf5 install", etc Relates: #1946
I've been tinkering with and testing dnf5 for a while. Key items are: - ensuring cliwrap is properly unwound (checked rpm-ostree Rust code) - using normal (not wrapped) binaries, eg for dracut - and the more obvious, replacing "rpm-ostree install" with "dnf5 install", etc Relates: #1946
As you all know,
rpm-ostree
is being "deprecated" in favor ofbootc
and Bluefin should follow that lead, this is just a tracking issue for what I think needs to be done so that we completely do not depend onrpm-ostree
anymoreAfter removing rpm-ostree/moving to fedora-bootc
bootc container lint
to the final build stepsThe text was updated successfully, but these errors were encountered: