fix(24.04): missing lib64 in base-files

[cjdcordeiro]

fixes #153

/lib64 is now in base-files, so this PR includes said paths in its libs slice.

[norrisjeremy]

Thanks!

[norrisjeremy]

FYI, I believe /lib64 is owned by the libc6 package, not base-files.
That is what shows up when I run dpkg -S /lib64 on a regular 24.04 container.
I think that's why your CI builds fail.

[norrisjeremy]

$ docker run -it --rm ubuntu:24.04 dpkg -S /lib64  
libc6:amd64: /lib64

[norrisjeremy]

diff --git a/slices/libc6.yaml b/slices/libc6.yaml
index 5f67118..fcd25b4 100644
--- a/slices/libc6.yaml
+++ b/slices/libc6.yaml
@@ -28,3 +28,4 @@ slices:
       /usr/lib/*-linux-*/libthread_db.so.*:
       /usr/lib/*-linux-*/libutil.so.*:
       /usr/lib*/ld*.so.*:
+      /lib64: {arch: [amd64,ppc64el]}

[cjdcordeiro]

The errors are coming from the fact that /lib64 isn't present for all architectures in base-files.

Noble is a development release and thus changing all the time. We'll take this internally to double check where /lib64 is eventually landing and whether it should belong to base-files or libc6. The symlink definition, according to dpkg -c, is currently under base-files.

# dpkg -c base-files_13ubuntu7_amd64.deb | grep lib64
drwxr-xr-x root/root         0 2024-02-22 14:39 ./usr/lib64/
lrwxrwxrwx root/root         0 2024-02-22 14:39 ./lib64 -> usr/lib64

But this could be changing as we speak so let's wait for the upstream to finish updating.

[norrisjeremy]

Apologies for earlier reply, I misread your response.

[rebornplusplus]

LGTM, thank you.

[rebornplusplus]

LGTM.

[letFunny]

LGTM