Bug#726390: switch to upstream udev rules
Michael Tokarev
mjt at tls.msk.ru
Tue Oct 15 12:54:44 UTC 2013
Control: tag -1 wontfix
15.10.2013 14:10, email.bug at arcor.de wrote:
> Package: mdadm
>
> Wondering about why nothing happened when hot-plugging a
> raid member drive, I found the following answer in the changelog:
>
> * disabled the incremental assembly upstream turned on in 3.1.3 for
> now, this will have to wait until after the squeeze release.
>
> And saw the Maintainer changed. Many thanks to all for maintaining
> the package in the past and ongoing!
>
> Maybe it is possible to shed some light about the current state
> and the intentions of enabling upsteam's incremental/hotplug code
> (udev rules) in Debian?
I plan to work on auto-assembly support in debian in a near future,
so that jessie should definitely have it.
We already use upstream udev rules, for a long time, so this
bugreport makes no sense as it is filed.
However, upstream udev rules as-is wont work because udev as
shipped in debian does not have blkid built-in, so upstream
rules (which uses IMPORT{builtin}=blkid) does not work, and
I had to patch it to use external blkid. Hence I mark this
bug as wontfix, because I don't want to break mdadm in debian
by switching to upstream rules.
Thanks,
/mjt
More information about the pkg-mdadm-devel
mailing list