Quoting Brian Potkin (firstname.lastname@example.org): > > After more thinking, my (wild) guess is that, at the time this is > > done, these groups...do not exist on the system. And "adduser <user> > > <group>" then fails when "<group>" doesn't exist. > > > > If I'm right, there are probably traces of this is the installer log, I'd guess. > > Not such a wild guess. .../... Right. The package changelog indeed does give the key: user-setup (1.3) unstable; urgency=low * Add first user to two additional groups: netdev and powerdev Note that this assumes that something creates these groups during the task installation, as hal does with powerdev. The first user is added to the groups in finish-install so the groups need not be static. Closes: #352713 .../... -- Joey Hess <email@example.com> Mon, 10 Jul 2006 18:23:44 -0400 In short, if packages that need some groups are installed *during installation*, then the first created user will be added to these groups. Which brings the question: what package is in charge of creating "lpadmin"?
Description: Digital signature