Control: reassing -1 libaudit1 Control: forcemerge 828991 -1 Hello Eric,
Eric Valette [2016-06-30 21:05 +0200]: > 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! systemd already grew a check in debian/rules [1], after you previously filed [2]. But this doesn't help, because this time this: > valette@tri-yann4:~$ ldd /lib/systemd/systemd > libcap-ng.so.0 => /usr/lib/x86_64-linux-gnu/libcap-ng.so.0 > (0x00007f962afa4000) ... was not caused by a systemd upload, but by a new audit package. But really, this is a whack-a-mole game. You keep running an unsupported configuration, you get to keep both halves. You *must* run an initrd if you have a separate /usr. At some point we'll get the /usr merge and this will be the latest point where separate /usr without initrd will break for good, and even now it can't work reliably (not just because of linking to pid 1, but also because of udev rules or early boot scripts calling programs from /usr, etc.). This has never been a supported configuration, and just because it happend to mostly work once it doesn't mean that it can be guaranteed forever, sorry. Martin [1] http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=24b267b53 [2] https://bugs.debian.org/771652 -- Martin Pitt | http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
signature.asc
Description: PGP signature
