[OE-core] [PATCH 0/3] Upgrade systemd to 241

[Alex Kiernan]

On Fri, Mar 1, 2019 at 8:42 AM Chen Qi <Qi.Chen at windriver.com> wrote:
>
>
> The following changes since commit 4d275d97b6c572fe11668ac16d2c77c018340c7c:
>
>   perl: apply a native-only patch only to -native (2019-02-28 17:49:40 +0000)
>
> are available in the git repository at:
>
>   git://git.pokylinux.org/poky-contrib ChenQi/systemd-241
>   http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=ChenQi/systemd-241
>
> Chen Qi (3):
>   systemd: upgrade to 241
>   systemd-conf: add version info in recipe name
>   systemd-boot: upgrade to 241
>

This upgrade seems to cause problems with the on-disk timestamp for
systemd-timesyncd. Having started writing what goes on, it's actually
in the systemd NEWS for 240:

* DynamicUser=yes is dropped from systemd-networkd.service,
  systemd-resolved.service and systemd-timesyncd.service, which was
  enabled in v239 for systemd-networkd.service and systemd-resolved.service,
  and since v236 for systemd-timesyncd.service. The users and groups
  systemd-network, systemd-resolve and systemd-timesync are created
  by systemd-sysusers again. Distributors or system administrators
  may need to create these users and groups if they not exist (or need
  to re-enable DynamicUser= for those units) while upgrading systemd.
  Also, the clock file for systemd-timesyncd may need to move from
  /var/lib/private/systemd/timesync/clock to /var/lib/systemd/timesync/clock.

It's the last bit that's tripping things up. I'm not sure I can think
of a good way of expressing that fixup using tmpfiles. I can use a
ConditionNeedsUpdate=/var to catch it locally (I'm using OSTree, and
OSTree successfully triggers that), but I don't know how useful that
approach will be to others.

-- 
Alex Kiernan