Dear Maintainer,

Currently, zfs-initramfs and zfs-dracut are not co-installable,
because they have Depends: initramfs-tools and dracut, respectively,
and those conflict.

initramfs-tools and dracut are the "please use
initramfs-tools-core/dracut-core to generate system initrds"
integration-only packages.

The actual generation program and plugins are provided in the
-core packages. Please consider the attached patches, based on recent
Salsa, to make them co-installable.

Best,
наб

Dear наб,

I don’t think that proposed patches have a practical value, in fact, they make things worse.
E.g. I expect to have a working initrd by installing a kernel and zfs-initramfs when I bootstrap a Debian ZFS install.
And I barely imagine a situation when a user uses one of initrd generators and needs to have *-core package of second one installed at the same time.

You will be delighted to know, then, that this continues to work.
Conversely, imagining (and being in) such a situation is very easy to me.
This is the reason why they are made co-installable, and only the "bare"
dracut/initramfs-tools packages aren't.

наб

Hi,

If I understand correctly, the -core packages provide the tools for
generating initramfs, but they'll not automatically update the actual
initramfs image. Depending only on the -core packages looks a bit
unusual for integration packages like zfs-initramfs and zfs-dracut,
for example cryptsetup,dropbear (they do not provide -dracut package,
though), and clevis.

Regards,
Aron

The package is intended for normal users, for whom installing both dracut
and initramfs-tools seems really rare and weird. Also your patch will even render
the system not usable because now initramfs no more updates when zfs upgrades.

It is possible to further split packages into, e.g., zfs-{initramfs,dracut}-core
that depends on their corresponding underlying -core packages, and make
zfs-{initramfs,dracut} depend on them. However I haven't heard similar
use cases from any other users.

Thanks,
Shengqi Chen