Bug#801563: marked as done (cryptsetup: if I do not enter unlocking password during initialization at a time, systemd can not boot)

Sat Oct 24 10:00:07 BST 2015

Your message dated Sat, 24 Oct 2015 11:57:17 +0300
with message-id <562b47f1.e9b5700a.cdab5.14f4 at mx.google.com>
and subject line I will create another bug report, because I was wrong in diagnosis of this problem
has caused the Debian Bug report #801563,
regarding cryptsetup: if I do not enter unlocking password during initialization at a time, systemd can not boot
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.)

-- 
801563: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801563
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Jayson Willson <jaysonwillson245 at gmail.com>
Subject: cryptsetup: if I do not enter unlocking password during initialization at a time, systemd can not boot
Date: Mon, 12 Oct 2015 08:42:48 +0300
Size: 9942
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20151024/711e00f3/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Jayson Willson <jaysonwillson245 at gmail.com>
Subject: I will create another bug report, because I was wrong in diagnosis of this problem
Date: Sat, 24 Oct 2015 11:57:17 +0300
Size: 2728
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20151024/711e00f3/attachment-0001.mht>