Bug#1091864: tech-ctte: Avahi and systemd-resolved cannot a run mDNS responder at the same time

Michael Biebl <[email protected]> Thu, 16 Jan 2025 13:19:42 +0100

Newsgroups	gmane.linux.debian.devel.ctte
Message-ID	<9a824cd4-dfe0-49d7-a7e4-9770b8525d9d__16142.4004518025$1737030993$gmane$org@debian.org>

Hi Helmut,

thanks for the summary.

I also want to mention [0] here.


Am 16.01.25 um 09:32 schrieb Helmut Grohne:
> This gives rise possible CTTE actions.
> 
> (O) The CTTE overrules the systemd maintainers and requires mDNS to be
>      default-disabled in systemd-resolved for the trixie release.
>      (Requires a 3:1 majority overruling a developer.)
> (D) The CTTE decleines to overrule the systemd maintainers regarding the
>      default of mDNS in systemd-resolved and recommends that avahi-daemon
>      disables mDNS in systemd-resolved upon its installation.

Do you consider [1] an RC bug, i.e. something that should/must be 
addressed one way or another for trixie?
I personally do, and if you agree, this would mean option (D) is not a 
simple recommendation but you have to say that you would override my 
wish as maintainer of avahi-daemon to not ship such a config snippet. 
Afaics, this would then also mean a 3:1 majority.

Otherwise option (D) would mean I'll most likely close [1] as wontfix, 
i.e. would leave this issue unresolved.
I haven't seen any convincing arguments so far why the mDNS 
functionality in resolved must be turned on by default.

Regards,
Michael

[0] 
https://fedoraproject.org/wiki/Changes/systemd-resolved#Local_multicast_DNS
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077937

OpenPGP_signature.asc (application/pgp-signature, 840 B)