Bogus dependency on mdadm
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lvm-common (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: lvm-common
root@echo:~# LANG=C aptitude install lvm2
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Building tag database... Done
The following NEW packages will be automatically installed:
lvm-common mdadm
LVM has no dependency on mdadm, as it can easily be used directly on other, non-md, devices. I do it all the time, no problems at all. This dependency should be demoted to a suggests or recommends, especially because mdadm, when installed on a machine not using md devices, by default makes noise during boot and when initrd images are made, and also starts a useless monitoring daemon.
Tore
Related branches
Changed in lvm-common: | |
status: | Unconfirmed → In Progress |
So this is the reason for mdadm being installed?
I kept wondering why I have to have a raid-manager when I don't have or plan on having a raid in my system. :/
What is the reason for this dependency? Why does every user, with or without raid-systems, get this? These
W: mdadm: /etc/mdadm/ mdadm.conf defines no arrays.
W: mdadm: no arrays defined in configuration file.
W: mdadm: falling back to emergency procedure in initramfs.
messages are getting kind of annoying. Especially on systemupgrades.