bootc-deb/bootc-libostree-compatibility.patch
robojerk 695714a60e
Some checks failed
Build Packages / Build libostree Backport (push) Failing after 0s
Build Packages / Build bootc Package (push) Has been skipped
Test Build / Test bootc Build (with existing libostree) (push) Failing after 0s
Build Packages / Create Release (push) Has been skipped
Build Packages / Create Artifacts for README Update (push) Has been skipped
Initial commit: Complete bootc packaging with CI/CD automation
2025-07-20 23:30:16 +00:00

27 lines
No EOL
1.2 KiB
Diff

From 1234567890abcdef1234567890abcdef12345678 Mon Sep 17 00:00:00 2001
From: Bootc Debian Packaging <packaging@example.com>
Date: Sun, 20 Jul 2025 22:50:00 +0000
Subject: [PATCH] Fix compatibility with libostree 2025.2-1 on Ubuntu Noble
This patch comments out the set_null_log() call that is not available
in the current ostree Rust bindings version, allowing bootc to build
and run successfully with libostree 2025.2-1 backported to Ubuntu Noble.
---
crates/lib/src/cli.rs | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/crates/lib/src/cli.rs b/crates/lib/src/cli.rs
index abc1234..def5678 100644
--- a/crates/lib/src/cli.rs
+++ b/crates/lib/src/cli.rs
@@ -1029,7 +1029,8 @@ pub fn global_init() -> Result<()> {
eprintln!("failed to set name: {e}");
}
// Silence SELinux log warnings
- ostree::SePolicy::set_null_log();
+ // TODO: Re-enable when ostree Rust bindings support set_null_log()
+ // ostree::SePolicy::set_null_log();
let am_root = rustix::process::getuid().is_root();
// Work around bootc-image-builder not setting HOME, in combination with podman (really c/common)
// bombing out if it is unset.