[ Reordering slightly ]
Cyril Brulebois <kibi@debian.org> (2023-05-02):
> Paul Seelig <thinkpad@rumbero.org> (2023-05-02):
> > Attached installation logs should be sufficiently verbose about what
> > actually happened underneath.
>
> Either it was forgotten or dropped by the BTS; please use reply-all,
> and attach it compressed (to avoid hitting size limits on either the
> BTS side or on the debian-boot ML side).
For reference:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035360#10
- https://bugs.debian.org/cgi-bin/bugreport.cgi?att=2;bug=1035360;filename=installer-logs.tar.xz;msg=10
> > Apparently, the required cryptsetup-initramfs packages were removed
> > from the system during the last instalation stages, rendering the
> > resulting system unbootable.
That's not quite what happened. Instead, the cryptsetup-initramfs wasn't
available to start with:
Apr 30 16:11:44 in-target: Package cryptsetup-initramfs is not available, but is referred to by another package.
Apr 30 16:11:44 in-target: E: Package 'cryptsetup-initramfs' has no installation candidate
Later on, cryptsetup got removed along with a bunch of live packages.
Presumably, if cryptsetup-initramfs had been successfully installed, it
would have kept cryptsetup around.
Again, I'm not familiar with the live environment, it'd be great if some
with some knowledge about the way it operates and/or the way it's built
could comment on this.
Adding debian-live@ for now, but might be debian-cd@ territory…
Very wild guess: Could cryptsetup-initramfs be missing from live-setup?
https://salsa.debian.org/images-team/live-setup.git
Cheers,
--
Cyril Brulebois (kibi@debian.org) <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant
Attachment:
signature.asc
Description: PGP signature