Bug#1091864: TC decision on avahi vs systemd-resolved - #1091864

Helmut Grohne <[email protected]> Tue, 25 Feb 2025 18:54:46 +0100
Newsgroups gmane.linux.debian.devel.ctte
Message-ID <20250225175446.GA1723595__34572.6533139654$1740520489$gmane$org@subdivi.de>
The Debian Technical Committee was asked to rule about a dispute between
the avahi and systemd maintainers in #1091864.

The following resolution was passed. The decision was reached
unanimously meeting the required 3:1 majority requirement for overruling
a maintainer.

=== Resolution ===

The CTTE reaffirms that avahi-daemon is the default mDNS implementation
in Debian trixie. Therefore systemd-resolved should disable the mDNS
functionality in its default installation in Debian trixie.

=== End Resolution ===

=== Rationale ===

It was considered to allow both implementations to coexist. However,
binding a UDP port is required for operation and that tends to not work.
As a result, consensus between the relevant package maintainers was
reached that when both implementations were installed that avahi should
be in charge. Disagreement existed about whether systemd-resolved should
support mDNS in the absence of avahi-daemon and how mDNS would be
disabled in systemd-resolved when avahi-daemon would be installed. It
was also noted that systemd-resolved requires mDNS to additionally be
enabled per interface, which does not yet happen by default. Given that
historically, avahi was the only implementation of mDNS and that other
distributions such as Fedora also disable mDNS in resolved by default,
the members of the Debian Technical Committee agreed that for the time
being and for trixie, we should continue using avahi as the default
implementation and it is typically part of a desktop installation due to
reverse dependencies. We also recognize that the code base of avahi is
aging and that one its primary developers is now developing systemd. As
a result, the decision is limited to the trixie release to leave room
for future changes.

=== End Rationale ===

Please refer to https://bugs.debian.org/1091864 for the complete
discussion.

Helmut for the Technical Committee
signature.asc (application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEETMLS2QqNFlTb+HOqLRqqzyREREIFAme+A+IACgkQLRqqzyRE
REKx9g/+JDEeLdPzL8iIkNZAMRM4FvuGPvY5dajltmOjEs52DwmP19nR5SM2YHtW
X58ASQl8JTBdA2yPVf48W5aNdsotkSBImGAk+RVV51+qsCSGpSROk9qPMreWWD/T
hvBU5hlcZsN2GEbTJSWTF0Sr2SlfZ797iYUtYlezFvExubbKeYDtQFb2XaFv+1Jc
KYEMr8Ac92ahSmKrnfI4+3Ps1Tvscdohzkao+0HNRI7scOEeqdhpXSrQfwPTrTM0
crLBoMCS+rY66rKuCdNeFMR2UhJsbmfy0O2Qr+QYTaGVi5XItev9CNwJheyGZAB3
UwuIU3RQQFk5cn2zt5QYe8fQj94pN7jkDqYp3o1YsiwBBfjTWNcclY0aCcWhtGSg
2Uhf8/rhpEt0Zk5h3Ba1J/Gbj5s5iyogB4vhDb4yz94mli8X6yNKxL0tKAvOVK9h
HmmZUjfW3OVip79ygI9pkFi5vNvIfIMSFXKoITnhuXCRcNF8H7Ohtd6iKZ0cSP+w
g67PaTfS/UVDlsXYXi9bCPe+Nneo8SZ9m+YEUBdGncsyfor9//WinIWiVSIKx0Nq
Yza5p9zaF0mj56TAubLcdq/wj2VUPHC6dIPFRPNsJOCN+hRxgZ25dQg8WBcc2gqx
tt1/Rzod/rnUge4TPM3XOU3Nj8kukIBtluqJkSbrxgKiuggb8Vo=
=jeI4
-----END PGP SIGNATURE-----