[Debian-iot-maintainers] Bug#926317: marked as done (libyder.pc Requires.private systemd, but systemd not in debian/control)

[Debian Bug Tracking System]

Your message dated Sat, 06 Apr 2019 23:36:36 +0000
with message-id <E1hCurU-00009S-EG at fasolo.debian.org>
and subject line Bug#926317: fixed in yder 1.4.4-5
has caused the Debian Bug report #926317,
regarding libyder.pc Requires.private systemd, but systemd not in debian/control
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.)


-- 
926317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926317
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Harald Welte <laforge at gnumonks.org>
Subject: libyder.pc Requires.private systemd, but systemd not in debian/control
Date: Wed, 03 Apr 2019 12:02:22 +0200
Size: 3709
URL: <http://alioth-lists.debian.net/pipermail/debian-iot-maintainers/attachments/20190406/41136232/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Nicolas Mora <nicolas at babelouest.org>
Subject: Bug#926317: fixed in yder 1.4.4-5
Date: Sat, 06 Apr 2019 23:36:36 +0000
Size: 6038
URL: <http://alioth-lists.debian.net/pipermail/debian-iot-maintainers/attachments/20190406/41136232/attachment-0001.mht>