Your message dated Sat, 2 Jul 2016 09:40:41 +0200
with message-id <82ea4835-9ea2-41e5-440e-33c6e01ce...@free.fr>
and subject line Re: Bug#829127: systemd: Please make sure /lib/systemd/systemd
is not linked with something in /usr
has caused the Debian Bug report #829127,
regarding initrd does not mount /usr
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
829127: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829127
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 230-3
Severity: critical
Justification: breaks the whole system
Today a system using initrd was unbootable after upgrade because of the very
same problem of /usr/lib library dependency.
Please make a check afetr building the binary so this is automagically detected!
valette@tri-yann4:~$ ldd /lib/systemd/systemd
linux-vdso.so.1 (0x00007ffc639f4000)
libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1
(0x00007f962ccdc000)
libcap.so.2 => /lib/x86_64-linux-gnu/libcap.so.2 (0x00007f962cad6000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f962c8cd000)
libseccomp.so.2 => /lib/x86_64-linux-gnu/libseccomp.so.2
(0x00007f962c688000)
libpam.so.0 => /lib/x86_64-linux-gnu/libpam.so.0 (0x00007f962c479000)
libaudit.so.1 => /lib/x86_64-linux-gnu/libaudit.so.1
(0x00007f962c250000)
libkmod.so.2 => /lib/x86_64-linux-gnu/libkmod.so.2 (0x00007f962c039000)
libapparmor.so.1 => /lib/x86_64-linux-gnu/libapparmor.so.1
(0x00007f962be28000)
libmount.so.1 => /lib/x86_64-linux-gnu/libmount.so.1
(0x00007f962bbdd000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x00007f962b9c0000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f962b61f000)
/lib64/ld-linux-x86-64.so.2 (0x00005612a1c74000)
libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007f962b3ae000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f962b1aa000)
libcap-ng.so.0 => /usr/lib/x86_64-linux-gnu/libcap-ng.so.0
(0x00007f962afa4000)
libblkid.so.1 => /lib/x86_64-linux-gnu/libblkid.so.1
(0x00007f962ad60000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x00007f962ab5b000)
-- Package-specific info:
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.4.14 (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages systemd depends on:
ii adduser 3.115
ii libacl1 2.2.52-3
ii libapparmor1 2.10.95-3
ii libaudit1 1:2.6.1-1
ii libblkid1 2.28-5
ii libc6 2.23-0experimental4
ii libcap2 1:2.25-1
ii libcap2-bin 1:2.25-1
ii libcryptsetup4 2:1.7.0-2
ii libgcrypt20 1.7.1-2
ii libgpg-error0 1.23-1
ii libkmod2 22-1.1
ii liblzma5 5.1.1alpha+20120614-2.1
ii libmount1 2.28-5
ii libpam0g 1.1.8-3.3
ii libseccomp2 2.3.1-2
ii libselinux1 2.5-3
ii libsystemd0 230-3
ii mount 2.28-5
ii util-linux 2.28-5
Versions of packages systemd recommends:
ii dbus 1.11.2-1
ii libpam-systemd 230-3
Versions of packages systemd suggests:
ii policykit-1 0.113-4
pn systemd-container <none>
pn systemd-ui <none>
Versions of packages systemd is related to:
ii udev 230-3
-- no debconf information
--- End Message ---
--- Begin Message ---
On 30/06/2016 22:00, Eric Valette wrote:
On 30/06/2016 21:46, Martin Pitt wrote:
Hello Eric,
Eric Valette [2016-06-30 21:33 +0200]:
I have an initrd on this machine so this is something else
OK, I owe you an apology then, sorry. In #771652 you didn't yet, so I
just assumed that was still the case.
I was lucky to see at the top of the screen something about shared
object,
booted with sysvinit and found it. I suspect the bug is true even
with an
initrd this time. Maybe analysing the initrd could tell us.
That's strange indeed. Mind booting with "debug" and attaching
/run/initramfs/initramfs.debug?
Turns out I did it and it produced no trace (no file just systemd was
printing like crasy). As I've been using my own kernel without initramfs
for so long, I simply forgot to enable initrd support in this kernel. I
enabled it and voilà, /usr is mounted.
Groumph and sorry for the waste of time.
-- eric
--- End Message ---
