Pull ostree from forky: bootc needs libostree >= 2025.3 #1
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/ostree-2025.3"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
CI run 1 failed in the builder stage:
Every recent bootc release (checked back to v1.10.0) builds ostree-ext with the
v2025_3crate feature, so pinningBOOTC_REFolder is not an option. trixie ships ostree 2025.2; forky/sid ship 2025.7.Fix:
build/ostree-forky.shadds a forky apt source pinned to priority 100 globally, with only the ostree binary packages raised to 990. It runs in both stages — the builder needslibostree-dev>= 2025.3 to compile, and the runtime image needs the matchinglibostree-1.so.1for the bootc binary to load.Possible follow-up risk: if forky's ostree 2025.7 depends on libraries newer than trixie's (e.g. glib), apt will refuse and the pin list will need widening — the PR build will show it.