Bug#939904: Temporary network disruption during upgrade

[Raphaël Halimi]

Le 18/08/2022 à 16:20, Luca Boccassi a écrit :
> No, it is not, because no integration nor support was provided before.
> It was an inhert and disabled service and binary.
> The NEWS file covers the change adequately for custom setups. Custom
> setups are always at risk of breakage.

I agree that it was not enabled by default, but it was shipped by 
systemd, with a stable interface, and as such, it was available for the 
admin to use it if he/she wished. Breaking DNS resolution after an 
upgrade is not a serious bug in your opinion ?

> That would make it de-facto the default resolver on Debian, and we
> really don't want that at this stage. There appears to be some bug in
> apt-listchanges when showing changelogs is enabled making it skip NEWS
> files if a changelog for the same version was already displayed, and
> there's not much we can do about it, it's a problem to be solved by
> apt-listchanges.

Wrong, I always receive e-mails with news as well as changelogs during 
upgrades, with the more recent examples being on July 13, 22 and 25. I 
don't know why it didn't work this time, but I can hardly believe that 
it's apt-listchanges' fault.

> Absolutely not, the alternatives system is a gigantic mess that should
> have never existed in the first place. If you want to use openresolv,
> install openresolv and remove resolved.

I think you don't understand my position: I don't care about resolvconf 
or openresolv, I just want to use systemd-resolved (not the systemd 
resolvconf interface, but the systemd-resolved service itself!) and 
avoid breakage during upgrades for all users.

Look, I'm just trying to help here. You made a change, it has serious 
consequences for systemd-resolved users, and I hinted them to you, 
that's all. I think this is a bad change, but that's another matter. 
Being obtuse and condescending won't help.

Regards,

-- 
Raphaël Halimi