Bug 19604 – slocate not in /etc/group file after a fresh install

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Tobias Eichert 2003-04-19 06:45:35 UTC]

After a fresh installation I expected to run the slocate (updatedb) script.
slocate won't run until it's got an entry in /etc/group.
The solution is to remerge slocate so /etc/group gets updated.

Reproducible: Always
Steps to Reproduce:

1. Do a fresh Gentoo installation ;-)
2. Try to run slocate
3. emerge slocate again
4. Try again

[Comment 1 Brandon Low (RETIRED) 2003-04-19 10:53:46 UTC]

same version of slocate both times?  Did slocate get merged as part of system before you did a baselayout update with CONFIG_PROTECT="" or something?  It should add the group regardless of when it gets installed as long as the group didn't previously exist.

[Comment 2 Mr. Bones. (RETIRED) 2003-04-19 17:12:35 UTC]

I noticed this same thing myself last night.

I wonder if this is caused by emerging baselayout after slocate with CONFIG_PROTECT turned off.

[Comment 3 Brandon Low (RETIRED) 2003-04-22 19:36:39 UTC]

So perhaps we need to get the slocate group added to baselayout and assigned a number, let me get Azarah's thoughts and hopefully a number choice :)

And btw: heya viz, how's stuff? :-D

[Comment 4 PJ 2003-04-23 00:34:58 UTC]

Just wanted to confirm this. I just did a fresh install of 1.4rc4 and ran into this same problem. The fix described above worked for me as well.

[Comment 5 Martin Schlemmer (RETIRED) 2003-04-27 11:15:48 UTC]

Added baselayout-1.8.5.9 to fix this.  Will be in next unstable baselayout
as well.

[Comment 6 Mr. Bones. (RETIRED) 2003-08-01 10:27:31 UTC]

*** Bug 25714 has been marked as a duplicate of this bug. ***