[ubuntu/impish-proposed] mdadm 4.2~rc2-2ubuntu1 (Accepted)

[Graham Inggs]

mdadm (4.2~rc2-2ubuntu1) impish; urgency=medium

  * Merge from Debian unstable (LP: #1940096), remaining changes:
    - Ship finalrd hook.
    - Do not install mdadm-shutdown.service on Ubuntu.
    - Drop broken and unused init scripts in favor of native systemd units,
      which can cause failure to reconfigure mdadm package under certain
      confiment types.
    - Drop /etc/cron.d/mdadm and migrate to systemd mdcheck_start|continue
      timer units.
    - Drop /etc/cron.daily/mdadm and migrate to system mdmonitor-oneshot
      timer unit.
    - mdcheck_start.timer configures the mdcheck on a first sunday of the
      month, with a randomized start delay of up to 24h, and runs for at
      most 6h. mdcheck_continue.timer kicks off daily, with a randomized
      start delay of up to 12h, and continues mdcheck for at most 6h.
    - mdmonitor-oneshot.timer runs daily, with a randomized start delay of
      up to 24h.
    - One can use systemd drop-ins to change .timer units timings, set
      environmental variables to decrease/increase the length of checking,
      or start the checks by hand. Previously used checkarray is still
      available, albeit not used by timer units.
    - Above ensures that previous daily / monthly checks are performed, but
      are randomized, such that performance is not as impacted across a
      cluster of machines.
    - Honor the debconf daily autoscan setting in the systemd timer.
    - d/p/mdcheck-fix-empty-spaces-in-timer-unit-files.patch:
      - The spaces were causing a FTBFS situation, triggered by
        dh_installsystemd not finding units.
    - Mention mdmonitor-oneshot.service instead of /etc/cron.daily/mdadm
      in /etc/default/mdadm

mdadm (4.2~rc2-2) unstable; urgency=medium

  * Upload targeting unstable.
  * Fix uscan regex for upstream tarballs.

mdadm (4.2~rc2-1) experimental; urgency=medium

  * New release candidate from upstream.

Date: Tue, 17 Aug 2021 17:41:27 +0000
Changed-By: Graham Inggs <ginggs at ubuntu.com>
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
https://launchpad.net/ubuntu/+source/mdadm/4.2~rc2-2ubuntu1
-------------- next part --------------
Format: 1.8
Date: Tue, 17 Aug 2021 17:41:27 +0000
Source: mdadm
Built-For-Profiles: noudeb
Architecture: source
Version: 4.2~rc2-2ubuntu1
Distribution: impish
Urgency: medium
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
Changed-By: Graham Inggs <ginggs at ubuntu.com>
Launchpad-Bugs-Fixed: 1940096
Changes:
 mdadm (4.2~rc2-2ubuntu1) impish; urgency=medium
 .
   * Merge from Debian unstable (LP: #1940096), remaining changes:
     - Ship finalrd hook.
     - Do not install mdadm-shutdown.service on Ubuntu.
     - Drop broken and unused init scripts in favor of native systemd units,
       which can cause failure to reconfigure mdadm package under certain
       confiment types.
     - Drop /etc/cron.d/mdadm and migrate to systemd mdcheck_start|continue
       timer units.
     - Drop /etc/cron.daily/mdadm and migrate to system mdmonitor-oneshot
       timer unit.
     - mdcheck_start.timer configures the mdcheck on a first sunday of the
       month, with a randomized start delay of up to 24h, and runs for at
       most 6h. mdcheck_continue.timer kicks off daily, with a randomized
       start delay of up to 12h, and continues mdcheck for at most 6h.
     - mdmonitor-oneshot.timer runs daily, with a randomized start delay of
       up to 24h.
     - One can use systemd drop-ins to change .timer units timings, set
       environmental variables to decrease/increase the length of checking,
       or start the checks by hand. Previously used checkarray is still
       available, albeit not used by timer units.
     - Above ensures that previous daily / monthly checks are performed, but
       are randomized, such that performance is not as impacted across a
       cluster of machines.
     - Honor the debconf daily autoscan setting in the systemd timer.
     - d/p/mdcheck-fix-empty-spaces-in-timer-unit-files.patch:
       - The spaces were causing a FTBFS situation, triggered by
         dh_installsystemd not finding units.
     - Mention mdmonitor-oneshot.service instead of /etc/cron.daily/mdadm
       in /etc/default/mdadm
 .
 mdadm (4.2~rc2-2) unstable; urgency=medium
 .
   * Upload targeting unstable.
   * Fix uscan regex for upstream tarballs.
 .
 mdadm (4.2~rc2-1) experimental; urgency=medium
 .
   * New release candidate from upstream.
Checksums-Sha1:
 5efe3f55cdea2fe958e623faa379d0c01d4b63fe 2126 mdadm_4.2~rc2-2ubuntu1.dsc
 75bb4e38d53e2b6b9fe064337df9ab2a877ce933 600129 mdadm_4.2~rc2.orig.tar.gz
 23704f661cbf1f3355f1645c5d8e62a356401ce6 91596 mdadm_4.2~rc2-2ubuntu1.debian.tar.xz
 e9c118d95f85ba1a30897794cb94b11229976474 6733 mdadm_4.2~rc2-2ubuntu1_source.buildinfo
Checksums-Sha256:
 63899dd5cb2c640cbb0d5d79952f3ce445148216c1b7bac8e2d142a6991f00c0 2126 mdadm_4.2~rc2-2ubuntu1.dsc
 098a2fc84e5fcee06d25cab6e6d4e8de861217bedc79585337b24e0e46e09206 600129 mdadm_4.2~rc2.orig.tar.gz
 621c58ff594dce21ec04a3338dd05ec2e53239e051f9a3caafee3b024a9b527d 91596 mdadm_4.2~rc2-2ubuntu1.debian.tar.xz
 4ab1d4f227d596740b0ac4fe404c1f9401091ac551514d8946871af14679a9ed 6733 mdadm_4.2~rc2-2ubuntu1_source.buildinfo
Files:
 9c06ee28db03047d73c341ca4144fa97 2126 admin optional mdadm_4.2~rc2-2ubuntu1.dsc
 d4dfb210db56592fd8ef66ed2f799f76 600129 admin optional mdadm_4.2~rc2.orig.tar.gz
 fe2759c80a245913b84e713d1f3a82c0 91596 admin optional mdadm_4.2~rc2-2ubuntu1.debian.tar.xz
 939ab0d3be79f5274c521d9b6c99b0b7 6733 admin optional mdadm_4.2~rc2-2ubuntu1_source.buildinfo
Original-Maintainer: Felix Lechner <felix.lechner at lease-up.com>