Your message dated Thu, 06 Jan 2011 15:59:04 +0100
with message-id <[email protected]>
and subject line Not needed
has caused the Debian Bug report #609118,
regarding Please add Breaks: resolvconf << 1.48
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.)
--
609118: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=609118
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bind9
Version: 1:9.7.2.dfsg.P3-1
Severity: normal
Since bind9 changed from using /var/run/bind/ to /var/run/named/ it fails
to work properly in some circumstances with resolvconf << 1.48 which,
under those circumstances, still assumes the use of /var/run/bind/.
Upcoming resolvconf release 1.48 assumes the use of /var/run/named/.
Please add a "Breaks: resolvconf (<< 1.48)" and modify the "Suggests:
resolvconf"
to "Suggests: resolvconf (>= 1.48)".
Thanks,
--
Thomas Hood
Resolvconf maintainers <[email protected]>
--- End Message ---
--- Begin Message ---
I've realized that this is not needed. Although resolvconf << 1.48 uses
/var/run/bind/ it also creates that directory if it doesn't exist, so
nothing actually breaks.
As mentioned in #483098, resolvconf 1.48 and higher will continue to use
/var/run/bind/ so that existing installations don't break.
The Suggests: line also doesn't need to be changed.
--
Thomas
--- End Message ---
