fix: preserve glibc 2.17 archive publication for v0.3.1 (#15)

Author: santoshkumarradha

Cargo.lock

@@ -3,7 +3,7 @@ resolver = "2"
 members = ["furrow-core", "furrow-cli", "furrow-daemon"]
 
 [workspace.package]
-version = "0.3.0"
+version = "0.3.1"
 edition = "2021"
 rust-version = "1.83"
 license = "Apache-2.0"

Cargo.toml

@@ -735,8 +735,11 @@ pub fn restore(store: &Path, id: &str, destination: &Path) -> Result<Receipt> {
     let from = std::ffi::CString::new(root.as_os_str().as_bytes())?;
     let to = std::ffi::CString::new(destination.as_os_str().as_bytes())?;
     #[cfg(target_os = "linux")]
+    // The kernel operation predates its glibc 2.28 wrapper. Use the syscall
+    // directly so release binaries retain their glibc 2.17 compatibility floor.
     let renamed = unsafe {
-        libc::renameat2(
+        libc::syscall(
+            libc::SYS_renameat2,
             libc::AT_FDCWD,
             from.as_ptr(),
             libc::AT_FDCWD,