Bug#965062: marked as done (systemd: Cannot resolve user name systemd-network: No such process)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jul 2020 22:14:10 +0200
with message-id <d295415a-8c1d-2ad4-86cb-3f5ae15e1615 at debian.org>
and subject line Re: Bug#965062: systemd: Cannot resolve user name systemd-network: No such process
has caused the Debian Bug report #965062,
regarding systemd: Cannot resolve user name systemd-network: No such process
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.)


-- 
965062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965062
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Marc Lehmann <debian-reportbug at plan9.de>
Subject: systemd: Cannot resolve user name systemd-network: No such process
Date: Wed, 15 Jul 2020 14:00:13 +0200
Size: 3077
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20200726/e7917e88/attachment-0002.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Michael Biebl <biebl at debian.org>
Subject: Re: Bug#965062: systemd: Cannot resolve user name systemd-network: No such process
Date: Sun, 26 Jul 2020 22:14:10 +0200
Size: 8057
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20200726/e7917e88/attachment-0003.mht>