Package: adduser Version: 3.143 Followup-For: Bug #1099470 Control: merge 1099470 1099477
Hi Vincent, > So, if EXISTING_LOCKED is set, then the test will be false and will not > trigger the error. yes, looked into the code and changes and came to the same conclusion. I will mark by bug report in #1099477 as duplication of this one. > Now, I don't understand why the account is not locked on the old machine and > the account is locked on the more recent machine. > A past bug of adduser? I just checked /etc/shadow, and from one point in time all system users are locked (!), and the previous one (*). Seems to have change somewhere before 07.10.2021, this is were my first locked entry happened. br m -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (504, 'unstable'), (503, 'testing'), (502, 'experimental'), (500, 'unstable-debug'), (1, 'experimental-debug') Architecture: amd64 (x86_64) Kernel: Linux 6.12.17-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages adduser depends on: ii passwd 1:4.17.3-1 adduser recommends no packages. Versions of packages adduser suggests: ii cron 3.0pl1-194 ii liblocale-gettext-perl 1.07-7+b1 ii perl 5.40.1-2 pn quota <none> -- debconf information excluded
