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

Remove usage of rpm-ostree #1946

Open
5 tasks
tulilirockz opened this issue Nov 19, 2024 · 4 comments
Open
5 tasks

Remove usage of rpm-ostree #1946

tulilirockz opened this issue Nov 19, 2024 · 4 comments
Assignees
Labels
enhancement New feature or request help wanted Keep Bluefin alive, dive in!

Comments

@tulilirockz
Copy link
Collaborator

tulilirockz commented Nov 19, 2024

As you all know, rpm-ostree is being "deprecated" in favor of bootc 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 on rpm-ostree anymore

After removing rpm-ostree/moving to fedora-bootc

  • Add bootc container lint to the final build steps
@dosubot dosubot bot added the enhancement New feature or request label Nov 19, 2024
@tulilirockz tulilirockz added the help wanted Keep Bluefin alive, dive in! label Nov 19, 2024
@RealVishy
Copy link
Contributor

Would this be as simple as replacing rpm-ostree with dnf in some of these examples?

@Malix-Labs
Copy link

Malix-Labs commented Nov 19, 2024

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
There are open issues about it in upstrem issue tracker too

@castrojo
Copy link
Member

Would this be as simple as replacing rpm-ostree with dnf in some of these examples?

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.

@RealVishy
Copy link
Contributor

I'm happy to work on the user-facing scripts, once I've got a local registry setup to test on!

bsherman added a commit that referenced this issue Nov 21, 2024
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
bsherman added a commit that referenced this issue Nov 25, 2024
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
bsherman added a commit that referenced this issue Dec 15, 2024
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Keep Bluefin alive, dive in!
Projects
None yet
Development

No branches or pull requests

5 participants