>>>>> "Michael" == Michael Biebl <bi...@debian.org> writes:
Michael> Hi Helmut, thanks for the summary.
Michael> I also want to mention [0] here.
Michael> 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.
Michael> Do you consider [1] an RC bug, i.e. something that
Michael> should/must be addressed one way or another for trixie? I
Michael> personally do, and if you agree, this would mean option (D)
Michael> is not a simple recommendation but you have to say that you
Michael> would override my wish as maintainer of avahi-daemon to not
Michael> ship such a config snippet. Afaics, this would then also
Michael> mean a 3:1 majority.
It also seems like the TC has the option of providing policy here, for
example policy on what the default MDNS implementation is in Debian or
policy on how services can interact that gives guidance on the
interaction between packages like avahi-daemon and systemd-resolved.
Such policy would not require a 3:1 supermajority, and in general, we'd
expect maintainers to follow policy, especially TC-level policy, or to
accept patches to do so.
I think overriding maintainers is a very heavy hammer in a situation
when there is an interaction between two packages.
(For that matter, the TC could rule under the grounds that there is
overlapping responsibility between the two maintainers, also not
requiring a 3:1 super majority.)
For what it's worth, as someone who is not involved in the TC, I
definitely think our users would be best solved by resolving things so
that a default desktop installation of Debian has avahi-daemon as a
working mdns resolver without systemd-resolved getting in the way.
signature.asc
Description: PGP signature
