Change log for mdadm package in Ubuntu
1 → 75 of 152 results | First • Previous • Next • Last |
Published in oracular-release |
Published in noble-release |
Deleted in noble-proposed (Reason: Moved to noble) |
mdadm (4.3-1ubuntu2) noble; urgency=medium * No-change rebuild for CVE-2024-3094 -- Steve Langasek <email address hidden> Sun, 31 Mar 2024 09:17:46 +0000
Available diffs
- diff from 4.3-1ubuntu1 to 4.3-1ubuntu2 (313 bytes)
mdadm (4.3-1ubuntu1) noble; urgency=medium * Merge with Debian unstable. Remaining changes: - d/control, d/mdadm.install, d/local/finalrd/mdadm.finalrd: Ship finalrd hook - d/local/initramfs-tools/init-top/00_mount_efivarfs: Mount efivarfs during initramfs boot phase - d/mdadm.maintscript: Keep Ubuntu prior-versions until after the release of 24.04
Available diffs
Deleted in noble-updates (Reason: superseded by release) |
Superseded in noble-release |
Deleted in noble-proposed (Reason: Moved to noble) |
mdadm (4.2+20231121-1ubuntu1) noble; urgency=medium * Merge with Debian unstable. Remaining changes: - d/control, d/mdadm.install, d/local/finalrd/mdadm.finalrd: Ship finalrd hook - d/local/initramfs-tools/init-top/00_mount_efivarfs: Mount efivarfs during initramfs boot phase - d/mdadm.maintscript: Keep Ubuntu prior-versions until after the release of 24.04
Available diffs
mdadm (4.2+20231026-1ubuntu1) noble; urgency=medium * Merge with Debian unstable. Remaining changes: - d/control, d/mdadm.install, d/local/finalrd/mdadm.finalrd: Ship finalrd hook - d/local/initramfs-tools/init-top/00_mount_efivarfs: Mount efivarfs during initramfs boot phase - d/mdadm.maintscript: Keep Ubuntu prior-versions until after the release of 24.04
Available diffs
Superseded in noble-release |
Published in mantic-release |
Deleted in mantic-proposed (Reason: Moved to mantic) |
mdadm (4.2+20230508-7ubuntu1) mantic; urgency=medium * Merge with Debian unstable. Remaining changes: - d/control, d/mdadm.install, d/local/finalrd/mdadm.finalrd: Ship finalrd hook - d/local/initramfs-tools/init-top/00_mount_efivarfs: Mount efivarfs during initramfs boot phase - d/mdadm.maintscript: Keep Ubuntu prior-versions until after the release of 24.04
Available diffs
mdadm (4.2+20230508-6ubuntu1) mantic; urgency=medium * Merge from Debian unstable, remaining changes: - d/control, d/mdadm.install, d/local/finalrd/mdadm.finalrd: Ship finalrd hook - d/local/initramfs-tools/init-top/00_mount_efivarfs: Mount efivarfs during initramfs boot phase * d/mdadm.maintscript: Keep Ubuntu prior-versions until after the release of 24.04 * Dropped changes, included in Debian: - 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
Available diffs
- diff from 4.2-5ubuntu2 to 4.2+20230508-6ubuntu1 (163.4 KiB)
mdadm (4.2-0ubuntu2) jammy; urgency=medium * Add scripts/init-top/00_mount_efivarfs, mounting efivarfs. (LP: #1993541) -- Cyrus Lien <email address hidden> Tue, 11 Apr 2023 11:22:59 +0800
Available diffs
- diff from 4.2-0ubuntu1 to 4.2-0ubuntu2 (747 bytes)
mdadm (4.2-3ubuntu2) kinetic; urgency=medium * Add scripts/init-top/00_mount_efivarfs, mounting efivarfs. (LP: #1993541) -- Cyrus Lien <email address hidden> Tue, 11 Apr 2023 11:22:59 +0800
Available diffs
- diff from 4.2-3ubuntu1 to 4.2-3ubuntu2 (584 bytes)
Published in lunar-updates |
Superseded in mantic-release |
Deleted in mantic-proposed (Reason: Moved to mantic) |
Deleted in lunar-proposed (Reason: moved to -updates) |
mdadm (4.2-5ubuntu2) lunar; urgency=medium * Add scripts/init-top/00_mount_efivarfs, mounting efivarfs. (LP: #1993541) -- Cyrus Lien <email address hidden> Tue, 11 Apr 2023 11:22:59 +0800
Available diffs
- diff from 4.2-5ubuntu1 to 4.2-5ubuntu2 (571 bytes)
Superseded in mantic-release |
Published in lunar-release |
Deleted in lunar-proposed (Reason: Moved to lunar) |
mdadm (4.2-5ubuntu1) lunar; urgency=medium * Merge from Debian unstable, 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, included in Debian: - Install /usr/share/apport/package-hooks/source_mdadm.py with install instead of a second call to dh_install, which clears the execute permission on /usr/share/mdadm/mdcheck - Drop /lib/udev/rules.d/64-md-raid-assembly.rules from mdadm-udeb, no longer built - Ship /etc/mdadm directory again to prevent dpkg warning: unable to delete old directory '/etc/mdadm': Directory not empty - Display $(DEB_VENDOR) $(DEB_VERSION) in mdadm --version output
Available diffs
- diff from 4.2-3ubuntu1 to 4.2-5ubuntu1 (2.6 KiB)
Superseded in lunar-release |
Obsolete in kinetic-release |
Deleted in kinetic-proposed (Reason: Moved to kinetic) |
mdadm (4.2-3ubuntu1) kinetic; urgency=medium * Merge from Debian unstable, 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 * Install /usr/share/apport/package-hooks/source_mdadm.py with install instead of a second call to dh_install, which clears the execute permission on /usr/share/mdadm/mdcheck * Drop /lib/udev/rules.d/64-md-raid-assembly.rules from mdadm-udeb, no longer built * Ship /etc/mdadm directory again to prevent dpkg warning: unable to delete old directory '/etc/mdadm': Directory not empty, see #1004475 * Display $(DEB_VENDOR) $(DEB_VERSION) in mdadm --version output, see #1000663
Available diffs
- diff from 4.2-0ubuntu1 to 4.2-3ubuntu1 (14.7 KiB)
Superseded in kinetic-release |
Published in jammy-release |
Deleted in jammy-proposed (Reason: Moved to jammy) |
mdadm (4.2-0ubuntu1) jammy; urgency=medium * New upstream release (LP: #1959843) -- Graham Inggs <email address hidden> Thu, 24 Feb 2022 15:19:00 +0000
Available diffs
- diff from 4.2~rc2-2ubuntu1 to 4.2-0ubuntu1 (12.0 KiB)
Superseded in jammy-release |
Obsolete in impish-release |
Deleted in impish-proposed (Reason: Moved to impish) |
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
Available diffs
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
Available diffs
- diff from 4.1-11ubuntu1 to 4.2~rc1-1ubuntu1 (90.6 KiB)
mdadm (4.1-11ubuntu1) impish; urgency=medium * Merge from Debian unstable. 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. - 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 * Mention mdmonitor-oneshot.service instead of /etc/cron.daily/mdadm in /etc/default/mdadm
Available diffs
- diff from 4.1-10ubuntu3 to 4.1-11ubuntu1 (1.9 KiB)
Superseded in impish-release |
Obsolete in hirsute-release |
Deleted in hirsute-proposed (Reason: moved to Release) |
mdadm (4.1-10ubuntu3) hirsute; urgency=medium * No-change rebuild to drop the udeb package. -- Matthias Klose <email address hidden> Thu, 25 Feb 2021 06:59:03 +0100
Available diffs
- diff from 4.1-10ubuntu2 to 4.1-10ubuntu3 (292 bytes)
mdadm (4.1-10ubuntu2) hirsute; urgency=medium * No-change rebuild to drop the udeb package. -- Matthias Klose <email address hidden> Mon, 22 Feb 2021 10:35:27 +0100
Available diffs
- diff from 4.1-10ubuntu1 to 4.1-10ubuntu2 (322 bytes)
mdadm (4.1-10ubuntu1) hirsute; urgency=medium * Merge from Debian unstable. 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. - 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
Available diffs
- diff from 4.1-8ubuntu1 to 4.1-10ubuntu1 (3.5 KiB)
mdadm (4.1-8ubuntu1) hirsute; urgency=low * Merge from Debian unstable. 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. - 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. * Also fix up whitespace in systemd/mdmonitor-oneshot.timer. * Cherrypick upstream fix to allow assembling dirty degrated IMSM raid arrays with --force flag. LP: #1894792
Available diffs
- diff from 4.1-5ubuntu5 to 4.1-8ubuntu1 (38.0 KiB)
mdadm (4.1-5ubuntu1.2) focal; urgency=medium * d/p/mdcheck-when-mdcheck-start-is-enabled-mdcheck-continue-too.patch: - When mdcheck_start is enabled, enable mdcheck_continue too.
Available diffs
- diff from 4.1-5ubuntu1.1 to 4.1-5ubuntu1.2 (989 bytes)
Superseded in hirsute-release |
Obsolete in groovy-release |
Deleted in groovy-proposed (Reason: moved to Release) |
mdadm (4.1-5ubuntu5) groovy; urgency=medium * 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.
Available diffs
- diff from 4.1-5ubuntu3 to 4.1-5ubuntu5 (1.2 KiB)
- diff from 4.1-5ubuntu4 to 4.1-5ubuntu5 (774 bytes)
Superseded in groovy-proposed |
mdadm (4.1-5ubuntu4) groovy; urgency=medium * d/p/mdcheck-when-mdcheck-start-is-enabled-mdcheck-continue-too.patch: - When mdcheck_start is enabled, enable mdcheck_continue too.
Available diffs
- diff from 4.1-5ubuntu3 to 4.1-5ubuntu4 (962 bytes)
mdadm (4.1-5ubuntu3) groovy; urgency=medium * 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. -- Eric Desrochers <email address hidden> Thu, 24 Sep 2020 09:14:49 -0400
Available diffs
- diff from 4.1-5ubuntu2 to 4.1-5ubuntu3 (1.0 KiB)
Superseded in focal-proposed |
mdadm (4.1-5ubuntu1.1) focal; urgency=medium * d/rules: Install misc/mdcheck (LP: #1852747) - The absence of mdcheck utility is preventing mdcheck_continue.service & mdcheck_start.service to execute the command when the service start via ExecStart. (Closes: #960132) * 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. -- Eric Desrochers <email address hidden> Thu, 24 Sep 2020 07:54:15 -0400
Available diffs
- diff from 4.1-5ubuntu1 to 4.1-5ubuntu1.1 (1.3 KiB)
mdadm (4.1-5ubuntu2) groovy; urgency=medium * d/rules: Install misc/mdcheck (LP: #1852747) - The absence of mdcheck utility is preventing mdcheck_continue.service & mdcheck_start.service to execute the command when the service start via ExecStart. (Closes: #960132) -- Eric Desrochers <email address hidden> Wed, 23 Sep 2020 14:08:32 -0400
Available diffs
- diff from 4.1-5ubuntu1 to 4.1-5ubuntu2 (609 bytes)
Superseded in groovy-release |
Published in focal-release |
Deleted in focal-proposed (Reason: moved to Release) |
mdadm (4.1-5ubuntu1) focal; urgency=medium [ dann frazier ] * Merge from Debian unstable. 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.
Available diffs
- diff from 4.1-4ubuntu1 to 4.1-5ubuntu1 (3.2 KiB)
mdadm (4.1~rc1-3~ubuntu18.04.4) bionic; urgency=medium * Introduce "broken" state for RAID0/Linear in mdadm (LP: #1847924) - d/p/lp1847924-Introduce-new-array-state-broken-for-raid0.patch * Disable patches from proposed version 4.1~rc1-3~ubuntu18.04.3 due to issues with kernel -- <email address hidden> (Guilherme G. Piccoli) Tue, 14 Jan 2020 16:10:59 -0300
Available diffs
mdadm (4.1-2ubuntu3.2) eoan; urgency=medium * Introduce "broken" state for RAID0/Linear in mdadm (LP: #1847924) - d/p/lp1847924-Introduce-new-array-state-broken-for-raid0.patch * Disable patches from proposed version 4.1-2ubuntu3.1 due to issues with kernel -- <email address hidden> (Guilherme G. Piccoli) Tue, 14 Jan 2020 17:09:06 -0300
Available diffs
Superseded in bionic-proposed |
mdadm (4.1~rc1-3~ubuntu18.04.3) bionic; urgency=medium * Add support for RAID0 layouts. Released kernels are being updated to require an explicit layout version for multi-zone RAID0 arrays to avoid potential corruption. This update allows users to program such a layout version into the metadata of an array. LP: #1850540 -- dann frazier <email address hidden> Wed, 04 Dec 2019 12:52:00 -0700
Available diffs
Obsolete in disco-proposed |
mdadm (4.1-1ubuntu1.1) disco; urgency=medium * Add support for RAID0 layouts. Released kernels are being updated to require an explicit layout version for multi-zone RAID0 arrays to avoid potential corruption. This update allows users to program such a layout version into the metadata of an array. LP: #1850540 -- dann frazier <email address hidden> Wed, 04 Dec 2019 12:44:30 -0700
Available diffs
- diff from 4.1-1ubuntu1 to 4.1-1ubuntu1.1 (6.4 KiB)
Superseded in eoan-proposed |
mdadm (4.1-2ubuntu3.1) eoan; urgency=medium * Add support for RAID0 layouts. Released kernels are being updated to require an explicit layout version for multi-zone RAID0 arrays to avoid potential corruption. This update allows users to program such a layout version into the metadata of an array. LP: #1850540 -- dann frazier <email address hidden> Wed, 04 Dec 2019 12:31:35 -0700
Available diffs
- diff from 4.1-2ubuntu3 to 4.1-2ubuntu3.1 (6.4 KiB)
mdadm (4.1-4ubuntu1) focal; urgency=medium [ dann frazier ] * Merge from Debian unstable. 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. [ Guilherme G. Piccoli ] * Introduce "broken" state for RAID0/Linear in mdadm (LP: #1847924) -- dann frazier <email address hidden> Wed, 04 Dec 2019 07:05:07 -0700
Available diffs
- diff from 4.1-2ubuntu3 to 4.1-4ubuntu1 (13.8 KiB)
Superseded in focal-release |
Obsolete in eoan-release |
Deleted in eoan-proposed (Reason: moved to release) |
mdadm (4.1-2ubuntu3) eoan; urgency=medium * 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. LP: #1815201 -- Dimitri John Ledkov <email address hidden> Tue, 18 Jun 2019 16:29:44 +0100
Available diffs
- diff from 4.1-2ubuntu2 to 4.1-2ubuntu3 (2.3 KiB)
mdadm (4.1-2ubuntu2) eoan; urgency=medium * Drop broken and unused init scripts in favor of native systemd units, which can cause failure to reconfigure mdadm package under certain confiment types. LP: #1829325 -- Dimitri John Ledkov <email address hidden> Mon, 20 May 2019 19:57:41 +0100
Available diffs
- diff from 4.1-2ubuntu1 to 4.1-2ubuntu2 (1.8 KiB)
mdadm (4.1-2ubuntu1) eoan; urgency=low * Merge from Debian unstable. Remaining changes: - Ship finalrd hook. - Do not install mdadm-shutdown.service on Ubuntu.
Available diffs
- diff from 4.1-1ubuntu1 to 4.1-2ubuntu1 (757 bytes)
mdadm (4.1~rc1-4ubuntu1.1) cosmic; urgency=medium * d/p/lp-1811228-imsm-Block-volume-creation-with-empty-name.patch: avoid creating whitespaced or empty names (LP: #1811228) * d/p/lp-1811795-remove-external-arrays-and-devices.patch: fix removal of failing disks with external metadata (LP: #1811795) -- Christian Ehrhardt <email address hidden> Wed, 10 Apr 2019 16:14:17 +0200
Available diffs
mdadm (4.1~rc1-3~ubuntu18.04.2) bionic; urgency=medium * d/p/lp-1811228-imsm-Block-volume-creation-with-empty-name.patch: avoid creating whitespaced or empty names (LP: #1811228) * d/p/lp-1811795-remove-external-arrays-and-devices.patch: fix removal of failing disks with external metadata (LP: #1811795) -- Christian Ehrhardt <email address hidden> Wed, 10 Apr 2019 16:14:17 +0200
Available diffs
Superseded in eoan-release |
Obsolete in disco-release |
Deleted in disco-proposed (Reason: moved to release) |
mdadm (4.1-1ubuntu1) disco; urgency=low * Merge from Debian unstable. Remaining changes: - Ship finalrd hook. - Do not install mdadm-shutdown.service on Ubuntu.
Available diffs
- diff from 4.1~rc1-4ubuntu1 to 4.1-1ubuntu1 (55.6 KiB)
Superseded in disco-release |
Obsolete in cosmic-release |
Deleted in cosmic-proposed (Reason: moved to release) |
mdadm (4.1~rc1-4ubuntu1) cosmic; urgency=medium * Ship finalrd hook. * Do not install mdadm-shutdown.service on Ubuntu. -- Dimitri John Ledkov <email address hidden> Fri, 03 Aug 2018 14:53:18 +0100
Available diffs
mdadm (4.1~rc1-4) unstable; urgency=medium * Cherrypick master patches up to 20th of July 2018. LP: #1781427 * Make safe-timouts udev rules compatible with usr-split systems. -- Dimitri John Ledkov <email address hidden> Mon, 23 Jul 2018 11:48:50 +0100
Available diffs
- diff from 4.1~rc1-3 to 4.1~rc1-4 (14.3 KiB)
mdadm (4.1~rc1-3~ubuntu18.04.1) bionic; urgency=medium * No-change backport to bionic to enable Intel VROC support LP: #1779685
Available diffs
mdadm (4.1~rc1-3) unstable; urgency=medium * Cherrypick master patches up to 4th of June 2018. -- Dimitri John Ledkov 🌈 <email address hidden> Tue, 26 Jun 2018 15:38:04 +0100
Available diffs
- diff from 4.1~rc1-2 to 4.1~rc1-3 (12.4 KiB)
mdadm (4.0-2ubuntu1.1) bionic; urgency=medium * Install identical udev rules into d-i installer udeb, as used in the installed system. Specifically, post-processed rules with full path to mdadm binary subsituted, instead of installing useless rules with the template variable BINDIR. LP: #1705215 -- Dimitri John Ledkov <email address hidden> Thu, 24 May 2018 11:14:57 +0100
Available diffs
- diff from 4.0-2ubuntu1 to 4.0-2ubuntu1.1 (750 bytes)
mdadm (4.1~rc1-2) unstable; urgency=medium * Install identical udev rules into d-i installer udeb, as used in the installed system. Specifically, post-processed rules with full path to mdadm binary subsituted, instead of installing useless rules with the template variable BINDIR. LP: #1705215 -- Dimitri John Ledkov <email address hidden> Tue, 22 May 2018 14:26:59 +0100
Available diffs
- diff from 4.1~rc1-1 to 4.1~rc1-2 (722 bytes)
mdadm (4.1~rc1-1) unstable; urgency=medium * New upstream release. * Import patches since rc1. * Bump standards version & debhelper compat. -- Dimitri John Ledkov <email address hidden> Tue, 15 May 2018 12:10:33 +0100
Available diffs
- diff from 4.0-2ubuntu1 (in Ubuntu) to 4.1~rc1-1 (138.7 KiB)
Superseded in cosmic-release |
Published in bionic-release |
Deleted in bionic-proposed (Reason: moved to release) |
mdadm (4.0-2ubuntu1) bionic; urgency=medium * Cherry-pick upstream patch to ensure mdadm-last-resort services only runs when it is needed LP: #1753786 - debian/patches/mdadm-last-resort-use-condition-path-exists.patch -- Ryan Harper <email address hidden> Wed, 07 Mar 2018 01:43:16 -0600
Available diffs
mdadm (3.3-2ubuntu7.6) xenial; urgency=medium * Prevent segfault when get_md_name() returns NULL This fixes mdadm segfaults when running inside a container. (LP: #1617919) -- Dan Streetman <email address hidden> Mon, 09 Oct 2017 10:06:22 -0400
Available diffs
mdadm (3.2.5-5ubuntu4.4) trusty; urgency=medium * Prevent segfault when get_md_name() returns NULL This fixes mdadm segfaults when running inside a container. (LP: #1617919) -- Dan Streetman <email address hidden> Mon, 09 Oct 2017 10:06:22 -0400
Available diffs
mdadm (3.4-4ubuntu0.1) zesty; urgency=medium * Ship mdadm-shutdown.service and suggest dracut-core. Users of systemd with rootfs on Intel Matrix Raid and DDF external metadata-raid arrays that require mdmon monitoring, may wish to install dracut-core package and enable mdadm-shutdown.service. This will create a shutdown initramfs, that systemd-shutdown can pivot to. This may result in an improved shutdown behaviour with less hangs and synced raid arrays. The generated initramfs will takeover mdmon monitoring, wait for the arrays to be clean before stopping them and unmounting everything and finally executing requested shutdown command. LP: #1722491 -- Dimitri John Ledkov <email address hidden> Fri, 13 Oct 2017 18:31:49 +0100
Available diffs
Superseded in bionic-release |
Obsolete in artful-release |
Deleted in artful-proposed (Reason: moved to release) |
mdadm (4.0-2) unstable; urgency=medium * Ship mdadm-shutdown.service and suggest dracut-core. Users of systemd with rootfs on Intel Matrix Raid and DDF external metadata-raid arrays that require mdmon monitoring, may wish to install dracut-core package and enable mdadm-shutdown.service. This will create a shutdown initramfs, that systemd-shutdown can pivot to. This may result in an improved shutdown behaviour with less hangs and synced raid arrays. The generated initramfs will takeover mdmon monitoring, wait for the arrays to be clean before stopping them and unmounting everything and finally executing requested shutdown command. * Bump standards version, no changes required. * Bump debhelper to 9. * Add second email address to avoid NMU warnings. -- Dimitri John Ledkov <email address hidden> Tue, 10 Oct 2017 11:55:52 +0100
Available diffs
- diff from 4.0-1 to 4.0-2 (1.7 KiB)
mdadm (3.3-2ubuntu7.5) xenial; urgency=medium * Add systemd shutdown script which waits for arrays to be clean during shutdown phase. * Do not take over initramfs mdmon services, and continue running them off initrd to avoid killing mdmon processes before systemd attempts dm detach and hang. As systemd in xenial does not appear to honor sendsigs.omit.d. * Add mdadm-shutdown.service which is recommended to be used on systems with Intel Matrix / DDF raid. It creates a shutdown initramfs which systemd-shutdown may pivot to, and complete clean external metadata raid array shutdown. * LP: #1722491 -- Dimitri John Ledkov <email address hidden> Mon, 09 Oct 2017 14:56:09 +0100
Available diffs
mdadm (3.3-2ubuntu7.4) xenial; urgency=medium * Drop versioned dependency on initramfs-tools, which was only needed for upgrades and now keeps initramfs-tools installed on systems that don't need it. LP: #1716818. * Guard calls to update-initramfs -u in the maintainer scripts for a check that the script is present. -- Steve Langasek <email address hidden> Wed, 13 Sep 2017 03:52:18 +0000
Available diffs
Superseded in xenial-proposed |
mdadm (3.3-2ubuntu7.3) xenial; urgency=medium * Drop versioned dependency on initramfs-tools, which was only needed for upgrades and now keeps initramfs-tools installed on systems that don't need it. LP: #1716818. * Guard calls to update-initramfs -u in the maintainer scripts for a check that the script is present. -- Steve Langasek <email address hidden> Wed, 13 Sep 2017 03:52:18 +0000
Available diffs
mdadm (4.0-1) unstable; urgency=medium * New upstream release. LP: #1668128 * Drop warnings that raid arrays are missing from the initramfs configuration. Instead have a positive message as to which arrays are included in the initramfs. * Add a warning to mkconf generated file that mdadm.conf is copied into initrafms. * Fix checkarray script bugs. LP: #1599428 Closes: #787950 Closes: #843665 -- Dimitri John Ledkov <email address hidden> Thu, 22 Jun 2017 13:23:10 +0100
Available diffs
- diff from 3.4-4 to 4.0-1 (67.7 KiB)
mdadm (3.3-2ubuntu7.2) xenial; urgency=medium * Backport initramfs changes from 3.4-4, to improve reliability of booting with degraded arrays. LP: #1635049 * debian/initramfs/hook: - Fix UUID= grep for configured RAIDs to be case insensitive. - Drop CREATE stanzas from mkconf and don't include them in the initramfs. The generated defaults, are the compiled-in defaults. And the current one generates warnings when running mdadm in the initramfs, as there is no passwd|group files to resolve root/disk uid/gid. * debian/initrmafs/script.local-block|script.local-bottom: - Use local-block integration scrips, in favor of root-fail hooks to activate incomplete arrays. * debian/initramfs/init-premount|mdadm-functions: - Drop, no longer in use. -- Dimitri John Ledkov <email address hidden> Mon, 20 Feb 2017 10:57:43 +0000
Available diffs
Superseded in artful-release |
Obsolete in zesty-release |
Obsolete in yakkety-release |
Deleted in yakkety-proposed (Reason: moved to release) |
mdadm (3.4-4) unstable; urgency=high * Bring in changes from Ubuntu, to make the two packages in sync: - Drop README.Debian, quite out-of-date w.r.t. current packaging. - debian/control - on ubuntu, downgrade default-mta from Recommends to Suggests. - update-grub in postinst, if available (note does not update grub1). - drop stderr warnings in postrm. - drop presubj, out of date, and all types of bugs are welcomed. - on ubuntu, install apport package hook. - on ubuntu, install incremental assembly udev rules into udeb. -- Dimitri John Ledkov <email address hidden> Thu, 28 Jul 2016 16:52:07 +0100
Available diffs
- diff from 3.4-3 to 3.4-4 (5.3 KiB)
mdadm (3.4-3) unstable; urgency=high * Fix UUID= grep for configured RAIDs to be case incesetive, regression from 3.4-2. * Re-trigger block devices at the start of local-block mdadm loop, to re-incrementally assemble disks that appeared before RAID personalities were registered with the kernel. * Also, invoke non-incremental assembly of raid arrays in the local-block loop to support running mdadm with user-exported variables specified via param.conf. * Set Vcs- fields to dgit repositories. * Closes: #830770, #830300. -- Dimitri John Ledkov <email address hidden> Tue, 26 Jul 2016 17:09:54 +0100
Available diffs
- diff from 3.3-2ubuntu9 (in Ubuntu) to 3.4-3 (210.3 KiB)
mdadm (3.3-2ubuntu9) yakkety; urgency=medium * Drop obsolete initscripts dependency. (Closes: #804973) -- Martin Pitt <email address hidden> Wed, 22 Jun 2016 16:21:25 +0200
Available diffs
- diff from 3.3-2ubuntu8 to 3.3-2ubuntu9 (567 bytes)
mdadm (3.2.5-5ubuntu4.3) trusty; urgency=medium * debian/source_mdadm.py: fix bytes versus strings mismatch that caused the apport hook to fail (LP: #1583279) -- Steve Beattie <email address hidden> Wed, 18 May 2016 15:48:46 -0700
Available diffs
mdadm (3.3-2ubuntu2.1) wily-proposed; urgency=medium * debian/source_mdadm.py: fix bytes versus strings mismatch that caused the apport hook to fail (LP: #1583279) -- Steve Beattie <email address hidden> Wed, 18 May 2016 16:18:51 -0700
Available diffs
- diff from 3.3-2ubuntu2 to 3.3-2ubuntu2.1 (1.1 KiB)
mdadm (3.3-2ubuntu7.1) xenial-proposed; urgency=medium * debian/source_mdadm.py: fix bytes versus strings mismatch that caused the apport hook to fail (LP: #1583279) -- Steve Beattie <email address hidden> Wed, 18 May 2016 15:24:48 -0700
Available diffs
- diff from 3.3-2ubuntu7 to 3.3-2ubuntu7.1 (1.0 KiB)
mdadm (3.3-2ubuntu8) yakkety; urgency=medium * debian/source_mdadm.py: + fix bytes versus strings mismatch that caused the apport hook to fail (LP: #1583279) + capture grub.cfg for grub2 + pyflakes and pep8 cleanups -- Steve Beattie <email address hidden> Wed, 18 May 2016 13:31:04 -0700
Available diffs
- diff from 3.3-2ubuntu7 to 3.3-2ubuntu8 (1.3 KiB)
Superseded in yakkety-release |
Published in xenial-release |
Deleted in xenial-proposed (Reason: moved to release) |
mdadm (3.3-2ubuntu7) xenial; urgency=medium * Do not start when inside a container (LP: #1568993) -- Simon Deziel <email address hidden> Mon, 11 Apr 2016 18:33:45 +0000
Available diffs
- diff from 3.3-2ubuntu6 to 3.3-2ubuntu7 (576 bytes)
mdadm (3.3-2ubuntu6) xenial; urgency=medium * debian/cotrol: Drop MTA Recommends to a Suggests (LP #1549319) -- Adam Conrad <email address hidden> Thu, 24 Mar 2016 16:39:13 -0600
Available diffs
- diff from 3.3-2ubuntu5 to 3.3-2ubuntu6 (694 bytes)
mdadm (3.3-2ubuntu5) xenial; urgency=medium * Drop grub override, and thus use mdadm to assemble ISMS and DDF raids. -- Dimitri John Ledkov <email address hidden> Fri, 19 Feb 2016 17:27:12 +0000
Available diffs
- diff from 3.3-2ubuntu4 to 3.3-2ubuntu5 (600 bytes)
mdadm (3.3-2ubuntu4) xenial; urgency=low * debian/control: recommend kmod in preference to module-init-tools. -- Andy Whitcroft <email address hidden> Wed, 17 Feb 2016 11:43:15 +0000
Available diffs
- diff from 3.3-2ubuntu3 to 3.3-2ubuntu4 (674 bytes)
mdadm (3.3-2ubuntu3) xenial; urgency=medium * debian/mdadm.init: Stop depending on mdadm-raid, as we removed that init script in Ubuntu in favor of udev rules. -- Martin Pitt <email address hidden> Fri, 11 Dec 2015 10:03:17 +0100
Available diffs
- diff from 3.3-2ubuntu2 to 3.3-2ubuntu3 (575 bytes)
mdadm (3.2.5-5ubuntu4.2) trusty; urgency=medium * debian/dmraid2mdadm.cfg: Only append to GRUB_CMDLINE_LINUX_DEFAULT one time. (LP: #1465567) -- Iain Lane <email address hidden> Tue, 16 Jun 2015 11:06:14 +0100
Available diffs
- diff from 3.2.5-5ubuntu4.1 to 3.2.5-5ubuntu4.2 (527 bytes)
mdadm (3.3-2ubuntu1.1) vivid; urgency=medium * debian/dmraid2mdadm.cfg: Only append to GRUB_CMDLINE_LINUX_DEFAULT one time. (LP: #1465567) -- Iain Lane <email address hidden> Tue, 16 Jun 2015 10:56:44 +0100
Available diffs
- diff from 3.3-2ubuntu1 to 3.3-2ubuntu1.1 (513 bytes)
Superseded in xenial-release |
Obsolete in wily-release |
Deleted in wily-proposed (Reason: moved to release) |
mdadm (3.3-2ubuntu2) wily; urgency=medium * debian/dmraid2mdadm.cfg: Only append to GRUB_CMDLINE_LINUX_DEFAULT one time. (LP: #1465567) -- Iain Lane <email address hidden> Tue, 16 Jun 2015 10:48:09 +0100
Available diffs
- diff from 3.3-2ubuntu1 to 3.3-2ubuntu2 (509 bytes)
Superseded in wily-release |
Obsolete in vivid-release |
Obsolete in utopic-release |
Deleted in utopic-proposed (Reason: moved to release) |
mdadm (3.3-2ubuntu1) utopic; urgency=medium * Merge from Debian unstable, remaining changes: - debian/initramfs/mdadm-functions: add call wait_for_udev to wait a little longer for RAID devices to appear. - debian/control: we need udev and util-linux in the right version. We also remove the build dependency from quilt and docbook-to-man as both are not used in Ubuntus mdadm. - debian/initramfs/hook: kept the Ubuntus version for handling the absence of active raid arrays in <initramfs>/etc/mdadm/mdadm.conf - debian/initramfs/script.local-top.DEBIAN, debian/mdadm-startall, debian/mdadm.raid.DEBIAN: removed. udev does its job now instead. - debian/mdadm-startall.sgml, debian/mdadm-startall.8: documentation of unused startall script - debian/mdadm.config, debian/mdadm.postinst - let udev do the handling instead. Resolved merge conflict by keeping Ubuntu's version. - debian/mkconf.in is the older mkconf. Kept the Ubuntu version. - debian/rules: Kept Ubuntus version for installing apport hooks, not installing un-used startall script. - debian/presubj: Dropped this unused bug reporting file. Instead use source_mdadm.py act as an apport hook for bug handling. - d/p/debian-changes-3.1.4-1+8efb9d1ubuntu4: mdadm udev rule incrementally adds mdadm member when detected. Starting such an array in degraded mode is possible by mdadm -IRs. Using mdadm -ARs without stopping the array first does nothing when no mdarray-unassociated device is available. Using mdadm -IRs to start a previously partially assembled array through incremental mode. Keeping the mdadm -ARs for assembling arrays which were for some reason not assembled through incremental mode (i.e through mdadm's udev rule). - Take kernel cmdline parameters "nomdmonisw" and "nomdmonddf" into account, when assembling imsm/ddf arrays. This defaults to assembling those arrays using mdmon/mdadm, with a fallback to dmraid upon request. - Use default/grub.d snippet to continue using dmraid to assemble fakeraid arrays. * Install incremental assembly rules. * Disable use-external-blkid.diff, udev in Ubuntu is recent enough.
Available diffs
- diff from 3.2.5-5ubuntu5 to 3.3-2ubuntu1 (299.6 KiB)
mdadm (3.2.5-5ubuntu4.1) trusty; urgency=medium * Instead of calling update-grub in postinst, call update-grub2. (LP: #1285312) Although machines installed in this decade would have grub2's update-grub, this is not the case for machines upgraded into this decade from e.g. 8.04 LTS in which case update-grub would be grub1 with which this package doesn't integrate any more. All users who have not yet upgraded to grub2 are urged to upgrade to grub following instructions at: https://help.ubuntu.com/community/Grub2/Upgrading -- Dimitri John Ledkov <email address hidden> Wed, 30 Apr 2014 20:42:45 +0100
Available diffs
- diff from 3.2.5-5ubuntu4 to 3.2.5-5ubuntu4.1 (701 bytes)
mdadm (3.2.5-5ubuntu5) utopic; urgency=medium * Instead of calling update-grub in postinst, call update-grub2. (LP: #1285312) Although machines installed in this decade would have grub2's update-grub, this is not the case for machines upgraded into this decade from e.g. 8.04 LTS in which case update-grub would be grub1 with which this package doesn't integrate any more. All users who have not yet upgraded to grub2 are urged to upgrade to grub following instructions at: https://help.ubuntu.com/community/Grub2/Upgrading -- Dimitri John Ledkov <email address hidden> Wed, 30 Apr 2014 20:42:45 +0100
Available diffs
- diff from 3.2.5-5ubuntu4 to 3.2.5-5ubuntu5 (700 bytes)
Superseded in utopic-release |
Published in trusty-release |
Deleted in trusty-proposed (Reason: moved to release) |
mdadm (3.2.5-5ubuntu4) trusty; urgency=medium * Don't fail package configure if update-grub fails for any reason, e.g. not use. (LP: #1284514) -- Dimitri John Ledkov <email address hidden> Fri, 28 Feb 2014 11:03:28 +0000
Available diffs
- diff from 3.2.5-5ubuntu3 to 3.2.5-5ubuntu4 (490 bytes)
mdadm (3.2.5-5ubuntu3) trusty; urgency=medium * Drop precise-sru-reverts.patch, which disabled imsm/ddf raid assembly. * Take kernel cmdline parameters "nomdmonisw" and "nomdmonddf" into account, when assembling imsm/ddf arrays. This defaults to assembling those arrays using mdmon/mdadm, with a fallback to dmraid upon request. * Add breaks on dmraid, of versions that assemble fakeraid devices by default. * Drop degraded array questions, since the degraded check results in false negatives (e.g. all drives present & started arrays, yet resyncing) assemble arrays as best as is possible. (LP: #1279741) * Use default/grub.d snippet to continue using dmraid to assemble fakeraid arrays. -- Dimitri John Ledkov <email address hidden> Tue, 18 Feb 2014 09:12:20 +0000
Available diffs
1 → 75 of 152 results | First • Previous • Next • Last |