pe 27.12.2024 klo 12.22 Michael Biebl (bi...@debian.org) kirjoitti: > > Am 27.12.24 um 10:42 schrieb Martin-Éric Racine: > > to 26.12.2024 klo 21.55 Michael Biebl (bi...@debian.org) kirjoitti: > >> > >> On Wed, 18 Dec 2024 17:00:40 +0200 =?UTF-8?Q?Martin=2D=C3=89ric_Racine?= > >> <martin-eric.rac...@iki.fi> wrote: > >> I've marked this as RC, as I'm convinced this needs to fixed/addressed > >> for trixie. If you disagree, feel free to argue this case with the > >> release team, which I've CCed now. > > > > That still doesn't qualify it as RC. > > It violates Debian policy by misusing Provides. > > As maintainer of avahi-autoipd I want to see this incorrect Provides > dropped.
You're misuing an RC bug just because you disagree with what the maintainer of another package did. > >> TBH, I'm not sure what you are trying to achieve with the Provides: > >> avahi-autoipd in dhcpcd-base. > >> > >> Answering that question might help with finding a proper solution. > > > > dhclient doesn't provide IPv4LL but has hooks to call avahi-autoipd as > > needed. Meanwhile dhcpcd provides IPv4LL out of the box, along the > > same fallback connectivity logic as avahi-autoipd. Having both > > installed is not only redundant, it concurrently tries to control the > > same interfaces. Basically, this is the same reason why we want to > > avoid 2 DHCP clients trying to control the same interface and assume > > that as long as one package Proivides dhcp-client, we've got a > > bootable host. > > A Provides: avahi-autoipd does not ensure that both packages can't be > installed at the same time. So it fails to achieve what you are trying > to do. I've been told before not to Conflicts against other packages providing similar features. I therefore avoided doing the same here and instead Provides along a logic similar to dhcp-client. Anyhow, if you're gonna misuse RC bugs, just because what I do doesn't fit your agenda, I very much expect that you to propose actual solutions. Dropping that Provides isn't one. Martin-Éric