Your message dated Sun, 1 Feb 2026 15:34:33 +0100
with message-id <[email protected]>
and subject line Re: Deprecate .local detection in favor of NEWS.Debian and
disabling service?
has caused the Debian Bug report #785325,
regarding Deprecate .local detection in favor of NEWS.Debian and disabling
service?
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.)
--
785325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785325
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: avahi-daemon
Version: 0.6.31-5
Severity: normal
File: /etc/network/if-up.d/avahi-daemon
Currently, avahi-daemon ships a network hook
/etc/network/if-up.d/avahi-daemon , which detects if the local network
uses .local for something other than mDNS, and if so, disables Avahi.
This script can take a non-trivial amount of time to run, especially on
networks with *interesting* DNS (e.g. if the probe for .local ends up
waiting for a timeout); on my system, I've observed it taking more time
than the rest of the network bringup process combined.
I don't think it makes sense for *every* system to pay the cost of this
detection on every network bringup. People have had several years to
fix their networks, and anyone still on such a network probably won't be
able to change that anytime soon. Could we deprecate this hook, in
favor of a note in NEWS.Debian explaining how to disable the avahi
service if necessary (e.g. with update-rc.d or systemctl)? (Or, for
people who roam between networks where they want to use avahi and broken
networks using .local as a unicast DNS suffix, ship the script in
/usr/share/doc/avahi-daemon as an example that NEWS.Debian could
reference?)
- Josh Triplett
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.0.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages avahi-daemon depends on:
ii adduser 3.113+nmu3
ii bind9-host [host] 1:9.9.5.dfsg-9
ii dbus 1.8.16-2
ii init-system-helpers 1.23
ii libavahi-common3 0.6.31-5
ii libavahi-core7 0.6.31-5
ii libc6 2.19-18
ii libcap2 1:2.24-8
ii libdaemon0 0.14-6
ii libdbus-1-3 1.8.16-2
ii libexpat1 2.1.0-6+b3
ii lsb-base 4.1+Debian13+nmu1
Versions of packages avahi-daemon recommends:
pn libnss-mdns <none>
Versions of packages avahi-daemon suggests:
pn avahi-autoipd <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.8-4
This was fixed in
https://salsa.debian.org/utopia-team/avahi/-/commit/ac54649321cd5917d9611f4ff6dd848021ac357b
but this particular bug report was not mentioned in the changelog.
So closing it manually now.
On Thu, 14 May 2015 10:50:14 -0700 Josh Triplett <[email protected]>
wrote:
Package: avahi-daemon
Version: 0.6.31-5
Severity: normal
File: /etc/network/if-up.d/avahi-daemon
Currently, avahi-daemon ships a network hook
/etc/network/if-up.d/avahi-daemon , which detects if the local network
uses .local for something other than mDNS, and if so, disables Avahi.
This script can take a non-trivial amount of time to run, especially on
networks with *interesting* DNS (e.g. if the probe for .local ends up
waiting for a timeout); on my system, I've observed it taking more time
than the rest of the network bringup process combined.
I don't think it makes sense for *every* system to pay the cost of this
detection on every network bringup. People have had several years to
fix their networks, and anyone still on such a network probably won't be
able to change that anytime soon. Could we deprecate this hook, in
favor of a note in NEWS.Debian explaining how to disable the avahi
service if necessary (e.g. with update-rc.d or systemctl)? (Or, for
people who roam between networks where they want to use avahi and broken
networks using .local as a unicast DNS suffix, ship the script in
/usr/share/doc/avahi-daemon as an example that NEWS.Debian could
reference?)
- Josh Triplett
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.0.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages avahi-daemon depends on:
ii adduser 3.113+nmu3
ii bind9-host [host] 1:9.9.5.dfsg-9
ii dbus 1.8.16-2
ii init-system-helpers 1.23
ii libavahi-common3 0.6.31-5
ii libavahi-core7 0.6.31-5
ii libc6 2.19-18
ii libcap2 1:2.24-8
ii libdaemon0 0.14-6
ii libdbus-1-3 1.8.16-2
ii libexpat1 2.1.0-6+b3
ii lsb-base 4.1+Debian13+nmu1
Versions of packages avahi-daemon recommends:
pn libnss-mdns <none>
Versions of packages avahi-daemon suggests:
pn avahi-autoipd <none>
-- no debconf information
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
