[pkg-cryptsetup-devel] Bug#1140141: marked as done (cryptsetup: Failure to boot fresh install via cryptroot-unlock with an encrypted home partition)

[Debian Bug Tracking System]

Your message dated Tue, 16 Jun 2026 16:07:46 +0200
with message-id <ajFYstpxGt3GWVFq at debian.org>
and subject line Re: Bug#1140141: cryptsetup: Failure to boot fresh install via cryptroot-unlock with an encrypted home partition
has caused the Debian Bug report #1140141,
regarding cryptsetup: Failure to boot fresh install via cryptroot-unlock with an encrypted home partition
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 at bugs.debian.org
immediately.)


-- 
1140141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1140141
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Alex <alex at alex.com>
Subject: cryptsetup: Failure to boot fresh install via cryptroot-unlock with an encrypted home partition
Date: Tue, 16 Jun 2026 08:02:47 -0500
Size: 22842
URL: <http://alioth-lists.debian.net/pipermail/pkg-cryptsetup-devel/attachments/20260616/183607a7/attachment.eml>
-------------- next part --------------
An embedded message was scrubbed...
From: Guilhem Moulin <guilhem at debian.org>
Subject: Re: Bug#1140141: cryptsetup: Failure to boot fresh install via cryptroot-unlock with an encrypted home partition
Date: Tue, 16 Jun 2026 16:07:46 +0200
Size: 5571
URL: <http://alioth-lists.debian.net/pipermail/pkg-cryptsetup-devel/attachments/20260616/183607a7/attachment-0001.eml>