Bug#733232: marked as done (systemd: Systemd fails to boot after fscking filesystem if plymouth not installed)

[Debian Bug Tracking System]

Your message dated Sat, 28 Jun 2014 02:49:23 +0200
with message-id <53AE1113.3010504 at debian.org>
and subject line systemd: Systemd fails to boot after fscking filesystem if plymouth not installed
has caused the Debian Bug report #733232,
regarding systemd: Systemd fails to boot after fscking filesystem if plymouth not installed
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.)


-- 
733232: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733232
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Philip Armstrong <phil at kantaka.co.uk>
Subject: systemd: Systemd fails to boot after fscking filesystem if plymouth not installed
Date: Fri, 27 Dec 2013 14:41:21 +0000
Size: 498697
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20140628/c3bb127d/attachment-0002.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Michael Biebl <biebl at debian.org>
Subject: systemd: Systemd fails to boot after fscking filesystem if plymouth not installed
Date: Sat, 28 Jun 2014 02:49:23 +0200
Size: 3279
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20140628/c3bb127d/attachment-0003.mht>