Your message dated Thu, 22 Jul 2010 11:32:09 +0000
with message-id <[email protected]>
and subject line Bug#589029: fixed in cryptsetup 2:1.1.3-3
has caused the Debian Bug report #589029,
regarding cryptsetup: crypttab: please add noloud or quiet or something like
that
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.)
--
589029: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589029
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: cryptsetup
Version: 2:1.1.3-1
Severity: wishlist
Hello,
especially since 2:1.1.3-1 changed its behaviour to "cryptdisks
initscript now raises a warning for failed started devices" it would be
great to have a way to tell the initscripts something like: "if the
source device exists, create the crypto mapping, if not, don't care and
don't complain about it", i.e. the inverse of the "loud" crypttab
option - something like "quiet", "nowarn", "noloud" or whatever you
like. This is somewhat different from "noauto", where the mapping is
just never created automagically.
Btw.: If I read /lib/cryptsetup/cryptdisks.functions correctly, enabling
the "loud" option for one device in the current implementation enables
it for subsequent devices as well (I didn't try it, it just looks like
this).
A correct solution would probably be something like LOUD="$DEFAULT_LOUD"
in parse_opts() and using DEFAULT_LOUD="" in cryptdisks-early and
DEFAULT_LOUD="yes" in cryptdisks.
Thanks for your work & best regards
Mario
--
Wine is fine, but wiskey is quicker. Suicide is slow with liquor.
-- Ozzy Osbourne
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: cryptsetup
Source-Version: 2:1.1.3-3
We believe that the bug you reported is fixed in the latest version of
cryptsetup, which is due to be installed in the Debian FTP archive:
cryptsetup-udeb_1.1.3-3_amd64.udeb
to main/c/cryptsetup/cryptsetup-udeb_1.1.3-3_amd64.udeb
cryptsetup_1.1.3-3.debian.tar.gz
to main/c/cryptsetup/cryptsetup_1.1.3-3.debian.tar.gz
cryptsetup_1.1.3-3.dsc
to main/c/cryptsetup/cryptsetup_1.1.3-3.dsc
cryptsetup_1.1.3-3_amd64.deb
to main/c/cryptsetup/cryptsetup_1.1.3-3_amd64.deb
libcryptsetup-dev_1.1.3-3_amd64.deb
to main/c/cryptsetup/libcryptsetup-dev_1.1.3-3_amd64.deb
libcryptsetup1_1.1.3-3_amd64.deb
to main/c/cryptsetup/libcryptsetup1_1.1.3-3_amd64.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jonas Meurer <[email protected]> (supplier of updated cryptsetup package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Thu, 22 Jul 2010 12:56:01 +0200
Source: cryptsetup
Binary: cryptsetup cryptsetup-udeb libcryptsetup1 libcryptsetup-dev
Architecture: source amd64
Version: 2:1.1.3-3
Distribution: unstable
Urgency: low
Maintainer: Debian Cryptsetup Team
<[email protected]>
Changed-By: Jonas Meurer <[email protected]>
Description:
cryptsetup - configures encrypted block devices
cryptsetup-udeb - configures encrypted block devices (udeb)
libcryptsetup-dev - libcryptsetup development files
libcryptsetup1 - libcryptsetup shared library
Closes: 589029
Changes:
cryptsetup (2:1.1.3-3) unstable; urgency=low
.
* fix usage of new variable $DEFAULT_LOUD, and some cosmetical changes.
thanks to Mario 'BitKoenig' Holbe. (closes: #589029)
Checksums-Sha1:
66aa074e093ad34afd3aa179adcd14b94a7578dc 1844 cryptsetup_1.1.3-3.dsc
a80d583a4e51eae88c0db9c88eac0bc6990c92cd 73424 cryptsetup_1.1.3-3.debian.tar.gz
975b5b9f49e81a57269a780637d18530e567de7e 413032 cryptsetup_1.1.3-3_amd64.deb
114082f82306a1a6fec15bfdb7176d3133e6a030 297484
cryptsetup-udeb_1.1.3-3_amd64.udeb
05c05676ebf0d0d737b377bdea58e74f59f17087 77308 libcryptsetup1_1.1.3-3_amd64.deb
7a1c38943c9a84730ccc9aec405a3438f89501a7 41314
libcryptsetup-dev_1.1.3-3_amd64.deb
Checksums-Sha256:
8f48bb07c0b0f765fb5548b902b22d4c2aca9e1df4a5272689e5323eebd706e1 1844
cryptsetup_1.1.3-3.dsc
e9c4d3399016f9cd8ed2b8e272834cad065f32d6b7646f02049b0805c1c983aa 73424
cryptsetup_1.1.3-3.debian.tar.gz
301cdcb10f769a3a2a7ce148c0e3327eea6678dc49db54baea2ed5043ce6c2ba 413032
cryptsetup_1.1.3-3_amd64.deb
6d880c68a520d7dd50185e937808d953141dc55cff5881e02ac859d905b7c38e 297484
cryptsetup-udeb_1.1.3-3_amd64.udeb
bc019272f9949b6ac3f8df3d026af0c42dd25a4de7842ce14e5eed4661f81813 77308
libcryptsetup1_1.1.3-3_amd64.deb
bc04c6fb16b0436dcf48ef5f55cd52c46d2fdffbfbd49dcf29e1247837906322 41314
libcryptsetup-dev_1.1.3-3_amd64.deb
Files:
10b4873d3042e67b597cc3c6e24216ca 1844 admin optional cryptsetup_1.1.3-3.dsc
ac864fae04c8128307d5aa3cf15ec218 73424 admin optional
cryptsetup_1.1.3-3.debian.tar.gz
0e6c911f55ea54cc3f5e1fd80b435af0 413032 admin optional
cryptsetup_1.1.3-3_amd64.deb
53434c827027f612545783125b996b6d 297484 debian-installer optional
cryptsetup-udeb_1.1.3-3_amd64.udeb
27c5be7673d7a25bbdd1ca511f724d73 77308 libs optional
libcryptsetup1_1.1.3-3_amd64.deb
00604c429bb5846a73c02126170dd03b 41314 libdevel optional
libcryptsetup-dev_1.1.3-3_amd64.deb
Package-Type: udeb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iQEcBAEBCAAGBQJMSCU9AAoJEHUY1PcOVR4z7i4H/RWnI26cAhLtmhBw8x7I3VMT
84b+DtaapQ71WpYm1wShYzEfDh4KvQpfuGwKGkUMr843pYgrlfa0fJyrcCBZGVsz
pMWAxbvd4UbsKjF9cnml9acFDu/01YTLWGfKU6JFrybkk5RtRsRWIIxaFaETMo2h
fqD9rBJ/XCAPgsD2Eo3e/dL+FdRZk9Yl8YWvoGo14zeZDGgq13vpBBINLqJEnafG
YKO1CWUVX0lzOe2IiL9x1K/buP+EQLXeaJhn7c4WmM3agpJz/+GZivWor9yakXj1
ED+FXtVto5EX+EorPiXpD2X7BgnOjYSL1TB2g89VsiMK+/3dF9Ah83fDDk8c1FM=
=qmpg
-----END PGP SIGNATURE-----
--- End Message ---
