Bug#980080: marked as done (Failed to read server status: Transport endpoint is not connected)

[Debian Bug Tracking System]

Your message dated Sun, 28 Mar 2021 04:33:09 +0200
with message-id <da196c53-e6d0-8af4-e0d3-ce2d822f4a4c at debian.org>
and subject line Re: Bug#980080: Failed to read server status: Transport endpoint is not connected
has caused the Debian Bug report #980080,
regarding Failed to read server status: Transport endpoint is not connected
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.)


-- 
980080: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980080
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Harald Dunkel <harald.dunkel at aixigo.com>
Subject: Failed to read server status: Transport endpoint is not connected
Date: Thu, 14 Jan 2021 08:32:28 +0100
Size: 2393
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20210328/9ed4fbdb/attachment.eml>
-------------- next part --------------
An embedded message was scrubbed...
From: Michael Biebl <biebl at debian.org>
Subject: Re: Bug#980080: Failed to read server status: Transport endpoint is not connected
Date: Sun, 28 Mar 2021 04:33:09 +0200
Size: 2722
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20210328/9ed4fbdb/attachment-0001.eml>