Debian Bug report logs - #468152
adduser: Parameter --ingroup does not work

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Daniel Migowski <dmigowski@ikoffice.de>

To: submit@bugs.debian.org

Subject: adduser: Parameter --ingroup does not work

Date: Wed, 27 Feb 2008 12:09:46 +0100

Package: adduser
Version: 3.102
Severity: normal

*** Please type your report below this line ***

Parameter --ingroup simply does not work. To test, invoke adduser like this:

 adduser peter --ingroup cdrom

I assume, a "cat /etc/group | grep cdrom" should bring something like this:

 cdrom:x:24:peter

and not this:

 cdrom:x:24:

If I am wrong, then this is a bugreport for uncomprehensible documentation,
since this says:

 --ingroup GROUP
       Add  the new user to GROUP instead of a usergroup or the default
       group defined by USERS_GID in the adduser.conf file.

And i wonder, what differs "GROUP" from "a usergroup", btw.

With best regards,
Daniel Migowski

-- System Information:
Debian Release: 4.0
 APT prefers stable
 APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.23.13-ikoffice
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Versions of packages adduser depends on:
ii  debconf [debconf-2.0]       1.5.11etch1  Debian configuration 
management sy
ii  passwd                      1:4.0.18.1-7 change and administer 
password and
ii  perl-base                   5.8.8-7etch1 The Pathologically Eclectic 
Rubbis

adduser recommends no packages.

-- debconf information:
 adduser/homedir-permission: true

Message #10 received at 468152@bugs.debian.org (full text, mbox, reply):

From: Marc Haber <mh+debian-packages@zugschlus.de>

To: Daniel Migowski <dmigowski@ikoffice.de>, 468152@bugs.debian.org

Subject: Re: [Adduser-devel] Bug#468152: adduser: Parameter --ingroup does not work

Date: Wed, 27 Feb 2008 12:17:26 +0100

On Wed, Feb 27, 2008 at 12:09:46PM +0100, Daniel Migowski wrote:
> Parameter --ingroup simply does not work. To test, invoke adduser like this:
> 
>   adduser peter --ingroup cdrom

try

adduser --ingroup cdrom peter

as documented.

Greetings
Marc

-- 
-----------------------------------------------------------------------------
Marc Haber         | "I don't trust Computers. They | Mailadresse im Header
Mannheim, Germany  |  lose things."    Winona Ryder | Fon: *49 621 72739834
Nordisch by Nature |  How to make an American Quilt | Fax: *49 3221 2323190

Message #15 received at 468152@bugs.debian.org (full text, mbox, reply):

From: Stephen Gran <sgran@debian.org>

To: Daniel Migowski <dmigowski@ikoffice.de>, 468152@bugs.debian.org

Subject: Re: [Adduser-devel] Bug#468152: adduser: Parameter --ingroup does not work

Date: Wed, 27 Feb 2008 11:25:16 +0000

[Message part 1 (text/plain, inline)]

This one time, at band camp, Daniel Migowski said:
> 
> Parameter --ingroup simply does not work. To test, invoke adduser like this:
> 
>   adduser peter --ingroup cdrom
> 
> I assume, a "cat /etc/group | grep cdrom" should bring something like this:
> 
>   cdrom:x:24:peter
> 
> and not this:
> 
>   cdrom:x:24:

The --ingroup option affects what the user's 'primary' group is - this
information is stored in the passwd file, not the groups file.  So,
getent passwd peter should return that he is in group 24, or cdrom.

> If I am wrong, then this is a bugreport for uncomprehensible documentation,
> since this says:
> 
>   --ingroup GROUP
>         Add  the new user to GROUP instead of a usergroup or the default
>         group defined by USERS_GID in the adduser.conf file.
> 
> And i wonder, what differs "GROUP" from "a usergroup", btw.

It is sort of an arbitrary way of thinking about it, it's true.  The
split is:
peter has some admin defined group as primary (cdrom)
peter has a primary group same as username (peter - this is a usergroup)
peter has the same primary group as all other users (group users)

Does that help?  Or do you have a better wording for the documentation?

Cheers,
-- 
 -----------------------------------------------------------------
|   ,''`.                                            Stephen Gran |
|  : :' :                                        sgran@debian.org |
|  `. `'                        Debian user, admin, and developer |
|    `-                                     http://www.debian.org |
 -----------------------------------------------------------------

[signature.asc (application/pgp-signature, inline)]

Message #20 received at 468152@bugs.debian.org (full text, mbox, reply):

From: Daniel Migowski <dmigowski@ikoffice.de>

To: Stephen Gran <sgran@debian.org>

Cc: 468152@bugs.debian.org

Subject: Re: [Adduser-devel] Bug#468152: adduser: Parameter --ingroup does not work

Date: Wed, 27 Feb 2008 13:59:46 +0100

Hello Stephan,

Thank you for your enlightening response.

Stephen Gran schrieb:
> This one time, at band camp, Daniel Migowski said:
>   
>> Parameter --ingroup simply does not work. To test, invoke adduser like this:
>>
>>   adduser peter --ingroup cdrom
>>
>> I assume, a "cat /etc/group | grep cdrom" should bring something like this:
>>
>>   cdrom:x:24:peter
>>
>> and not this:
>>
>>   cdrom:x:24:
>>     
>
> The --ingroup option affects what the user's 'primary' group is - this
> information is stored in the passwd file, not the groups file.  So,
> getent passwd peter should return that he is in group 24, or cdrom.
>   
This makes sense, and works.
>> If I am wrong, then this is a bugreport for uncomprehensible documentation,
>> since this says:
>>
>>   --ingroup GROUP
>>         Add  the new user to GROUP instead of a usergroup or the default
>>         group defined by USERS_GID in the adduser.conf file.
>>
>> And i wonder, what differs "GROUP" from "a usergroup", btw.
>>     
> It is sort of an arbitrary way of thinking about it, it's true.  The
> split is:
> peter has some admin defined group as primary (cdrom)
> peter has a primary group same as username (peter - this is a usergroup)
> peter has the same primary group as all other users (group users)
>
> Does that help?  Or do you have a better wording for the documentation?
>   
It helps. I wasn't aware of the primary/secondary group concept. And my 
try for a better wording of the documentation is this (This is what I 
would have understood better, but I am no linux guru, so if this is too 
obvious its okey for me know.):

Set the new users primary group to GROUP instead of creating a new 
usergroup and using this as the primary group or using the default group 
defined by USERS_DIG in the adduser.conf file. If you just want to add 
the new user to other secondary groups, use "adduser <user> <group>" 
after creating the user.

With best regards,
Daniel Migowski

Message #25 received at 468152@bugs.debian.org (full text, mbox, reply):

From: Stephen Gran <sgran@debian.org>

To: Daniel Migowski <dmigowski@ikoffice.de>, 468152@bugs.debian.org

Subject: Re: [Adduser-devel] Bug#468152: Bug#468152: adduser: Parameter --ingroup does not work

Date: Wed, 27 Feb 2008 13:20:25 +0000

[Message part 1 (text/plain, inline)]

This one time, at band camp, Daniel Migowski said:
> Hello Stephan,
> 
> Thank you for your enlightening response.

I'm glad it was helpful.

> Stephen Gran schrieb:
> > This one time, at band camp, Daniel Migowski said:
> > > If I am wrong, then this is a bugreport for uncomprehensible documentation,
> > > since this says:
> > >
> > >   --ingroup GROUP
> > >         Add  the new user to GROUP instead of a usergroup or the default
> > >         group defined by USERS_GID in the adduser.conf file.
> > >
> > > And i wonder, what differs "GROUP" from "a usergroup", btw.
> >
> > It is sort of an arbitrary way of thinking about it, it's true.  The
> > split is:
> > peter has some admin defined group as primary (cdrom)
> > peter has a primary group same as username (peter - this is a usergroup)
> > peter has the same primary group as all other users (group users)
> >
> > Does that help?  Or do you have a better wording for the documentation?
>   
> It helps. I wasn't aware of the primary/secondary group concept. And my 
> try for a better wording of the documentation is this (This is what I 
> would have understood better, but I am no linux guru, so if this is too 
> obvious its okey for me know.):
> 
> Set the new users primary group to GROUP instead of creating a new 
> usergroup and using this as the primary group or using the default group 
> defined by USERS_DIG in the adduser.conf file. If you just want to add 
> the new user to other secondary groups, use "adduser <user> <group>" 
> after creating the user.

Something like that seems reasonable, I agree.  I will add a note to the
documentation that --ingroup does not add additional groups, it affects
the user's primary group.  From my point of view, I thought that was
obvious enough not to need to be stated explicitly, but I apparently
have the blinders of having worked with this stuff for too long, and
have to be corrected :)

Thanks for the report,
-- 
 -----------------------------------------------------------------
|   ,''`.                                            Stephen Gran |
|  : :' :                                        sgran@debian.org |
|  `. `'                        Debian user, admin, and developer |
|    `-                                     http://www.debian.org |
 -----------------------------------------------------------------

[signature.asc (application/pgp-signature, inline)]

Message #30 received at 468152-close@bugs.debian.org (full text, mbox, reply):

From: Stephen Gran <sgran@debian.org>

To: 468152-close@bugs.debian.org

Subject: Bug#468152: fixed in adduser 3.106

Date: Sun, 02 Mar 2008 17:17:03 +0000

Source: adduser
Source-Version: 3.106

We believe that the bug you reported is fixed in the latest version of
adduser, which is due to be installed in the Debian FTP archive:

adduser_3.106.dsc
  to pool/main/a/adduser/adduser_3.106.dsc
adduser_3.106.tar.gz
  to pool/main/a/adduser/adduser_3.106.tar.gz
adduser_3.106_all.deb
  to pool/main/a/adduser/adduser_3.106_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 468152@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Stephen Gran <sgran@debian.org> (supplier of updated adduser package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Sun, 02 Mar 2008 16:57:21 +0000
Source: adduser
Binary: adduser
Architecture: source all
Version: 3.106
Distribution: unstable
Urgency: low
Maintainer: Debian Adduser Developers <adduser-devel@lists.alioth.debian.org>
Changed-By: Stephen Gran <sgran@debian.org>
Description: 
 adduser    - add and remove users and groups
Closes: 145430 435778 439212 442203 447104 447868 451321 451967 452289 452290 453419 454928 468152
Changes: 
 adduser (3.106) unstable; urgency=low
 .
   [ Joerg Hoh ]
   * adduser exits with returncode 1 if trying to add an already existing user
     as system user. Thanks to Vincent Bernat; Closes: #435778
   * deluser: warn if you want to remove the root account. Closes: #145430
   * deluser: fix backup when bzip2 is not available. Closes: #453419
   * deluser: print correct warning when you removed the last user in a group;
     thanks Marc 'Zugschlus' Haber and Peter Eisentraut
     (Closes: #454928,#451967)
 .
   [ Stephen Gran ]
   * Translation:
     be (thanks Pavel Piatruk <berserker@neolocation.com>)( closes: #447104)
     fr (thanks Nicolas François <nicolas.francois@centraliens.net>)
     (closes: #442203)
     ru (thanks Yuri Kozlov <kozlov.y@gmail.com>)(closes: #452289, #452290)
     sk (thanks Ivan Masár <helix84@centrum.sk>)(closes: #439212)
     zh_CN (thanks LI Daobing <lidaobing@gmail.com>)(closes: #447868)
   * Clarify --in-group documentation (closes: #468152)
   * deluser: Let tar gzip/bzip backups directly (closes: #451321)
   * Update Standards Version (no changes)
   * Homepage, Vcs-Svn and Vcs-Browser fields added
   * Do nothing in binary-arch
Files: 
 542e266dab99f99dea31a4ba016fd7d7 835 admin important adduser_3.106.dsc
 3329395cc47d3f5f147e87028736387b 262830 admin important adduser_3.106.tar.gz
 be4885c8629de328cc18cff8352d280e 183366 admin important adduser_3.106_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHyt0bSYIMHOpZA44RAoekAKDP4rjhUqCdHRv0lnrQyQTGnK2fbgCfX/Jo
ffCcTqO+7IMpzabvF+jGodA=
=bPI8
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.