Bug#755160: marked as done (Segfault when starting new system instance in a systemd-nspawn environment)

Fri Jan 29 14:00:55 GMT 2016

Your message dated Fri, 29 Jan 2016 11:22:58 +0100
with message-id <20160129102258.GB6198 at msg.df7cb.de>
and subject line Re: Bug#755160: Segfault when starting new system instance in a systemd-nspawn environment
has caused the Debian Bug report #755160,
regarding Segfault when starting new system instance in a systemd-nspawn environment
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.)

-- 
755160: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755160
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Christoph Berg <myon at debian.org>
Subject: Segfault when starting new system instance in a systemd-nspawn environment
Date: Fri, 18 Jul 2014 14:56:46 +0300
Size: 8021
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20160129/1efdd0c2/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Christoph Berg <myon at debian.org>
Subject: Re: Bug#755160: Segfault when starting new system instance in a systemd-nspawn environment
Date: Fri, 29 Jan 2016 11:22:58 +0100
Size: 3749
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20160129/1efdd0c2/attachment-0001.mht>