Your message dated Sat, 5 Sep 2015 16:32:07 -0400
with message-id <[email protected]>
and subject line Re: Bug#95773: bind asks questions more than once
has caused the Debian Bug report #95773,
regarding bind asks questions more than once
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.)


-- 
95773: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=95773
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bind
Version: 8.2.2p7-1

See the transcript below.  I already said `return' to all of these
comments the last time I upgraded BIND; it shouldn't ask me again.

Ian.


Setting up bind (8.2.2p7-1) ...

You have an /etc/named.boot file.  This is a remnant from a BIND 4.x
version, or the Debian BIND package up through 8.1.2.  We are not
prepared to try and update this for you automatically.  You should
extract any relevant information, put it in /etc/bind/named.conf,
and then remove /etc/named.boot.  Note that named.conf uses different
syntax than named.boot!

Press <enter> to continue

You have an /etc/named.conf file.  This is a remnant from a previous
package version.  The new location for this configuration file is
/etc/bind/named.conf.  Please review your configuration, put
everything relevant in /etc/bind/named.conf, then remove
/etc/named.conf

Press <enter> to continue

You have a /var/named directory.  Previous Debian packages used this
directory to hold zone data files.  Please review the contents, move
any relevant configuration to /etc/bind as per the instructions in
/usr/share/doc/bind/README.Debian, and then remove the /var/named
directory.  This package uses /var/cache/bind as the working directory,
and by default expects master zone files to be put in /etc/bind.

Press <enter> to continue

Restarting named... new pid is 16071


--- End Message ---
--- Begin Message ---
Ian Jackson wrote:
> Bdale Garbee writes ("Re: Bug#95773: bind asks questions more than once"):
> > [email protected] (Ian Jackson) writes:
> > > See the transcript below.  I already said `return' to all of these
> > > comments the last time I upgraded BIND; it shouldn't ask me again.
> > 
> > So, is there some reason you haven't cleaned up the named.boot file and
> > friends?  Doing so will, as indicated, cause these interruptions to not 
> > occur
> > on the next upgrade.
> 
> I don't feel like it.  My current configuration is perfectly correct
> and I don't see any need to change it at the moment.
> 
> Pointing out that I'm not following the `Debian way' is fine.  Nagging
> is not; it's my system, and you should follow the longstanding
> tradition in Debian (previous history in the BIND packages
> notwithstanding) that packages try to respect the sysadmin's
> configuration decisions.

Hi, Ian:

As far as I can tell, these nag prompts no longer exist in the bind9
package, and in fact probably never have, so I'm closing this bug.

The only thing in bind9 that looks even vaguely similar to the original
bug report is this error exit from bind9's preinst:

http://sources.debian.net/src/bind9/1:9.9.5.dfsg-12/debian/bind9.preinst/#L6-L15

(These lines should obviously be deleted now, but I suspect it's
impossible to trip this error condition on modern systems.)

-- 
Robert Edmonds
[email protected]

--- End Message ---

Reply via email to