Bug#788913: marked as done (boot failure with separate /usr and no initramfs due to libseccomp being in /usr)

[Debian Bug Tracking System]

Your message dated Wed, 17 Jun 2015 08:16:58 +0200
with message-id <20150617061658.GA3426 at piware.de>
and subject line Re: Bug#788913: systemd prevents to boot with a kernel panic. Boot in systemv mode is ok
has caused the Debian Bug report #788913,
regarding boot failure with separate /usr and no initramfs due to libseccomp being in /usr
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.)


-- 
788913: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788913
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Eric Valette <eric2.valette at orange.com>
Subject: systemd prevents to boot with a kernel panic. Boot in systemv mode is ok
Date: Tue, 16 Jun 2015 10:06:07 +0200
Size: 3889
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20150617/2b860731/attachment-0004.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Martin Pitt <mpitt at debian.org>
Subject: Re: Bug#788913: systemd prevents to boot with a kernel panic. Boot in systemv mode is ok
Date: Wed, 17 Jun 2015 08:16:58 +0200
Size: 2757
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20150617/2b860731/attachment-0005.mht>