[pkg-firebird-general] Bug#514379: firebird2.0-classic-common postinst script does not create proper user:group
Damyan Ivanov
dmn at debian.org
Thu Apr 2 11:57:08 UTC 2009
tags 514379 unreproducible moreinfo
thanks
-=| Fabricio Cannini - Yahoo, Fri, Feb 06, 2009 at 08:25:57PM -0200 |=-
> Package: firebird2.0-classic
> Version: 2.0.3.12981.ds1-14~bpo40+1
>
>
> When performing its instalation routines, the said script does not create the
> proper user:group tuple.
Was there an error message?
> Something like this, in firebird2.0-server-common.postinst, would
> solve the problem:
>
>
> --- firebird2.0-server-common.postinst.orig 2009-02-06 19:57:49.854848585 -0200
> +++ firebird2.0-server-common.postinst 2009-02-06 20:03:06.878848150 -0200
> @@ -30,8 +30,10 @@
>
> checkFirebirdAccount() {
>
> + adduser --system --quiet --group firebird
> +
> adduser --system --quiet --shell /bin/bash --home $VAR \
> - --group --gecos "Firebird Database Administator" firebird
> + --group firebird --gecos "Firebird Database Administator" firebird
> }
According to adduser(1), --group alone shall be sufficient:
Add a system user
If called with one non-option argument and the --system
option, adduser will add a system user. If a user with
the same name already exists in the system uid range (or, if
the uid is specified, if a user with that uid already
exists), adduser will exit with a warning.
By default, system users are placed in the nogroup group.
To place the new system user in an already existing group,
use the --gid or --ingroup options. To place the new
system user in a new group with the same ID, use the --group
option.
Running the above command in a fresh chroot runs fine. Even with
adduser from Etch. I looked at the changelog and see no changes that
would alter that behaviour between the Etch version and now.
So, how can I reproduce that?
--
dam JabberID: dam at jabber.minus273.org
More information about the pkg-firebird-general
mailing list