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

[vlagged]

Hello, since about a month or so I am not able to update with `apt` the PineNote (batch 2) because Debian Trixie moved some folders around according to wiki.debian.org/UsrMerge

Code:

$ sudo apt upgrade
[...]
Upgrading: 397, Installing: 24, Removing: 0, Not Upgrading: 0
Continue? [Y/n] y
Extracting templates from packages: 100%
Preconfiguring packages ...
cat: '/sys/bus/usb/devices/*:*/bInterfaceClass': No such file or directory
cat: '/sys/bus/usb/devices/*:*/bInterfaceSubClass': No such file or directory
cat: '/sys/bus/usb/devices/*:*/bInterfaceProtocol': No such file or directory
(Reading database ... 134526 files and directories currently installed.)
Preparing to unpack .../base-files_13.6_arm64.deb ...


******************************************************************************
*
* The base-files package cannot be installed because
* /lib64 is a symbolic link and not pointing at usr/lib64 exactly.
*
* This is an unexpected situation. Cannot proceed with the upgrade.
*
* For more information please read https://wiki.debian.org/UsrMerge.
*
******************************************************************************


dpkg: error processing archive /var/cache/apt/archives/base-files_13.6_arm64.deb (--unpack):
new base-files package pre-installation script subprocess returned error exit status 1
Errors were encountered while processing:
/var/cache/apt/archives/base-files_13.6_arm64.deb
Error: Sub-process /usr/bin/dpkg returned an error code (1)

Are there any plans to make this package compatible?

[j_s]

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

[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

[bills2002]

relates to that libby post where I was getting that error.
I think they recommended remove the link?
I am still working on flashing to factory stock before I go changing stuff.

I dont boot to graphics now but the serial usb dongle does give me a login prompt. Not trying anything until I get it back to stock (with graphics).
Then Im going to try libby and if it (snapd) fails with the same error, I will then try removing /lib64 soft link.

[j_s]

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

I didn't notice that your log window needed scrolling and jumped to the conclusion that the empty USB device tree was the problem.

I also had the symbolic link problem earlier and removed the link, which worked. I didn't know about the "installl usrmerge" advice. I'm going to leave well enough alone unless the symbilic link shows up again.

I still have the USB problem.

[vlagged]

@bills2002 you're right, this post already mentions removing that link: https://forum.pine64.org/showthread.php?...#pid123754

Sorry for the noise, I should've searched a bit better the forums. I don't think you need to install usr-merge manually.

@j_s I'm also interested in connecting over USB and follow up debugging that, let me know if there's another thread where you mention the issue or I should leave this open/unsolved for this/

[j_s]

@j_s I'm also interested in connecting over USB and follow up debugging that, let me know if there's another thread where you mention the issue or I should leave this open/unsolved for this/

@vlagged I put a poll in the PineNote hardware forum about the USB issue to try to see how widespread it is. I don't know whether it is a hardware or software issue, but I'm leaning toward software.

https://forum.pine64.org/showthread.php?tid=19589

I didn't mention anything about it interfering with updates, so you might want to make a post there about it.

Also, please vote in it.