Bug#939904: Temporary network disruption during upgrade

Luca Boccassi bluca at debian.org
Tue Aug 16 23:36:12 BST 2022


On Tue, 2022-08-16 at 23:17 +0200, Raphaël Halimi wrote:
> Le 16/08/2022 à 22:59, Luca Boccassi a écrit :
> > You want resolved? Install the resolved package. Don't want resolved?
> > Don't install the package.
> 
> Personally I see this as a regression, since resolved used to be part of 
> systemd and thus readily available without installing additional packages.

No support was provided before for resolved, it was completely inhert,
hence it is not a regression. It is a change in behaviour, and thus
noted in the NEWS file as expected.

> > 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.
> 
> Yes, but this goal could be achieved by letting resolved in the main 
> systemd package, and splitting only systemd-resolvconf in its own package.
> 

Having a single-file-package that is confusing and harder to find is
not something we want to do, unless there are extremely compelling
reasons for it. Supporting resolvconf is not one.

-- 
Kind regards,
Luca Boccassi



More information about the Pkg-systemd-maintainers mailing list