Bug#1101532: systemd: unable to migrate to Testing because of removed packages

[Noah Meyerhans]

On Tue, Apr 01, 2025 at 09:35:02PM +0000, Luca Boccassi wrote:
> > > > Please let's not get ahead of ourselves.  I think Stefano was simply
> > > > pointing out something that had happned in the past, not any new DAM
> > > > involvement.
> > >
> > > Sorry I should have been clearer: when I said warning, I literally
> > > meant it, and I was not talking about Stefano. An hour after sending
> > > the previous message, and while I was already working to add the
> > > package back (proof:
> > > https://salsa.debian.org/bluca/systemd/-/commit/5067878f3a691fb7a1dd1df30ca9c78935c50479
> > > ), this loveliness popped up in my inbox:
> > >
> > > date: 1 Apr 2025, 21:46
> > > subject: DAM warning for continuing to ignore Technical Committee decisions
> >
> > Understood.  I'm still trying to work out how to process this, but me
> > reiterate my position that the removal of systemd-networkd from trixie
> > is the worst possible outcome of this discussion so far.
> 
> I don't think we need to rework networkd's integration, I just meant
> the use of resolved to manage resolv.conf.

I know, and I'm sure we can extract the DHCP lease's DNS info from
networkd over dbus and craft a resolv.conf... but it's still a bespoke
solution that exists nowhere else.  And in trixie we have enabled
libnss-resolve (we didn't in bookworm), which we'd lose with this
change.  So it's still not ideal.