Comment 9 for bug 2004092

> systemd-journald now uses GID 999

Ummm where is this coming from? Debian Policy states:

9.2.2. UID and GID classes
--------------------------
[...]

100-999:
   Dynamically allocated system users and groups. Packages which need
   a user or group, but can have this user or group allocated
   dynamically and differently on each system, should use "adduser
   --system" to create the group and/or user. "adduser" will check for
   the existence of the user or group, and if necessary choose an
   unused id based on the ranges specified in "adduser.conf".

I see no addgroup calls in the systemd maintainer scripts. And in a lunar container created before systemd 252 was uploaded, I see systemd-journald created as group 101. This appears to be happening via /usr/lib/sysusers.d/systemd-journal.conf.

I think it is a bug in systemd to be bypassing the process specified in Debian Policy.

> Rather than going through the painstaking task of updating systemd
> to use a *different* user, let's just update casper to use 1000,
> which is the first dynamically-allocated user account per Debian
> Policy[1].

This is the GID expected to be used for the first user created on the target system. It's not clear to me that changing the casper user to use this uid won't badly confuse the installer when it comes time to create the actual user account, or at least cause gid 1000 to be skipped.