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 #213706,
regarding bind: apt-get install -y bind < /dev/null fails if /etc/named.conf
exists
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.)
--
213706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=213706
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bind
Version: 1:8.4.1.0-1.woody.0
Severity: normal
If /etc/named.conf exists, not created by me but just as an artifact
of having some previous version of bind installed, then background
updates such as from an automated installer fails. Interestingly
enough the bind9 package does not have this problem.
apt-get install --reinstall -y bind < /dev/null
...
Preparing to replace bind 1:8.4.1.0-1.woody.0 (using
.../bind_1%3a8.4.1.0-1.woody.0_i386.deb) ...
Unpacking replacement bind ...
Setting up bind (8.4.1.0-1.woody.0) ...
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 continuedpkg: error processing bind (--configure):
subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
bind
E: Sub-process /usr/bin/dpkg returned an error code (1)
This makes it difficult to _automatically_ keep systems up to date. I
would like to do updates completely without interaction.
I think if the postinst script were changed to the following it would
then work okay. But I did not try it. Instead I am trying to deduce
a way to go directly to bind9 without this intervening update to
bind8. But this is still something I think should be addressed
regardless.
- read yn
+ read yn || true
Thanks
Bob Proulx <[email protected]>
-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux misery.proulx.com 2.4.20-2-k7 #1 Fri Jun 6 00:25:53 EST 2003 i686
Locale: LANG=C, LC_CTYPE=C
Versions of packages bind depends on:
ii libc6 2.2.5-11.5 GNU C Library: Shared libraries an
ii netbase 4.07 Basic TCP/IP networking system
--- 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 ---
