Hi,
upgrading from bullseye to bookworm, during the "apt upgrade" step, it
may happen that login updates login.defs and adds the NONEXISTENT and
PREVENT_NO_AUTH options to login.defs. However, it is not guaranteed
that passwd gets upgraded quickly afterwards. Old groupmod, from old
passwd, doesn't understand the new configuration options and logs
Jun 22 07:38:41 emptybullseye99 groupmod[6828]: unknown configuration item `NONEXISTENT'
Jun 22 07:38:41 emptybullseye99 groupmod[6828]: unknown configuration item `PREVENT_NO_AUTH'
Those messages also end up on the console, unfortunately without a
prefix indicating which program caused the message. It just says
"configuration error - unknown item NONEXISTENT". If groupmod didn't log to
syslog as well, I would still be searching.
This shows, for example, when openssh-client tries to rename its ssh
group to _ssh in postinst between the updates of login and passwd. I
have also seen this when upgrading udev from bullseye to bookworm as it
tries to create the new sgx group.
Functionality is not affected, the operation succeeds, but there is a
confusing error message on the console.
Maybe it would be a good idea to have a versioned dependency between
login and passwd, preventing the case of an old binary not fully
understanding a new configuration file.
Greetings
Marc