Update mdadm in Jammy to 4.2 Official
Bug #1959843 reported by
Jeff Lane
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| mdadm (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Currently, we have mdadm 4.2~RC2 in Jammy:
mdadm | 4.2~rc2-2ubuntu1 | jammy | source, amd64, arm64, armhf, i386, ppc64el, riscv64, s390x
but 4.2 has now been officially released and debian has what I think is 4.2 official in Sid.
mdadm | 4.2-1 | unstable | source, amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
Could we please update what we're pulling for mdadm so we have 4.2 official in Jammy?
| tags: | added: needs-merge |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in mdadm (Ubuntu): | |
| status: | New → Fix Released |
| Changed in mdadm (Ubuntu): | |
| milestone: | none → jammy-updates |
To post a comment you must log in.
This bug was fixed in the package mdadm - 4.2-0ubuntu1
---------------
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