Your message dated Sun, 22 Oct 2017 13:19:11 +0200
with message-id
<1508671151.815349.1146906880.773a8...@webmail.messagingengine.com>
and subject line Closing bugs in old-old-stable bind9 versions
has caused the Debian Bug report #260759,
regarding bind: named(8) and named.conf(5) reference wrong filename.
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 [email protected]
immediately.)
--
260759: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=260759
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bind
Version: 1:8.4.4-1
Severity: normal
named(8) and named.conf(5) claim that the default bind configuration
file is /etc/namedb/named.conf, but it is actually
/etc/bind/named.conf on Debian systems.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.5
Locale: LANG=ja_JP.eucJP, LC_CTYPE=ja_JP.eucJP (ignored: LC_ALL set to
ja_JP.eucJP)
Versions of packages bind depends on:
ii libc6 2.3.2.ds1-13 GNU C Library: Shared libraries an
ii netbase 4.17 Basic TCP/IP networking system
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1:9.10.3.dfsg.P4-12.3
Hi,
the bind9 bug list grew too much and the Debian BIND team cannot
simply test all the reported bugs against versions not in stable, so
this is mass bug close, as either the version is no longer relevant
(because of old-old-stable 9.8.x or old-stable 9.9.5 or even older
version of bind9) or the bug was already fixed.
However, if you can reproduce the bug with a current version in stable,
please use Debian BTS 'found <bug> <version_you_reproduced_the_issue>'
command to retag the bug and reopen it.
Cheers,
Ondrej
signature.asc
Description: PGP signature
--- End Message ---
