base-files_13.6_arm64.deb and wiki.debian.org/UsrMerge

[vlagged]

Those errors have nothing to do with UsrMerge but they might explain why my PineNote does not notice when I plug in a hub sold for the PinePhone and my laptop doest not notice when I connect it to my PineNote over USB. Only charging and the dongle work for me. /sys/bus/usb/devices is empty in my PineNote.

Code:

user@pinenote:~$ ls '/sys/bus/usb/devices/*:*/bInterfaceClass'
ls: cannot access '/sys/bus/usb/devices/*:*/bInterfaceClass': No such file or directory

user@pinenote:~$ ls '/sys/bus/usb/'
devices  drivers  drivers_autoprobe  drivers_probe  uevent

user@pinenote:~$ ls /sys/bus/usb/devices/

user@pinenote:~$ ls /sys/bus/usb/drivers
hub  usb  usbfs  usbhid

Yes, there are these errors before, but the UsrMerge one after. Looking better at files in base-files_13.6 shows this preinst script:

Code:

user@pinenote:~$ dpkg --contents /var/cache/apt/archives/base-files_13.6_arm64.deb
#!/bin/sh
set -e

if [ "$1" = "install" ] || [ "$1" = "upgrade" ]; then
  msg=
  for d in bin lib lib32 lib64 libo32 libx32 sbin; do
    if [ -L "$DPKG_ROOT/$d" ]; then
      target=$(readlink "$DPKG_ROOT/$d")
      if [ "$target" != "usr/$d" ]; then
        if [ "$d" = lib64 ] && [ "$target" = "usr/lib/aarch64-linux-gnu" ]; then
          # Work around https://github.com/systemd/systemd/issues/33919
          echo "Fixing bad /$d symbolic link created by systemd-nspawn."
          if [ -d "$DPKG_ROOT/usr/$d" ]; then
            ln -sf "usr/$d" "$DPKG_ROOT/$d"
          else
            rm "$DPKG_ROOT/$d"
          fi
        else
          msg="/$d is a symbolic link and not pointing at usr/$d exactly"
        fi
      elif [ ! -d "$DPKG_ROOT/usr/$d" ]; then
        msg="/$d is a dangling symbolic link"
      fi
      msg2="This is an unexpected situation. Cannot proceed with the upgrade"
    elif [ -d "$DPKG_ROOT/$d" ]; then
      msg="/$d is a directory, but should be a symbolic link"
      msg2="Please install the usrmerge package to convert this system to merged-/usr"
    fi
    if [ -n "$msg" ]; then
      cat <<EOF


******************************************************************************
*
* The base-files package cannot be installed because
* $msg.
*
* $msg2.
*
* For more information please read https://wiki.debian.org/UsrMerge.
*
******************************************************************************


EOF
      exit 1
    fi
  done

(this is just its beginning).

Since the message is about msg="/lib64 is a symbolic link and not pointing at usr/lib64 exactly." and msg2="This is an unexpected situation. Cannot proceed with the upgrade." and lib64 is NOT present in the package, I looked at my root fs:

lrwxrwxrwx   1 root root     7 Oct 27 11:42 lib64 -> usr/lib

So clearly somebody created this link which is not very compatible with that check (should be usr/lib64, but that doesn't even exist).
lsof /lib64 does not show anyone so I might just remove it..

Code:

user@pinenote:~$ dpkg -S /lib64
diversion by base-files from: /lib64
diversion by base-files to: /.lib64.usr-is-merged