Bug#858986: marked as done (systemd-container: systemd-nspawn fails to spawn container from a read-only image)

Sat Apr 29 20:33:10 BST 2017

Your message dated Sat, 29 Apr 2017 21:30:31 +0200
with message-id <dcc63e8c-f6b9-c199-cca7-77d03be4c78d at debian.org>
and subject line Re: Bug#858986: systemd-container: systemd-nspawn fails to spawn container from a read-only image
has caused the Debian Bug report #858986,
regarding systemd-container: systemd-nspawn fails to spawn container from a read-only image
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.)

-- 
858986: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858986
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Felix Wiedemann <1wiedema at informatik.uni-hamburg.de>
Subject: systemd-container: systemd-nspawn fails to spawn container from a read-only image
Date: Wed, 29 Mar 2017 12:20:52 +0200
Size: 3793
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20170429/7974587b/attachment-0002.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Michael Biebl <biebl at debian.org>
Subject: Re: Bug#858986: systemd-container: systemd-nspawn fails to spawn container from a read-only image
Date: Sat, 29 Apr 2017 21:30:31 +0200
Size: 5740
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20170429/7974587b/attachment-0003.mht>