Your message dated Tue, 8 Aug 2017 20:47:45 -0400 with message-id <email@example.com> and subject line Re: [pkg-cryptsetup-devel] Bug#870673: cryptsetup causes piuparts test to fail has caused the Debian Bug report #870673, regarding cryptsetup causes piuparts test to fail to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 870673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870673 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: cryptsetup Version: 2:1.7.3-4 Severity: serious Justification: fails to build from source (but built successfully in the past) Dear Maintainer, A new version of the kxc package fails piuparts due to cryptsetup not being able to be removed correctly. I belive this is unrelated to kxc itself, and it's blocking the move to testing. https://piuparts.debian.org/sid/fail/kxc_0.13+git20170730.6182dc8-1.log Relevant extract from the log (output of apt-get remove): Removing kxc (0.13+git20170730.6182dc8-1) ... Removing cryptsetup (2:1.7.3-4) ... /dev/mapper/control: open failed: No such device Failure to communicate with kernel device-mapper driver. Check that device-mapper is available in the kernel. Incompatible libdevmapper 1.02.137 (2016-11-30) and kernel driver (unknown version). Command failed Interestingly, the same output is in the passing cryptsetup piupart run (https://piuparts.debian.org/sid/pass/cryptsetup_2:1.7.3-4.log), but I cannot see anything else failing so I'm hoping you can take a look and see if you know why this would cause a failure on an unrelated package. Thanks a lot! Alberto
--- End Message ---
--- Begin Message ---On Fri, 04 Aug 2017 at 01:04:56 +0100, Alberto Bertogli wrote: > Removing cryptsetup (2:1.7.3-4) ... > /dev/mapper/control: open failed: No such device > Failure to communicate with kernel device-mapper driver. > Check that device-mapper is available in the kernel. > Incompatible libdevmapper 1.02.137 (2016-11-30) and kernel driver (unknown > version). > Command failed Interestingly I'm only able to reproduce this when 'dm_mod' is blacklisted. (`dmsetup table`, called by cryptsetup.prerm, tries to autoload the module if needs be, but fails when it's in the blacklist.) However a failure in `dmsetup table` is treated by the prerm script exactly like if there was no dm-crypt mappings, which seems the correct things to do in that case. Thus closing the bug (I see you closed #868973, too). Cheers, -- Guilhem.
Description: PGP signature
--- End Message ---