[pkg-cryptsetup-devel] cryptsetup_2.3.0-1_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Wed, 04 Mar 2020 00:48:19 +0100
Source: cryptsetup
Architecture: source
Version: 2:2.3.0-1
Distribution: unstable
Urgency: low
Maintainer: Debian Cryptsetup Team <pkg-cryptsetup-devel at alioth-lists.debian.net>
Changed-By: Guilhem Moulin <guilhem at debian.org>
Closes: 916649 918008 933142 949623
Changes:
 cryptsetup (2:2.3.0-1) unstable; urgency=low
 .
   * New upstream release, introducing support for BitLocker-compatible
     devices (BITLK format) used in Windows systems.
     WARNING: crypttab(5) support for these devices is currently *experimental*
     and requires blkid from util-linux >=2.33 (i.e., Buster or later).  These
     devices currently have no keyword to use in the 4th field (unlike 'luks'
     or 'plain'), the device type is inferred from the signature instead.
   * crypttab(5): Make the 4th field (options) optional so we don't have to
     introduce a new keyword for each new device type.  (That field is also
     optional in the systemd implementation.)  Other fields (dm target name,
     source device, and key file) remain required.
   * Install cryptdisks_{start,stop} bash completion scripts to the right
     path/name so they are loaded automatically. This was no longer the case
     since 2:1.7.0-1.  (Closes: #949623)
   * d/*.install: Replace tabs with spaces.
   * d/cryptdisks-functions: Fix broken $FORCE_START handling.  Since
     2:2.0.3-2 the SysV init scripts' "force-start" option was no longer
     overriding noauto/noearly.  (Closes: #933142)
   * Move some functions to d/function from the initramfs hook.
   * SysV init scripts: skip devices holding the root FS and/or /usr during the
     shutdown phase; these file systems are still mounted at this point so any
     attempt to gracefully close the underlying device(s) is bound to fail.
     (Closes: #916649, #918008)
   * Bump Standards-Version to 4.5.0 (no changes necessary).
Checksums-Sha1:
 13a2ef3ede7714314538442326ceb962eb44df4a 2853 cryptsetup_2.3.0-1.dsc
 14582633d4a1fa940ff1dbdf84b4c354f358aae7 11152992 cryptsetup_2.3.0.orig.tar.gz
 a789a23735e32b78943685550e0683249fecbb9d 113464 cryptsetup_2.3.0-1.debian.tar.xz
 5ea2c8c6731887deb625c252c1254b4093f5c3a3 9361 cryptsetup_2.3.0-1_amd64.buildinfo
Checksums-Sha256:
 6e45dade64562e0edf7b9b669bbac3cbdb07cdb86576d55b704cf0cb15dd2e69 2853 cryptsetup_2.3.0-1.dsc
 02be6c00f5575510bb56f8233279ab044b0be5c6622e17e37dad49cd7c237585 11152992 cryptsetup_2.3.0.orig.tar.gz
 e7cad0cf149aa3a1886e1845a3cf1e7be5195174c9557373fd6d29b5ed4cd5c3 113464 cryptsetup_2.3.0-1.debian.tar.xz
 1197c3e6af4d9b99edbaf3d43d7ab00f36967b9fb1236fd1e1a42fea6828ce2f 9361 cryptsetup_2.3.0-1_amd64.buildinfo
Files:
 194443b7a3baf95d4ae95e3df1f1e282 2853 admin optional cryptsetup_2.3.0-1.dsc
 725f10442d7c4d14236f96d2c72e0ded 11152992 admin optional cryptsetup_2.3.0.orig.tar.gz
 7a7d0203d241a9d535e80218efbe1162 113464 admin optional cryptsetup_2.3.0-1.debian.tar.xz
 ea549393dec8090abcce45b4c0d2636c 9361 admin optional cryptsetup_2.3.0-1_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEERpy6p3b9sfzUdbME05pJnDwhpVIFAl5e7YcACgkQ05pJnDwh
pVJ9ug//YWmqJi2h2difSrBeYJa3WS/HdB8pEP7mE4uEYxIIREPeRjFopAMQVjaB
deFBKv5i6+jXqJyDviBYdhPVokQYEutLz2ZIdmz7sn7zHzN2mD1Qg2x5e51+cZOL
fHPiSvwo428MYWN2j/xMZxxYvxWTu/8x4WGyWeFTXZrtbjc3ou8K/Gkq2ywNTRpT
NEb78neUj1crWpmy9ULqUEvd51D2jo1xax0dPns6bMGznS1dykL+SQkrPKaEKsmU
6/DjzgPkAVhULye46F7HAa32bJtG32NZJIj5uCmSsgW6qf3I7vvaP6cvcuyD9vFj
CAPHuv301ainrI5bJMCywH2zgWQ4FCf30FIuepMJ16PEgoqP1f/MbISVeqPU4UnR
FOEFD8YXrU1BT5zTRDRNWYxrJ3L/NykZDkE6ALknowRks31JtUo/Ot+dT+cJnKwT
D98Ad25aAHScsWWwwixXgGTsq0ApYmxvDp6VmKMd2wJn1xlzw7Vv8v8TpsD3su8s
ZEBt+tLUsWG3o9ewpFS3G28kpitTF/otiW27XFhnJKWKFLhAMGVcStcEIt1bbtPV
WHM7YjR6Q4HZCeKFpLTWz6Pl4K97RC7j60hS82Zb3FbPDR4xgYyQdS4ujs/2d/jg
Kaa6ga4TGX5wK7Hr27nmp3VRXKP+Odt3V0atcA+tb++6YU0Z9lE=
=7Jg6
-----END PGP SIGNATURE-----


Thank you for your contribution to Debian.