-
Notifications
You must be signed in to change notification settings - Fork 198
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
Fix rpm-ostree to handle ostree semver-incompatible changes #4400
Conversation
Skipping CI for Draft Pull Request. |
9fbb835
to
d674b1b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! Thanks so much for doing this! Looks good to me.
So at a technical level right now this blocks on an "official" release of the new ostree-ext crate, which in turn needs to wait until your changes in ostreedev/ostree-rs-ext#456 land at least.
(We may also want to go over the API and see if there are any other possible cleanups)
OK several other changes happened in ostree-ext git main since then, so I've reworked this to match! |
- ostree-ext updates to new ostree, so adjust our usage of the ostree crate - Also adjust for changed ostree-ext APIs - ostree-ext now re-exports cap-std-ext 2.0, which stopped re-exporting rustix, so depend on that directly
This is similar to coreos/rpm-ostree#4400 Signed-off-by: Colin Walters <[email protected]>
We ended up keeping this rolled into #4271 |
Cargo: Override to the main branch of ostree-rs-ext
Fixing ostree semver-incompatible changes