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 use
On Fri, 28 Jun 2024 22:22:46 +0300 hammered hammered
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 deci
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
Control: tags -1 wontfix
Control: close -1
On Fri, 28 Jun 2024 20:27:55 +0300 hammered hammered
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 unsta
Package: systemd-cryptsetup
Version: 256.1-2
I had setup dm-crypt/luks on my debian sid installation and it worked
perfectly for more than 5 years now.
I had configured two encrypted items. One for the swap and one for the home
dir of my user. The last one is dependent on an encrypted file contai
5 matches
Mail list logo
