Package: libc6 Version: 2.25-1 Severity: important Hi! After upgrading libc6 to 2.25-1, most components of openrc segfault on startup. This is pretty uncool for something that handles init scripts: it renders the system effectively unbootable (strictly speaking, it boots, init does its thing, but I for one would prefer hostname set, non-root filesystems mounted, ssh running -- that sort of things).
Obviously, this is a severity:critical bug in openrc, and it's up to one of its uploaders to fix it. Which we just did in 0.27-2. But, that's not enough, as if libc6 is upgraded first (or only, on partial upgrades), the user will end-up with openrc 0.27-1 but new libc. Thus, there's a need to prevent such situation. Usually, we add Breaks: but that's not enough: • openrc is deconfigured • libc6 is upgraded • a daemon tries to stop or restart -- boom! Thus, the obvious approach is to add "Conflicts: openrc (<< 0.27-2~)" to libc6 and its arch variants (libc{6.1,0.1,0.3}). I'm not sure that's the best solution: apt may prefer to instead remove openrc, and some other upgrade non-nicety is likely to pop up in the future. Would you have a better idea? If not, please add this Conflicts: stanza. Meow! -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (150, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.14.0+ (SMP w/6 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init)