Bug#1089516: kpartx won't handle boot cryptsetup'ed devices after decryption

2024-12-08 Thread Chris Hofstaedtler
* Sergey Aleynikov [241208 20:02]: > > If dmsetup_env helps with anything, then you found some other > > package's udev rules relying on extremely outdated stuff. > > > > dmsetup_env should have exported DM_NAME, DM_UUID, DM_STATE=ACTIVE, > > DM_TABLE_STATE=LIVE. DM_NAME and DM_UUID should be expo

Bug#1089516: kpartx won't handle boot cryptsetup'ed devices after decryption

2024-12-08 Thread Chris Hofstaedtler
Control: tags -1 + wontfix * Sergey Aleynikov [241208 11:09]: > While investigating this, I found that kpartx package has two following > changes between bullseye and bookworm: > > - dropped /lib/udev/dmsetup_env > - removed IMPORT{program}="dmsetup_env %M %m" line from > /lib/udev/rules.d/60-

Bug#1089516: kpartx won't handle boot cryptsetup'ed devices after decryption

2024-12-08 Thread Sergey Aleynikov
Package: kpartx Version: 0.9.4-3+deb12u1 Severity: important X-Debbugs-Cc: sergey.aleynikov+...@gmail.com Dear Maintainer, After upgrading from bullseye to bookworm, my boot sequence for assembling devices for the / partition stopped working. I have the following scheme in place: /dev/sdh -