Bug#935948: marked as done (can't start containers with different names but same prefix (xxxxxxxxxxx-1 and xxxxxxxxxxx-2))

[Debian Bug Tracking System]

Your message dated Wed, 11 Mar 2020 19:57:16 +0100
with message-id <4b86f0cf-2e13-ea5c-1b60-70a6d92d7aa3 at debian.org>
and subject line Re: can't start containers with different names but same prefix (xxxxxxxxxxx-1 and xxxxxxxxxxx-2)
has caused the Debian Bug report #935948,
regarding can't start containers with different names but same prefix (xxxxxxxxxxx-1 and xxxxxxxxxxx-2)
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.)


-- 
935948: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935948
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: "Trent W. Buck" <trentbuck at gmail.com>
Subject: can't start containers with different names but same prefix (xxxxxxxxxxx-1 and xxxxxxxxxxx-2)
Date: Wed, 28 Aug 2019 21:11:22 +1000
Size: 7652
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20200311/035166a9/attachment-0002.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Michael Biebl <biebl at debian.org>
Subject: Re: can't start containers with different names but same prefix (xxxxxxxxxxx-1 and xxxxxxxxxxx-2)
Date: Wed, 11 Mar 2020 19:57:16 +0100
Size: 7151
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20200311/035166a9/attachment-0003.mht>