[ubuntu/jammy-proposed] cryptsetup 2:2.4.2-1ubuntu1 (Accepted)

Michael Hudson-Doyle michael.hudson at ubuntu.com
Wed Dec 1 23:01:12 UTC 2021


cryptsetup (2:2.4.2-1ubuntu1) jammy; urgency=medium

  * 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.
    - Fix warning and error when running on ZFS on root: (LP: #1830110)
      - d/functions: Return an empty devno for ZFS devices as they don't have
        major:minor device numbers.
      - d/initramfs/hooks/cryptroot: Ignore and don't print an error message when
        devices don't have a devno.
      Submitted to debian upstream as bug #902449.
    - debian/patches/decrease_memlock_ulimit.patch
      Fixed FTBFS due a restrict environment in the new Bionic Builder (LP: #1891473)
      tests/luks2-validation.test, tests/compat-test, tests/tcrypt-compat-test.
      - Thanks Guilherme G. Piccoli.
    - Stop building the udeb on request.
  * Dropped change, included in Debian:
    - Introduce retry logic for external invocations after mdadm (LP: #1879980)
      - Currently, if an encrypted rootfs is configured on top of a MD RAID1
        array and such array gets degraded (e.g., a member is removed/failed)
        the cryptsetup scripts cannot mount the rootfs, and the boot fails.
        We fix that issue here by allowing the cryptroot script to be re-run
        by initramfs-tools/local-block stage, as mdadm can activate degraded
        arrays at that stage.
        There is an initramfs-tools counter-part for this fix, but alone the
        cryptsetup portion is harmless.
      - d/cryptsetup-initramfs.install: ship the new local-bottom script.
      - d/functions: declare variables for local-top|block|bottom scripts
        (flag that local-block is running and external invocation counter.)
      - d/i/s/local-block/cryptroot: set flag that local-block is running.
      - d/i/s/local-bottom/cryptroot: clean up the flag and counter files.
      - d/i/s/local-top/cryptroot: change the logic from just waiting 180
        seconds to waiting 5 seconds first, then allowing initramfs-tools
        to run mdadm (to activate degraded arrays) and call back at least
        30 times/seconds more.

Date: Thu, 02 Dec 2021 11:58:05 +1300
Changed-By: Michael Hudson-Doyle <michael.hudson at ubuntu.com>
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
https://launchpad.net/ubuntu/+source/cryptsetup/2:2.4.2-1ubuntu1
-------------- next part --------------
Format: 1.8
Date: Thu, 02 Dec 2021 11:58:05 +1300
Source: cryptsetup
Built-For-Profiles: noudeb
Architecture: source
Version: 2:2.4.2-1ubuntu1
Distribution: jammy
Urgency: medium
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
Changed-By: Michael Hudson-Doyle <michael.hudson at ubuntu.com>
Launchpad-Bugs-Fixed: 1830110 1879980 1891473
Changes:
 cryptsetup (2:2.4.2-1ubuntu1) jammy; urgency=medium
 .
   * 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.
     - Fix warning and error when running on ZFS on root: (LP: #1830110)
       - d/functions: Return an empty devno for ZFS devices as they don't have
         major:minor device numbers.
       - d/initramfs/hooks/cryptroot: Ignore and don't print an error message when
         devices don't have a devno.
       Submitted to debian upstream as bug #902449.
     - debian/patches/decrease_memlock_ulimit.patch
       Fixed FTBFS due a restrict environment in the new Bionic Builder (LP: #1891473)
       tests/luks2-validation.test, tests/compat-test, tests/tcrypt-compat-test.
       - Thanks Guilherme G. Piccoli.
     - Stop building the udeb on request.
   * Dropped change, included in Debian:
     - Introduce retry logic for external invocations after mdadm (LP: #1879980)
       - Currently, if an encrypted rootfs is configured on top of a MD RAID1
         array and such array gets degraded (e.g., a member is removed/failed)
         the cryptsetup scripts cannot mount the rootfs, and the boot fails.
         We fix that issue here by allowing the cryptroot script to be re-run
         by initramfs-tools/local-block stage, as mdadm can activate degraded
         arrays at that stage.
         There is an initramfs-tools counter-part for this fix, but alone the
         cryptsetup portion is harmless.
       - d/cryptsetup-initramfs.install: ship the new local-bottom script.
       - d/functions: declare variables for local-top|block|bottom scripts
         (flag that local-block is running and external invocation counter.)
       - d/i/s/local-block/cryptroot: set flag that local-block is running.
       - d/i/s/local-bottom/cryptroot: clean up the flag and counter files.
       - d/i/s/local-top/cryptroot: change the logic from just waiting 180
         seconds to waiting 5 seconds first, then allowing initramfs-tools
         to run mdadm (to activate degraded arrays) and call back at least
         30 times/seconds more.
Checksums-Sha1:
 ac4e9f26dc8122d78c2ae7c92bad130824b11934 3147 cryptsetup_2.4.2-1ubuntu1.dsc
 64ff62ca61945b4977854245208e2ddea5491cb6 11327591 cryptsetup_2.4.2.orig.tar.gz
 4e2d97e124efddfc9a8e2eb566d4e275fed8983f 139680 cryptsetup_2.4.2-1ubuntu1.debian.tar.xz
 bd24e849fc96d0af758bee36609d9d58f01453b9 7949 cryptsetup_2.4.2-1ubuntu1_source.buildinfo
Checksums-Sha256:
 dc2845c49655f6752dacdfa19869eb5026decbc92970797b20d29bf68f016ce1 3147 cryptsetup_2.4.2-1ubuntu1.dsc
 4b023868af0a8fd155ba5705ee289489e4ac79808df4d76db82fccb725e43275 11327591 cryptsetup_2.4.2.orig.tar.gz
 464012fb82b8d42ea0012c2ec75c9d067605bd6266c6ac13f11cdf23cee85c33 139680 cryptsetup_2.4.2-1ubuntu1.debian.tar.xz
 194cb64be61bbe0f4caddf6a48be8db2922d49bb114adf5e9c4f65702934a2e6 7949 cryptsetup_2.4.2-1ubuntu1_source.buildinfo
Files:
 bbebca8ec6d9db6f987f80178c8f0858 3147 admin optional cryptsetup_2.4.2-1ubuntu1.dsc
 a38f3fbd289b570864e52ba59acb2152 11327591 admin optional cryptsetup_2.4.2.orig.tar.gz
 049c95951b9e43a6d9e7ac2c583d2535 139680 admin optional cryptsetup_2.4.2-1ubuntu1.debian.tar.xz
 749c83d7b4580a4b6e007c0357849143 7949 admin optional cryptsetup_2.4.2-1ubuntu1_source.buildinfo
Original-Maintainer: Debian Cryptsetup Team <pkg-cryptsetup-devel at alioth-lists.debian.net>
Vcs-Git: https://git.launchpad.net/~mwhudson/ubuntu/+source/cryptsetup
Vcs-Git-Commit: 4acf3aa2ca444af19adab5f45f47d5f094be1257
Vcs-Git-Ref: refs/heads/ubuntu/jammy-proposed


More information about the jammy-changes mailing list