Bug#827438: marked as done (systemd: boot fails with rootfs on luks after systemd upgrade)

Sun May 27 20:21:05 BST 2018

Your message dated Sun, 27 May 2018 21:16:32 +0200
with message-id <87ab5bab-a035-32b4-d74c-f7f58d9e4fea at debian.org>
and subject line Re: systemd: boot fails with rootfs on luks after systemd upgrade
has caused the Debian Bug report #827438,
regarding systemd: boot fails with rootfs on luks after systemd upgrade
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.)

-- 
827438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827438
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Sander van Grieken <sander at outrightsolutions.nl>
Subject: systemd: boot fails with rootfs on luks after systemd upgrade
Date: Thu, 16 Jun 2016 08:39:53 +0200
Size: 573342
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20180527/f3951cfe/attachment-0002.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Michael Biebl <biebl at debian.org>
Subject: Re: systemd: boot fails with rootfs on luks after systemd upgrade
Date: Sun, 27 May 2018 21:16:32 +0200
Size: 8484
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20180527/f3951cfe/attachment-0003.mht>