>From what I can tell, it's adduser sending some output to STDOUT which
is causing this postinst script to fail. It looks like the --quiet
flag isn't being respected, and lines 29-33 of
/usr/share/debconf/confmodule are ineffective, or at least don't seem
to do what their comments say they should.
The following two patches both solve the problem with
/usr/sbin/adduser in two different ways: (a) respect the --quiet
option and don't send anything to STDOUT (as per its description), or
(b) send the notice/warning to STDERR instead. I'm not sure which
method will be preferred by the team responsible for
/usr/sbin/adduser.
--- /usr/sbin/adduser 2010-11-22 10:16:03.000000000 +1300
+++ adduser 2011-02-17 10:58:53.000000000 +1300
@@ -450,7 +450,8 @@
if ($?>>8);
&cleanup(sprintf((gtx("`%s' exited from signal %d.
Exiting.\n")), "$chage -M 99999 $new_name", $?&255));
} else {
- printf (gtx("%s failed with return code 15, shadow not enabled,
password aging cannot be set. Continuing.\n"), $chage);
+ printf gtx("%s failed with return code 15, shadow not enabled,
password aging cannot be set. Continuing.\n"), $chage
+ if $verbose;
}
}
&invalidate_nscd();
or
--- /usr/sbin/adduser 2010-11-22 10:16:03.000000000 +1300
+++ adduser 2011-02-17 11:08:56.000000000 +1300
@@ -450,7 +450,7 @@
if ($?>>8);
&cleanup(sprintf((gtx("`%s' exited from signal %d.
Exiting.\n")), "$chage -M 99999 $new_name", $?&255));
} else {
- printf (gtx("%s failed with return code 15, shadow not enabled,
password aging cannot be set. Continuing.\n"), $chage);
+ printf STDERR (gtx("%s failed with return code 15, shadow not
enabled, password aging cannot be set. Continuing.\n"), $chage);
}
}
&invalidate_nscd();
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
