-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I've been looking in to this bug because I use this package myself too,
and because it is among the RC bugs blocking lenny.
As I wrote in my message to control@ [1], I merged this issue with
#481103 because they report the same issue only for a different version
of the package.
This issue is similar to #433510 reported against mailgraph [2], which
changed the maintainer scripts to only generate the /etc/default/
configuration file if it does not exist and to source it otherwise.
The following section in debian/postinst appears to be the culprit that
changes the /etc/default/bindgraph file, specifically lines 64-70:
[...]
31 DEFAULTS=/etc/default/bindgraph
[...]
40 db_get bindgraph/logfile || true
41 LOGFILE="$RET"
[...]
52 # Solve #293819
53 BIND_VER="`dpkg -l bind9 | awk '/^ii/ { print $3; }'`"
54 if [ -n $BIND_VER ] && dpkg --compare-versions "$BIND_VER"
ge '9.3' ; then
55 log_ver="bind93" ;
56 else
57 log_ver="bind92" ;
58 fi
59
60 if [ ! -f $DEFAULTS ]; then
61 echo "DNS_LOG=$LOGFILE" > $DEFAULTS
62 echo "LOG_FORMAT=${log_ver}" >> $DEFAULTS
63
64 elif [ -z "`grep $LOGFILE $DEFAULTS`" ]; then
65 # update log file location
66 mv $DEFAULTS $DEFAULTS.tmp
67 grep -v DNS_LOG $DEFAULTS.tmp > $DEFAULTS
68 echo "DNS_LOG=$LOGFILE" >> $DEFAULTS
69 rm -f $DEFAULTS.tmp
70 fi
71
72 if [ -n "$2" ]; then
73 # if we are upgrading, update config :-)
74 if [ -z "`grep LOG_FORMAT ${DEFAULTS}`" ]; then
75 echo "LOG_FORMAT=${log_ver}" >> $DEFAULTS
76 fi
77 fi
[...]
The Debconf config.dat contains the following for bindgraph/logfile:
Name: bindgraph/logfile
Template: bindgraph/logfile
Value: /var/log/bind9-query.log
Owners: bindgraph
If the value of DNS_LOG in /etc/default/bindgraph does not match the
debconf bindgraph/logfile value, the debconf value is set in
/etc/default/bindgraph.
This logic seems to have been introduced to fix #318458 if I look at the
changelog and bug in question:
bindgraph (0.2a-3) unstable; urgency=high
* Reconfigure now updates logfile location (Closes: 318458)
I'll have a look to see if the bindgrapg maintainer scripts can be
modified to resemble those of mailgraph to fix this issue and not to
regress the previous issues.
Regards,
Bas
References:
[1]: http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=7;bug=503713
[2]: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=433510
- --
GnuPG: 0x77A975AD
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkkQSh8ACgkQRWRRA3epda2hsgCfSK1EojO8L8mNI44DXg1y5e5S
JzIAn0Hk/aMh/n+clCzKTh+55qGeRbmk
=mXmx
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
