Bug#939904: Temporary network disruption during upgrade

[Luca Boccassi]

On Sun, 14 Aug 2022 19:08:14 +0200 "Andrej Shadura"
<andrewsh at debian.org> wrote:
> Hi,
> 
> On Sun, 14 Aug 2022, at 19:04, Michael Biebl wrote:
> >> I agree that the decision should be revisited, but for a different
> >> reason. I see no reason why resolvconf cannot be used with
resolved; 
> >> OTOH the current split prevents that, which I find very
undesirable.
> >> 
> >> I was very surprised when I learnt today systemd-resolved has a 
> >> Conflicts against resolvconf, that was contrary to my
expectations, and 
> >> I suspect I’m not the only person concerned about this.
> >> 
> >
> > Given that the package takes over management of /etc/resolv.conf, I
> > don't think it makes sense to have resolvconf interfering here.
> >
> > tbh, I don't see the benefit/use case of installing resolvconf
along 
> > side systemd-resolved.
> 
> 
> But that's the point of the complaint, I'm afraid. Resolved doesn't
have to take it over, it's just one of its operation modes.

It's the mode we want to support and that provides the most value. We
remove unused binaries and config from the main package, while keeping
the new one as simple and straightforward as possible - no faffing
around with maintainer scripts managing persistent filesystem changes,
or weird optional toggles to figure out.
You want resolved? Install the resolved package. Don't want resolved?
Don't install the package.

We do no want to support combining resolved with resolvconf - and in
fact, the setup with conflicts+provides is exactly like other packages
like openresolv are set up.

-- 
Kind regards,
Luca Boccassi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20220816/cde6cfa9/attachment.sig>