Format: 1.8
Date: Wed, 28 Jul 2021 10:38:46 +0000
Source: mdadm
Binary: mdadm
Built-For-Profiles: noudeb
Architecture: s390x s390x_translations
Version: 4.2~rc1-1ubuntu1
Distribution: impish-proposed
Urgency: medium
Maintainer: Launchpad Build Daemon <buildd@bos02-s390x-016.buildd>
Changed-By: Graham Inggs <ginggs@ubuntu.com>
Description:
 mdadm      - Tool to administer Linux MD arrays (software RAID)
Launchpad-Bugs-Fixed: 1935895
Changes:
 mdadm (4.2~rc1-1ubuntu1) impish; urgency=medium
 .
   * Merge from Debian experimental (LP: #1935895), 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
   * Dropped changes:
     - d/p/mdcheck-when-mdcheck-start-is-enabled-mdcheck-continue-too.patch:
       - When mdcheck_start is enabled, enable mdcheck_continue too.
     - d/p/mdcheck-log-when-done.patch:
       - Make sure mdcheck logs the completion too, so that
       it can be determined how long the raid check took.
     - Cherrypick upstream fix to allow assembling dirty degrated IMSM raid
       arrays with --force flag
Checksums-Sha1:
 2b07d4cdfd6d53cd6edc80e6e160535ff846041a 1797782 mdadm-dbgsym_4.2~rc1-1ubuntu1_s390x.ddeb
 6624baa022bf0b9e1da059a38d8fb6b291a2aee1 5976 mdadm_4.2~rc1-1ubuntu1_s390x.buildinfo
 3cbb64139e10a4560d85f23da1106544531d63c8 521650 mdadm_4.2~rc1-1ubuntu1_s390x.deb
 d6393cfe90072f0d0d37cb03d707ba85798fea4e 35323 mdadm_4.2~rc1-1ubuntu1_s390x_translations.tar.gz
Checksums-Sha256:
 4d3df130010b4cbc463c41f4270fd765bd3619fdcf27a802f9153dc618d08424 1797782 mdadm-dbgsym_4.2~rc1-1ubuntu1_s390x.ddeb
 a8c929f0acb00d90a794070caeceb08b6bfa701edb67fc67640d668a957e1d60 5976 mdadm_4.2~rc1-1ubuntu1_s390x.buildinfo
 68f2dd76167ec5f8e1fb3a77ce66f8a6ae7c17b97ced337cfb0adeb8c75a74aa 521650 mdadm_4.2~rc1-1ubuntu1_s390x.deb
 a600d9a5a1653b69d7e71d80b11b62fe1461043593201ed0b4ee6c9942449c40 35323 mdadm_4.2~rc1-1ubuntu1_s390x_translations.tar.gz
Files:
 55c3e1bfa8440c0c5690e05014a9ec13 1797782 debug optional mdadm-dbgsym_4.2~rc1-1ubuntu1_s390x.ddeb
 507fa58ea40f180de588102a59ce0b88 5976 admin optional mdadm_4.2~rc1-1ubuntu1_s390x.buildinfo
 d803fff8829d8291c29aedbe127f1b66 521650 admin optional mdadm_4.2~rc1-1ubuntu1_s390x.deb
 e5a2a60eb61359586bf802b1894b87bc 35323 raw-translations - mdadm_4.2~rc1-1ubuntu1_s390x_translations.tar.gz
Original-Maintainer: Felix Lechner <felix.lechner@lease-up.com>