Your message dated Wed, 21 Oct 2009 20:05:43 +0100
with message-id <[email protected]>
and subject line Re: Bug#551533: installing cryptmount in chroot failed
has caused the Debian Bug report #551533,
regarding installing cryptmount in chroot failed
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 [email protected]
immediately.)
--
551533: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=551533
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: cryptmount
Version: 4.0.1-1
Trying to install cryptmount and cryptset in a freshly setup chroot
on an USB stick I got
Selecting previously deselected package dmsetup.
(Reading database ... 12591 files and directories currently installed.)
Unpacking dmsetup (from .../dmsetup_2%3a1.02.38-2_amd64.deb) ...
Selecting previously deselected package cryptsetup.
Unpacking cryptsetup (from .../cryptsetup_2%3a1.1.0~rc2-1_amd64.deb) ...
Selecting previously deselected package cryptmount.
Unpacking cryptmount (from .../cryptmount_4.0.1-1_amd64.deb) ...
Processing triggers for man-db ...
Setting up dmsetup (2:1.02.38-2) ...
update-initramfs: deferring update (trigger activated)
Setting up cryptsetup (2:1.1.0~rc2-1) ...
update-initramfs: deferring update (trigger activated)
Setting up cryptmount (4.0.1-1) ...
FATAL: Could not load /lib/modules/2.6.31.4/modules.dep: No such file or
directory
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-2.6.30-2-amd64
Press return to continue.
Regards
Harri
--- End Message ---
--- Begin Message ---
Hello Harri,
Thanks for the clarification.
I'm closing the bug-report because the problems you're having
are mostly caused by the difficulties of any application calling 'modprobe'
within a chroot environment, especially if the chroot environment doesn't
have a /lib/modules/`uname -r` directory. Furthermore, I believe the way
cryptmount protects its use of modprobe within the postinst script actually
means that the 'FATAL' error message you've seen (from modprobe) should
not prevent the postinst script completing successfully.
Thanks,
RW Penney
--- End Message ---
