On Tue, Mar 04, 2025 at 08:11:10AM +0100, Marc Haber wrote:
> I expect a fix for this adduser issue for later today and apologize for
> the problem. There is no need to debug other packages until adduser
> 3.144 is uploaded.
Can you try this trivial change?
diff --git a/adduser b/adduser
index 6fc7489..3166319 100755
--- a/adduser
+++ b/adduser
@@ -1154,6 +1154,7 @@ sub existing_user_status {
$ret |= EXISTING_SYSTEM if \
($uid >= $config{"first_system_uid"} && $uid <=
$config{"last_system_uid"});
$ret |= EXISTING_LOCKED if (substr($pw,0,1) eq "!"); # TODO: also
check expiry?
+ $ret |= EXISTING_LOCKED if (substr($pw,0,1) eq "*"); # TODO: also
check expiry?
}
log_trace( "existing_user_status( %s, %s ) returns %s", $new_name,
$new_uid, $ret );
return $ret;
I have, in a container, installed adduser and colord from testing,
changed /etc/shadow from colord:!:19977:::::: to colord:*:19977::::::,
upgraded adduser and colord. The bug issue was reproducible that way.
After patching adduser, the colord upgrade went through without issues.
And there is now a test case checking this.
I'll upload as soon as I get your feedback (or tonight).
Greetings
Marc
