st 6. 11. 2024 v 19:04 odesílatel Christoph Biedl
<debian.a...@manchmal.in-ulm.de> napsal:
>
> Control: tags 1086553 pending
> Control: tags 1086554 pending
>
> Oldřich Jedlička wrote...
>
> > I am testing various clevis implementations (thus using more recent custom
> > build) and I think it would be good for clevis-initramfs package to depend
> > on initramfs-tools-core rather than on initramfs-tools. This would allow
> > having both clevis-initramfs and clevis-dracut versions installed at the
> > same
> > time.
>
> This seems sensible. There's just one bit of information I needed to
> answer a question possible other people will ask as well: Will this
> break regular usage, especially (re-)creating the respective initramfs
> for a new kernel and/or clevis version?
>
> The answer is "no", as (for amd64) linux-image-amd64 depends on some
> versioned kernel package (currenty linux-image-6.11.5-amd64), and that
> depends on initramfs-tools | linux-initramfs-tool, and dracut provides
> the latter. So the initramfs-tools (or dracut) will still be required
> despite clevis-{initramfs,dracut} no longer depend on them.
This does not break image creation. The configuration is prepared by the
clevis-initramfs and clevis-dracut packages for the respective tool and it
then depends on whether you call `update-initramfs -u` or `dracut -f` to
create the actual image. The automatic image creation (after kernel update
for example) works still the same.
With custom-built clevis (with the updated dependencies) I was able to call
update-initramfs -u
dracut -f /boot/initrd.img-6.1.0-25-amd64.dracut
and I got bootable images /boot/initrd.img-6.1.0-25-amd64 (automatic one) and
/boot/initrd.img-6.1.0-25-amd64.dracut (manual one).
I found one more dependency forcing installation of initramfs-tools, which is
cryptsetup-initramfs, so I might fill a similar feature request for that
package too.
Oldrich.
>
> Upload of the new clevis upstream version will follow soon.
>
> Christoph
