Bug#166987: marked as done (debconf: Can't answer deb_get questions)

[Debian Bug Tracking System]

Your message dated Fri, 24 Nov 2017 11:48:50 +0000
with message-id <E1eICTS-0003w8-0Q at fasolo.debian.org>
and subject line Bug#166987: fixed in libterm-readline-gnu-perl 1.35-2
has caused the Debian Bug report #166987,
regarding debconf: Can't answer deb_get questions
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.)


-- 
166987: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=166987
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: gsstark at mit.edu
Subject: debconf: Can't answer deb_get questions
Date: Tue, 29 Oct 2002 17:46:11 -0500
Size: 1977
URL: <http://lists.alioth.debian.org/pipermail/pkg-perl-maintainers/attachments/20171124/0a98aae0/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Florian Schlichting <fsfs at debian.org>
Subject: Bug#166987: fixed in libterm-readline-gnu-perl 1.35-2
Date: Fri, 24 Nov 2017 11:48:50 +0000
Size: 6277
URL: <http://lists.alioth.debian.org/pipermail/pkg-perl-maintainers/attachments/20171124/0a98aae0/attachment-0001.mht>