On Mon, 3 Jan 2022 18:25:12 +0100 (CET) k...@aspodata.se wrote: > The first one gives me an unbootable system > $ ldd /sbin/init | grep /usr > libpcre2-8.so.0 => /usr/lib/x86_64-linux-gnu/libpcre2-8.so.0 > (0x00007f737ba28000) > > fortunately /bin/bash didn't depend on /usr so I could boot with > init=/bin/bash, but there is more breakage: > > $ ldd /bin/mount | grep /usr > libmount.so.1 => /usr/lib/x86_64-linux-gnu/libmount.so.1 > (0x00007f5bc9b06000) libblkid.so.1 => > /usr/lib/x86_64-linux-gnu/libblkid.so.1 (0x00007f5bc98f0000) > libpcre2-8.so.0 => /usr/lib/x86_64-linux-gnu/libpcre2-8.so.0 > (0x00007f5bc982c000) > > $ dpkg -l | grep sysvinit-core > ii sysvinit-core 2.96-7+devuan1 > amd64 System-V-like init $ dpkg -l | grep mount > ii libmount1:amd64 2.36.1-8+devuan1 > amd64 device mounting library ii mount > 2.36.1-8+devuan1 amd64 > tools for mounting and manipulating filesystems >
No solution, but it looks like "the culprit" for this is that the libselinux1 package changed in between beowulf (buster) and chimaera (bullseye) from depending on libpcre3 to depending on libcre2-8-0. The former, libpcre3, installs its libraries in both /lib and /usr/lib (different), in both its beowulf and chimaera versions, whereas libcre2-8-0 installs only in /usr/lib. I haven't reviewed the source for comment around that dependency change. Ralph. _______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
