[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1108823: marked as done (trixie: mention issue with cryptsetup support having been moved to systemd-cryptsetup)

Your message dated Fri, 18 Jul 2025 16:16:38 +0200
with message-id <aHpXRj7fP6fO8FmB@per.namespace.at>
and subject line Re: Bug#1108823: trixie: mention issue with cryptsetup support having been moved to systemd-cryptsetup
has caused the Debian Bug report #1108823,
regarding trixie: mention issue with cryptsetup support having been moved to systemd-cryptsetup
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1108823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1108823
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release-notes
Severity: normal
Tags: patch

Hi!

The support for opening and mounting encrypted storage devices (managed by
cryptsetup`) in systemd has been moved into a separate package,
systemd-cryptsetup`. If a system being upgraded to Trixie has installation of
recommended packages disabled (like does mine) or the user for some reason has
initiated the upgrade process with a call like

  apt dist-uprade --no-install-recommends

and the user has any encrypted filesystem listed in /etc/fstab or in a custom
systemd unit file of type "mount", the system may not boot properly - see,
for example, my case [1], and also [2] and [3].

I hence recommend to prominently mention this issue in the Trixie release
notes.

I've tried to come up with the text for this (patch attached) but feel free to
make arbitrary changes to it or use it merely as a reference.

 1. https://lists.debian.org/debian-devel/2025/07/msg00012.html
 2. https://bugs.debian.org/1079644
 3. https://bugs.debian.org/1076208


diff --git a/source/issues.rst b/source/issues.rst
index fea92a02..6698bb1c 100644
--- a/source/issues.rst
+++ b/source/issues.rst
@@ -41,6 +41,20 @@ possible, or retiring the hardware.
 `Cross-grading <https://wiki.debian.org/CrossGrading>`__ without a
 reinstall is a technically possible, but risky, alternative.
 
+.. _systemd-cryptsetup-support-moved-to-separate-package:
+
+Support in ``systemd`` for opening and mounting encrypted storage devices
+at boot has been moved into a separate package, ``systemd-cryptsetup``.
+The ``systemd`` package in Trixie recommends it, but on systems with
+the installation of recommended packages diabled it will not be automatically
+installed by the upgrade process, likely rendering the system unbootable.
+
+If you have installation of recommended packages disabled,
+and have any filesystem residing on an encrypted storage device
+listed in ``/etc/fstab`` (or being mounted by a custom ``systemd`` unit file),
+be sure to install the ``systemd-cryptsetup`` package
+before rebooting the system.
+
 .. _openssh-pam-environment-removed:
 
 openssh-server no longer reads ~/.pam_environment

--- End Message ---
--- Begin Message --- 
On Fri, Jul 11, 2025 at 06:08:31PM +0200, Guilhem Moulin wrote:
> [src:cryptsetup co-maintainer here, but not involved in src:systemd]
> 
> >.. _systemd-cryptsetup-support-moved-to-separate-package:
> 
> Thanks for the suggestion!  Makes sense to add this in the release notes
> indeed.

We ended up with the text in this commit:
https://salsa.debian.org/ddp-team/release-notes/-/commit/984f937b337d36d381eb989d8bbf7773d0f4f140

Best,
Chris

--- End Message ---
Reply to: