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

[hammered hammered]

You might have a point about recommends. But enabling recommends brings in
a whole lot of unnecessary cruft. I don't have stats of what percentage of
users disables them or not, so I won't argue on that point more.

However, at timepoint A a package provides some critical functionality that
the user depends on. After sometime, at timepoint B, the package is split
and loses some critical functionality expected by the user. This isn't
communicated well and it results in a broken boot.

If you (or others from the packaging team) think that `recommends` is
enough effort to avoid breaking the *system*, then fine. I won't comment
any further.

On Fri, 28 Jun 2024 20:49:41 +0100 Luca Boccassi <bluca at debian.org> wrote:
> On Fri, 28 Jun 2024 22:22:46 +0300 hammered hammered
> <hammered999 at gmail.com> wrote:
> > You should show a minimum effort to not break stuff even in
> > unstable/testing.
>
> You have intentionally disabled 'recommends', which are enabled by
> default, and which normally results in sd-cryptsetup being installed.
> That was your decision, so stop wasting time and blaming others for
> your choices.
>
> --
> Kind regards,
> Luca Boccassi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20240628/669ebd29/attachment.htm>