Bug#1074443: Unable to boot due to missing package from the split

[hammered hammered]

I think you have greatly underestimated the severity of the problem.

Do you understand that users who have enabled whole system encryption are
totally locked out of the system? And probably won't have a usable system
in the cmdline to begin manually decrypting/mounting stuff.

I was somewhat lucky because I had only my homedir encrypted.

Also, the fact that one is running unstable/testing doesn't mean that you
can show zero effort to ensure not breaking stuff. Especially when we're
talking about breaking the system itself and making it unable to boot after
an update and no warning.

You should show a minimum effort to not break stuff even in
unstable/testing.

Please reopen this issue. It is a serious one.


On Fri, 28 Jun 2024 19:09:53 +0100 Luca Boccassi <bluca at debian.org> wrote:
> Control: tags -1 wontfix
> Control: close -1
>
> On Fri, 28 Jun 2024 20:27:55 +0300 hammered hammered
> <hammered999 at gmail.com> wrote:
> > It is totally unacceptable to break a working systems like that.
>
> You are running "unstable" or "testing", not "stable", there's a reason
> they are called as such. Incompatible changes in unstable/testing are
> normal and expected, if you don't want to deal with them, just run
> stable.
>
> --
> Kind regards,
> Luca Boccassi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20240628/3217d4c2/attachment.htm>