A few weeks ago, the lvm2/device-mapper package has been split up into multiple subpackages to be more in line with the shared library packaging guideline. With this, it became possible to throw out the device-mapper package from your system if all you needed was cryptsetup. cryptsetup-1.7.0-1.4.x86_64 libdevmapper1_03-1.02.124-65.2.x86_64 (no lvm2-*, no device-mapper-*) cryptsetup itself works as expected, but mkinitrd/dracut rejects creating an initrd supporting crypto volumes, as it uses and therefore depends on /sbin/dmsetup, provided by device-mapper.rpm. So I had a little surprise yesterday when I played with^W^W botched a VM, because of course, mkinitrd ran as part of `zypper dup` and its output subsequently got ignored :-) # mkinitrd Creating initrd: /boot/initrd-4.6.0-rc6-1.ga3fdd2b-default [...] dracut: dracut module 'dm' will not be installed, because command 'dmsetup' could not be found! dracut: dracut module 'crypt' depends on 'dm', which can't be installed dracut: dracut module 'dmraid' will not be installed, because command 'dmraid' could not be found! dracut: dracut module 'lvm' will not be installed ,because command 'lvm' could not be found! I wondered whether there exists a possibility to improve that if ever so slightly without forcing the installation where the feature is not desired. 1. devicemapper.spec: Supplements: packageand(cryptsetup,dracut) ? or 2. Maybe it's worthwhile to split dracut and have a dracut-crypt.rpm which hard-Requires cryptsetup, device-mapper? 3. Other ideas you have? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org