forcemerge 548629 541884
thanks
On Sep 27, Petter Reinholdtsen wrote:
> What need to be fixed in mdadm? I find this changelog entry for udev
> mentioning mdadm, but it do not explain what need to be changed.
It needs to stop using vol_id which does not exist anymore:
> + vol_id and libvol
Processing commands for cont...@bugs.debian.org:
> forcemerge 548629 541884
Bug#548629: udev conflict with mdadm and cause removing mdadm package
Bug#541884: must use blkid instead of vol_id
Forcibly Merged 541884 548629.
> thanks
Stopping processing here.
Please contact me if yo
[Marco d'Itri]
> It's mdadm which needs to be fixed.
What need to be fixed in mdadm? I find this changelog entry for udev
mentioning mdadm, but it do not explain what need to be changed.
udev (146-1) experimental; urgency=low
* New upstream release.
+ vol_id and libvolume_id have been
Processing commands for cont...@bugs.debian.org:
> severity 548629 grave
Bug #548629 [udev] udev conflict with mdadm and cause removing mdadm package
Severity set to 'grave' from 'normal'
> reassign 548629 mdadm
Bug #548629 [udev] udev conflict with mdadm and cause removing mdadm package
Bug reas
4 matches
Mail list logo