Bug#986651: systemd: stop depending on systemd-timesyncd

[Michael Biebl]

Am 10.04.2021 um 17:11 schrieb Helmut Grohne:
> On Sat, Apr 10, 2021 at 12:17:24PM +0200, Michael Biebl wrote:

>> If we bump the prio of systemd-timesyncd, those minimal containers will now
>> suddenly get systemd-timesyncd by default (which in turn pulls systemd). So
>> this would be a regression. You'd have to be careful to omit
>> systemd-timesyncd when building the container image.
> 
> I don't think minimal containers install Priority: important packages,
> not even Priority: required ones.  At least that's not how I approach
> it. I usually start with just Essential: yes and add what is needed.
> Possibly though, this workflow is not the one other people use. How do
> we find out? 

Good question.

For instance, e2fsprogs is not Essential: yes, but
> Priority: required precisely for the container use case.
> 
> In any case, there is no regression as systemd presently is Priority:
> important and systemd depends on systemd-timesyncd. If they'd install
> systemd-timesyncd due to Priority: important, they'd do it today
> already.

That's a valid remark, thanks.

My main objective is, that I want to have an NTP client installed in all 
but unusual/special installations.
Demoting the dependency to Recommends would not work afaiu as systemd is 
installed during the initial debootstrap phase where, I was told, 
Recommends are not considered. That's the motivation for the Depends.


If we can achieve the same with Recommends + Prio: important, then I'm 
ok with this change.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20210410/c0e89df4/attachment.sig>