It's unacceptible to leave this bug open and wontfix. My main server uses the 2.4 kernel and lvm; when this bug was brought to my attention it was clear to me that since it's tracking unstable, the next time I reboot it it will no longer be able to mount its lvm volumes. The fact that debian unstable gets a system into this situation with no indication of the problem is a horrific bug.
Conflict with the 2.4 kernel, add a postinst check for 2.4, add a NEWS.Debian, add a debconf warning, but don't sit on your hands and let users break their running systems! -- see shy jo, removing lvm from all his systems in the meantime
signature.asc
Description: Digital signature
