Bug#816767: marked as done (systemd-coredump: Failed to connect to coredump service: No such file or directory)

[Debian Bug Tracking System]

Your message dated Mon, 21 Mar 2016 13:23:10 +0000
with message-id <E1ahzna-0006sc-J3 at franck.debian.org>
and subject line Bug#816767: fixed in systemd 229-3
has caused the Debian Bug report #816767,
regarding systemd-coredump: Failed to connect to coredump service: No such file or directory
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.)


-- 
816767: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816767
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Jakub Wilk <jwilk at debian.org>
Subject: systemd-coredump: Failed to connect to coredump service: No such file or directory
Date: Sat, 5 Mar 2016 01:10:34 +0100
Size: 3482
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20160321/970497e7/attachment-0004.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Martin Pitt <mpitt at debian.org>
Subject: Bug#816767: fixed in systemd 229-3
Date: Mon, 21 Mar 2016 13:23:10 +0000
Size: 8013
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20160321/970497e7/attachment-0005.mht>