Bug#945208: marked as done ("No such file or directory" when attempting to decrypt LUKS during init)

[Debian Bug Tracking System]

Your message dated Thu, 21 Nov 2019 17:05:10 +0100
with message-id <2d9658b2-bb85-76ee-94c1-e34c94035114 at debian.org>
and subject line Re: Bug#945208: "No such file or directory" when attempting to decrypt LUKS during init
has caused the Debian Bug report #945208,
regarding "No such file or directory" when attempting to decrypt LUKS during init
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.)


-- 
945208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945208
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Amit Agnani <amitagnani at protonmail.com>
Subject: "No such file or directory" when attempting to decrypt LUKS during init
Date: Thu, 21 Nov 2019 08:35:10 +0000
Size: 119237
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20191121/60596950/attachment-0002.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Michael Biebl <biebl at debian.org>
Subject: Re: Bug#945208: "No such file or directory" when attempting to decrypt LUKS during init
Date: Thu, 21 Nov 2019 17:05:10 +0100
Size: 7633
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20191121/60596950/attachment-0003.mht>