Bug#876103: marked as done (systemd-nspawn: --read-only is broken)

[Debian Bug Tracking System]

Your message dated Sat, 24 Mar 2018 21:47:51 +0100
with message-id <5a21ca04-4b83-62a0-86d0-eb3c7b55ec0d at debian.org>
and subject line Re: Bug#876103: systemd-nspawn: --read-only is broken
has caused the Debian Bug report #876103,
regarding systemd-nspawn: --read-only is broken
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.)


-- 
876103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876103
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Lauri Tirkkonen <lauri at tuxera.com>
Subject: systemd-nspawn: --read-only is broken
Date: Mon, 18 Sep 2017 16:43:27 +0300
Size: 4196
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20180324/95a41e74/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Michael Biebl <biebl at debian.org>
Subject: Re: Bug#876103: systemd-nspawn: --read-only is broken
Date: Sat, 24 Mar 2018 21:47:51 +0100
Size: 5981
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20180324/95a41e74/attachment-0001.mht>