This bug was fixed in the package mdadm - 3.2.5-1ubuntu0.2
---
mdadm (3.2.5-1ubuntu0.2) precise-proposed; urgency=low
* Patch udev-md-raid.rules to not auto-start arrays based on detection
of ddf or isw (imsm) signatures; this conflicts with dmraid usage in
precise and requi
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1002357
Title:
sort out udev rules madness (3 editions installed into 4 files)
To
Test case #2:
I have successfully created 0.9, 1.0, 1.1 and 1.2 format raid arrays with
old&new mdadm, which preserved/mounted across reboots and upgrades from precise
to precise-proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Testcase #1: Done.
$ apt-get download mdadm
$ wget
http://ubuntu.mirror.cambrium.nl/ubuntu//pool/main/m/mdadm/mdadm-udeb_3.2.3-2ubuntu1_amd64.udeb
$ dpkg-deb -R mdadm_*.deb standard
$ dpkg-deb -R mdadm-udeb*deb udeb
$ find . -name '*.rules' | xargs -L 1 md5sum
e143161798744026d7e4aac78e0bfede
.
** Description changed:
[IMPACT]
* Previously 3 different versions of udev rules where installed into 4
places (2 in the deb and 2 in the udeb)
* This causes confusion, as multiple mdadm rules are run. It is not
clear to the system administrator which udev rule to override in /et
@Steve Langasek, done.
** Description changed:
[IMPACT]
* Previously 3 different versions of udev rules where installed into 4
places (2 in the deb and 2 in the udeb)
* This causes confusion, as multiple mdadm rules are run. It is not
clear to the system administrator which udev
Dmitrijs, I think rather than noting that DDF and IMSM arrays are
affected, I think a good second test case here would be to explicitly
construct several different kinds of raid arrays and verify that the new
udev rules can handle them correctly?
--
You received this bug notification because you
Hello Dmitrijs, or anyone else affected,
Accepted mdadm into precise-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/mdadm/3.2.5-1ubuntu0.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://w
** Changed in: mdadm (Ubuntu Precise)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1002357
Title:
sort out udev rules madness (3 editions installed into 4 file
** Description changed:
[IMPACT]
- * Previously 3 different versions of udev rules where installed into 4
+ * Previously 3 different versions of udev rules where installed into 4
places (2 in the deb and 2 in the udeb)
- * This causes confusion, as multiple mdadm rules are run. It is
Is this still on target for 12.04.1?
** Changed in: mdadm (Ubuntu Precise)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1002357
Title:
sort out udev rules madne
** Description changed:
- # Sensible udev rules in debian
- $ find sid/debian/ -name '*.rules' | xargs -L 1 md5sum
- 6df86db16655769fa94086d3ee13453a
sid/debian/mdadm/lib/udev/rules.d/64-md-raid.rules
- 6df86db16655769fa94086d3ee13453a
sid/debian/mdadm-udeb/lib/udev/rules.d/64-md-raid.rules
+
** Changed in: mdadm (Ubuntu Precise)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1002357
Title:
sort out udev rules madness (3 editions installed into 4 files)
** Changed in: mdadm (Ubuntu Precise)
Milestone: None => ubuntu-12.04.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1002357
Title:
sort out udev rules madness (3 editions installed into 4 file
** Also affects: mdadm (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: mdadm (Ubuntu Quantal)
Importance: Undecided
Assignee: Dmitrijs Ledkovs (dmitrij.ledkov)
Status: Fix Released
** Changed in: mdadm (Ubuntu Precise)
Status: New => Confirmed
This bug was fixed in the package mdadm - 3.2.3-2ubuntu2
---
mdadm (3.2.3-2ubuntu2) quantal; urgency=low
* Minimizing the merge-diff from Debian:
+ debian/rules, debian/mdadm.udev, debian/mdadm.mdadm-blkid.udev:
Drop our own udev rules in favour of upstream's. Debian did s
** Changed in: mdadm (Ubuntu)
Status: New => In Progress
** Changed in: mdadm (Ubuntu)
Assignee: (unassigned) => Dmitrijs Ledkovs (dmitrij.ledkov)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
** Branch linked: lp:~dmitrij.ledkov/ubuntu/quantal/mdadm/merge
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1002357
Title:
sort out udev rules madness (3 editions installed into 4 files)
To manag
18 matches
Mail list logo
