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.
mdadm (3.3-2) unstable; urgency=low
* use 63-md-raid-arrays.rules instead of old 64-md-raid.rules
(Closes: #726237)
* do not use builtin blkid in udev rules, as our udev (at least
on wheezy) does not have it (use-external-blkid.diff)
mdadm (3.3-1) unstable; urgency=low
[ Michael Tokarev ]
* new upstream 3.3 release (Closes: #718896)
See ANNOUNCE-3.3 for details.
Patches:
- refreshed debian-conffile-location.diff
(added .conf.d)
- removed debian-disable-udev-incr-assembly.diff
(do not ship udev-md-raid-assembly.rules for now)
- refreshed debian-no-Werror.diff
- refreshed sha1-includes.diff
- removed patches (included upstream)A:
spelling-and-manpages.patch
fix-enough-function-for-RAID10.patch
fix-segfaults-in-detail.patch
super0-do-not-override-uuid-with-homehost.patch
mdmon-allow-takeover-when-original-was-started-with-.patch
mdmon-fix-arg-parsing.patch
mdmon-fix-arg-processing-for-a.path
Install udev-md-raid-arrays.rules instead of udev-md-raid.rules,
don't install new udev-md-raid-assembly.rules for now.
* remove Martin F. Krafft from uploaders per his request.
Thank you for your contributions!
* added remove-bashism-from-makefile.patch patch to work around
newly introduced bashism
* remove debian/source/options, there's no need to set compression
options for debian.tar.gz.
* remove outdated debian/docs/md_superblock_formats.txt and
debian/docs/md.txt (Closes: #714977, #714978)
* ship ANNOUNCE-*, external-reshape-design.txt, mdmon-design.txt
files as documentation (Closes: #715324)
[ Dmitrijs Ledkovs ]
* Properly remove 65-mdadm.vol_id.rules, instead of trying to remove a
never-existed 65_mdadm.vol_id.rules (note the 65- vs 65_).
mdadm (3.2.5-6) unstable; urgency=low
* replace home-grown and not-working-since-etch udevsettle call
in initramfs script with proper wait_for_udev function (from
common initramfs functions). This unbreaks situations when
the underlying device needs some udev magic to happen before
being available, which includes stacked devices (md on lvm)
and other cases. Thanks to Thomas Parmelan and Dave Whitla
for finding the root cause of breakage and for providing
the fix. (Closes: #644876)
-- Dimitri John Ledkov <email address hidden> Thu, 17 Jul 2014 14:49:19 +0100
