Package: usr-is-merged
Version: 39
Severity: normal
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
``systemctl status`` reports ``Tainted: unmerged-bin``, but the
usr-is-merged package description seems to indicate that this should not
be possible? "This package can be successfully installed only on
merged-/usr systems."
Researching this, I saw various mentions of ``/lib64``, which I have too:
```sh
root@bagend:~# ls -lh /
total 788K
lrwxrwxrwx 1 root root 7 Sep 18 2022 bin -> usr/bin
drwxr-xr-x 4 root root 4.0K Nov 29 16:38 boot
- -rw------- 1 root root 924K Mar 1 2018 core
drwxr-xr-x 20 root root 3.8K Dec 4 10:36 dev
drwxr-xr-x 2 root root 4.0K Jul 17 2023 efi
drwxr-xr-x 199 root root 12K Dec 4 00:03 etc
drwxr-xr-x 4 root root 4.0K Oct 15 2023 home
lrwxrwxrwx 1 root root 29 Nov 24 17:40 initrd.img ->
boot/initrd.img-6.11.10-amd64
lrwxrwxrwx 1 root root 37 Nov 24 17:40 initrd.img.old ->
boot/initrd.img-6.12+unreleased-amd64
lrwxrwxrwx 1 root root 7 Sep 18 2022 lib -> usr/lib
lrwxrwxrwx 1 root root 9 Sep 15 09:29 lib32 -> usr/lib32
lrwxrwxrwx 1 root root 9 Dec 4 02:28 lib64 -> usr/lib64
drwx------ 2 root root 16K Dec 24 2013 lost+found
drwxr-xr-x 14 root root 4.0K Dec 20 2023 media
drwxr-xr-x 2 root root 4.0K Mar 28 2024 mnt
drwxr-xr-x 4 root root 4.0K Apr 29 2022 opt
dr-xr-xr-x 508 root root 0 Dec 4 10:36 proc
drwx------ 21 root root 4.0K Dec 4 13:29 root
drwxr-xr-x 45 root root 1.4K Dec 4 11:06 run
lrwxrwxrwx 1 root root 8 Sep 18 2022 sbin -> usr/sbin
drwxr-xr-x 2 root root 4.0K Dec 24 2013 srv
dr-xr-xr-x 13 root root 0 Dec 4 10:36 sys
drwxrwxrwt 20 root root 460 Dec 4 13:33 tmp
drwxr-xr-x 15 root root 4.0K Oct 10 19:05 usr
drwxr-xr-x 12 root root 4.0K Oct 11 08:41 var
lrwxrwxrwx 1 root root 26 Nov 24 17:40 vmlinuz -> boot/vmlinuz-6.11.10-amd64
lrwxrwxrwx 1 root root 34 Nov 24 17:40 vmlinuz.old ->
boot/vmlinuz-6.12+unreleased-amd64
```
Thinking WCPGW when doing ``rm /lib64`` ... well it turned out a lot,
like no longer working ``ls``, ``bash`` and likely (almost) everything
on my system. And rebooting resulted in a kernel crash.
(fixed it via booting sysrescue and creating the symlink again)
Looking further, I saw a suggestion to check with ``ldd``:
```sh
root@bagend:~# ldd /usr/bin/bash
linux-vdso.so.1 (0x00007fb157938000)
libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6
(0x00007fb15778a000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fb157594000)
/lib64/ld-linux-x86-64.so.2 (0x00007fb15793a000)
root@bagend:~# ls -l /lib64/
total 0
lrwxrwxrwx 1 root root 44 Nov 23 14:57 ld-linux-x86-64.so.2 ->
../lib/x86_64-linux-gnu/ld-linux-x86-64.so.2
root@bagend:~# dpkg -S /lib64/ld-linux-x86-64.so.2
diversion by libc6 from: /lib64/ld-linux-x86-64.so.2
diversion by libc6 to: /lib64/ld-linux-x86-64.so.2.usr-is-merged
```
IIRC, I had the ``usrmerge`` package installed quite a while ago, but
had apparently since removed it again. Installing it (again) made no
difference.
Happy to do test or provide additional information, but I have no clue
why systemd reports/thinks I have unmerged-bin.
Cheers,
Diederik
- -- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (101, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.12+unreleased-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
iHUEARYIAB0WIQT1sUPBYsyGmi4usy/XblvOeH7bbgUCZ1BS0wAKCRDXblvOeH7b
bglyAP0Vt6AhoqS65dvTwT06ui4KekZ04dVpXwACbfnyWkpysgD9GgYkKHXeSwnl
CKOEKA5/4UbRBK6WDGxm7RPff4sXsQ8=
=Ql65
-----END PGP SIGNATURE-----
