[ubuntu/groovy-proposed] cryptsetup 2:2.3.1-1ubuntu1 (Accepted)

Steve Langasek steve.langasek at ubuntu.com
Fri May 1 14:14:13 UTC 2020


cryptsetup (2:2.3.1-1ubuntu1) groovy; urgency=low

  * Merge from Debian unstable.  Remaining changes:
    - debian/control:
      + Recommend plymouth.
      + Depend on busybox-initramfs instead of busybox | busybox-static.
    - Fix cryptroot-unlock for busybox compatibility.

cryptsetup (2:2.3.1-1) unstable; urgency=medium

  * New upstream release.
  * d/initramfs/hooks/cryptroot: Don't set unused variable LIBC_DIR.

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).

Date: Fri, 01 May 2020 07:07:58 -0700
Changed-By: Steve Langasek <steve.langasek at ubuntu.com>
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
https://launchpad.net/ubuntu/+source/cryptsetup/2:2.3.1-1ubuntu1
-------------- next part --------------
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Fri, 01 May 2020 07:07:58 -0700
Source: cryptsetup
Architecture: source
Version: 2:2.3.1-1ubuntu1
Distribution: groovy
Urgency: medium
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
Changed-By: Steve Langasek <steve.langasek at ubuntu.com>
Closes: 916649 918008 933142 949623
Changes:
 cryptsetup (2:2.3.1-1ubuntu1) groovy; urgency=low
 .
   * Merge from Debian unstable.  Remaining changes:
     - debian/control:
       + Recommend plymouth.
       + Depend on busybox-initramfs instead of busybox | busybox-static.
     - Fix cryptroot-unlock for busybox compatibility.
 .
 cryptsetup (2:2.3.1-1) unstable; urgency=medium
 .
   * New upstream release.
   * d/initramfs/hooks/cryptroot: Don't set unused variable LIBC_DIR.
 .
 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:
 1b014628590242584c201fbb24610a12b62b7433 2997 cryptsetup_2.3.1-1ubuntu1.dsc
 016a185c115ef08d0b54c38b521289edbb9610d9 11159434 cryptsetup_2.3.1.orig.tar.gz
 df944e9ff6ab3f76f6b1257587a88bf697ca1fca 123432 cryptsetup_2.3.1-1ubuntu1.debian.tar.xz
 731119cfa79d635e21e4d8ead8b8b0ae549798ef 6564 cryptsetup_2.3.1-1ubuntu1_source.buildinfo
Checksums-Sha256:
 9799e07fbf2693d1d9b71fa8516740819869a3ed6bb280ed17ec62f91e83850c 2997 cryptsetup_2.3.1-1ubuntu1.dsc
 9127744b5e59b318a7a27eedcbbf039ebfc9964291af835480a5f9b646f39d16 11159434 cryptsetup_2.3.1.orig.tar.gz
 b300d10792f217e345995eab2ff0d09fb959080bc01e5791b115f6d05e980c4c 123432 cryptsetup_2.3.1-1ubuntu1.debian.tar.xz
 f9241da0056598dc62bf2944107681de824b181e7fd9550828b7584eef6071d8 6564 cryptsetup_2.3.1-1ubuntu1_source.buildinfo
Files:
 3be54124008c353bfb42dff3af1ff6fc 2997 admin optional cryptsetup_2.3.1-1ubuntu1.dsc
 b0216cfe74f9b58fdac48ecd8e93e3a6 11159434 admin optional cryptsetup_2.3.1.orig.tar.gz
 5f0df708a647468525e737d83c49be7f 123432 admin optional cryptsetup_2.3.1-1ubuntu1.debian.tar.xz
 30b54a411e57dd95b5cc02330f0f5430 6564 admin optional cryptsetup_2.3.1-1ubuntu1_source.buildinfo
Original-Maintainer: Debian Cryptsetup Team <pkg-cryptsetup-devel at alioth-lists.debian.net>

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

iQJOBAEBCgA4FiEErEg/aN5yj0PyIC/KVo0w8yGyEz0FAl6sLgEaHHN0ZXZlLmxh
bmdhc2VrQHVidW50dS5jb20ACgkQVo0w8yGyEz2BYQ/9EkAaLoxUT2dvgf1Er2gf
ro/BN2Id7EYQLH+CFTf5xNlNqITAEq35zkE0okyXjM+h1Q/7E2Rk0PnIpywaQI7u
opCga0K5bKmLHvI9Gn+8mIUdErJKs8xcyZO2971qCy0Fy8GjOoQmEXtf0cUjhc93
/y18rJ7+eKYLW7r4CTTBexzgYBWimMPLAyWLE7bxxtkpiQvKcGsDFSOIBJkhPN4D
gXARhDFAWsKQt12a8U1bEkYyPETKfLGlugcBSi6nlKZzipeF+/EpbnhLNvBXieNC
Pv5GRdvgSz1LKyRmCP4a9U8WnF39fuCWGF7YQBJqVpA5vESY4zt9QtxmP6HenMbU
OofNB7hirhqgS7EGEi4IFEMVPp+3SFhD1Jp1UhziutNSPgQU8PpSabF9JmBJN0Xc
UtbE3e6GbJ1ruRIbN/MfIYBNo7IwKgwP+PjxrDIMTjfixKrtyT88ditfeuimzAtL
8iK/uIG/dr5X4iO9rTxv3T/ZWEXJkcSZ0Lt4QV3uNuIAfvN9A9BmwJ9aMdpt5gRg
nHuzio7QplCrrB2T5phZqvMXgYFo+1d+ifizFKUZVnUm8wDsXVU6vCKoGOUAeASH
YV+hIvmwHPUN0uWizcIczb/jxBkBpxQP8lBqhdM8/mJQFvVTm2rcwArm/bzO/+O9
24WBOVsYCM0Bg7e12AmRmXY=
=pFfR
-----END PGP SIGNATURE-----


More information about the Groovy-changes mailing list