Package: lsb-base
Followup-For: Bug #1019661
X-Debbugs-Cc: to...@atoth.sote.hu
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Regular nightly upgrade brought in 11.3 lsb-release and lsb-base, but didn't
get newer sysvinit-utils (as I'm reading that mught have prevented the carnage
if it placed the init-functionns to the exact expected path (/lib/lsb) - I'm
verifying that now
* What exactly did you do (or not do) that was effective (or
ineffective)?
This is a major PITA, I'm still trying to stand that system back up, somehow
shoveling the required file, but the pen drive's /dev/sda1 is not created
either.
* What was the outcome of this action?
Well, the outcome of the upgrade was that it totally broke the boot, like
really bad.
* What outcome did you expect instead?
I'd expect the system booting even in unstable/testing. Back in the past I've
had run-ins with network manager related stuff one time, but only one time I
had broken boot due to some grib EFI update debacle about 5 years ago.
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.19.0-trunk-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
-- no debconf information
