Your message dated Thu, 23 Feb 2006 11:50:18 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#353678: loop-aes-2.6.15-1-686: tests fail
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: loop-aes-2.6.15-1-686
Version: 3.1c+2
Severity: important
Running tests fails with stock testing kernel 2.6.15-1-686 :
# /usr/share/loop-aes-2.6.15-1-686/runtests
dd if=/dev/zero of=test-file1 bs=1024 count=33
33+0 enregistrements lus.
33+0 enregistrements écrits.
33792 bytes transferred in 0,053852 seconds (627496 bytes/sec)
cp test-file1 test-file3
echo 09876543210987654321 | /sbin/losetup -p 0 -e AES128 /dev/loop7 test-file3
ioctl: LOOP_SET_STATUS: Argument invalide, requested cipher or key length (128
bits) not supported by kernel
make: *** [tests] Erreur 1
Mounting of encrypted loop partition gives the same symptom
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-686
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)
Versions of packages loop-aes-2.6.15-1-686 depends on:
ii linux-image-2.6.15-1-686 2.6.15-4 Linux kernel 2.6.15 image on PPro/
ii loop-aes-utils 2.12r-1 Tools for mounting and manipulatin
loop-aes-2.6.15-1-686 recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Hello,
On Thu, Feb 23, 2006 at 11:30:28AM +0100, Olivier Berger wrote:
> It seems I've run exactly in the situation you describe.
>
> Actually, I had a loop module loaded already and didn't reboot after
> having installed the modules, nor unload and reload the module.
>
> Now I have rebooted, it works OK.
>
> Can close then.
Doing so..
Good to hear that it now works for you.
I will think about some way to indicate to the user that
unloading cryptoloop or loop may be necessary.
cheers,
Max
--- End Message ---
