On Thu, Apr 4, 2019 at 11:23 AM Lennart Poettering <lenn...@poettering.net> wrote: > > On Do, 04.04.19 10:06, Mike Gilbert (flop...@gentoo.org) wrote: > > > I pushed this out to our unstable testers yesterday, and received a > > couple bug reports this morning. I have requested that they be > > forwarded upstream, but wanted to point them out in case that doesn't > > happen promptly. > > > > https://bugs.gentoo.org/682492 > > sys-apps/systemd-242_rc2 boot fails: sd-passwd takes no arguments > > Most likely fixed by > https://github.com/systemd/systemd/commit/65e5d6934ec85febb6eb64e18ce829ddc9dee497 > already. > > > https://bugs.gentoo.org/682488 > > sys-apps/systemd-242_rc2: systemd-timesyncd.service: Failed to set up > > special execution directory in /var/lib: Not a directory > > Smells like a belated result of us dropping DynamicUser=1 from > timesyncd. > > Right now, systemd will automatically migrate the state directory for > services that have DynamicUser=0 to a newer version that has > DynamicUser=1, but not back. We should probably add that too. > > Anyway, it was systemd v240 where we dropped the DynamicUser=1 thing > already, hence not precisely a v242 regression...
These users probably upgraded from v239 to v241 to v242-rc2 over the course of a few months. We never shipped v240. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel