Bug#1019331: systemd-resolved: Update breaks DNS resolution, should be `Recommends:`.

[Luca Boccassi]

On Wed, 7 Sep 2022 16:18:57 +0200 Michael Biebl <biebl at debian.org>
wrote:
> 
> Hi Dirk
> 
> Am 07.09.22 um 15:28 schrieb Dirk Lehmann:
> > Package: systemd
> > Version: 251.4-3
> > Severity: grave
> > Tags: upstream
> > Justification: renders package unusable
> > 
> > Dear Maintainer,
> > 
> > On my system I am using `systemd-resolved` for DNS name resolution.
> > After updating to the current version of the package `systemd` my
DNS
> > name resolution goes down.
> > 
> > After that update an `apt-get install systemd-resolved` is not
> > possible anymore, due to missing DNS resolution.
> > 
> > I workaround it, by temporarily adding the DNS resolution of the
> > Debian Package Mirror manually to `/etc/hosts`, which is depending
on
> > the configuration in `/etc/apt/sources.list`.  After that it is
> > possible to `apt-get install systemd-resolved` and the changes in
> > `/etc/hosts` can be reverted.
> > 
> > For Systemd Maintainers I would recommend to add the package
> > `systemd-resolved` to `Recommends:` instead of `Suggests:`.  Then
it
> > should be installed automatically on a Debian system with a default
> > configured `apt` - as it was in the past.
> 
> We actually discussed this this very issue.
> Problem is: the new systemd-resolved package does enable resolved by 
> default (and this is a trait we wanted from the new, split-off 
> systemd-resolved package).
> So, by making systemd-resolved a Recommends we would basically enable
> systemd-resolved for everyone.
> This would be a much more intrusive change that would require further
> discussion and is not something we wanted to pursue at this point.
> 
> So instead, we opted to show a NEWS entry, which tells the (few)
users 
> that had systemd-resolved enabled manually, to explicitly install the
> systemd-resolved package [1]. We are also aware, that apt-listchanges
is 
> currently buggy [2] and doesn't always shows NEWS entries, so we
worked 
> around that [3].
> 
> We will also add a corresponding entry to the release notes of
bookworm [4].
> 
> We are aware that for users of systemd-resolved the upgrade
experience 
> is not perfect but given the current constraints, it's imho the best
we 
> can do. So I'm closing the bug report.
> If you have suggestions how the upgrade experience can be improved
with 
> the given constraints, please let us know.
> 
> Regards,
> Michael
> 
> 
> [1] 
>
https://salsa.debian.org/systemd-team/systemd/-/commit/5db8ba3017a000d4c338d88504fa48adcc6eaa63
> [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977422

This reply somehow didn't make it to the mailing list, so I missed it
before sending mine:

https://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/2022-September/thread.html

-- 
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/20220907/fef4e748/attachment.sig>