Package: lvm2 Version: 2.03.22-1+b1 Followup-For: Bug #1028541 Dear Maintainer,
We noticed this issue when we upgraded some our servers to use Bookworm. This is actually rendering our system unusable as the LVM partitions are not getting detected due to this issue. We have large number of servers and this is blocking us from upgrading to Bookworm. The fix is done by upstream can we please release updated LVM2 with fix for bookworm? Backporting does not seem to be right thing to do as this is genuine bug and also since its rendering systems unusable. Will this be considered for next point release of Bookworm?. If you need support in testing I'm ready to provide that. Thanks and Regards, Vasudev Kamath -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.7.12-amd64 (SMP w/8 CPU threads; PREEMPT) 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 Versions of packages lvm2 depends on: ii dmeventd 2:1.02.196-1+b1 ii dmsetup 2:1.02.196-1+b1 ii libaio1t64 0.3.113-8 ii libblkid1 2.40-8 ii libc6 2.37-19 ii libdevmapper-event1.02.1 2:1.02.196-1+b1 ii libedit2 3.1-20230828-1+b1 ii libselinux1 3.5-2+b2 ii libsystemd0 255.5-1 ii libudev1 255.5-1 Versions of packages lvm2 recommends: pn thin-provisioning-tools <none> lvm2 suggests no packages. -- no debconf information
