Bug 221861 – sys-fs/device-mapper-1.02.24-r1 emerge fails - no such group root

• Product: Gentoo Linux
• Status: RESOLVED INVALID

[Description joe 2008-05-12 19:25:34 UTC]

An emerge deep update world dies on device-mapper package. Here is a line with one error on it:

/usr/bin/install -c -D -o root -g root -m 555  libdevmapper-event.so \                /var/tmp/portage/sys-fs/device-mapper-1.02.24-r1/image//usr/lib/libdevmapper-event.so.1.02

/usr/bin/install: invalid group `root'




Reproducible: Always

Steps to Reproduce:
1. use my system
2. emerge --deep --update world
3. watch in horror

Actual Results:  
There is no die message ;/
Results in failure to emerge package device-mapper.

Expected Results:  
I'd expect to successfully update my gentoo system.

[Comment 1 SpanKY 2008-05-13 03:10:32 UTC]

if you dont have a root group in /etc/group, your system is broken

[Comment 2 joe 2008-05-13 13:52:20 UTC]

(In reply to comment #1)
> if you dont have a root group in /etc/group, your system is broken
> 

first line of my /etc/group file:

5Aroot::0:root

I dont know where the hell 5Aroot came from but that is whats there. Please advise.

[Comment 3 SpanKY 2008-05-13 14:13:30 UTC]

nothing in Gentoo should go randomly touching /etc/group.  unless you can figure out where/how/when it got modified, just fix it and be done.

[Comment 4 joe 2008-05-13 16:09:16 UTC]

(In reply to comment #3)
> nothing in Gentoo should go randomly touching /etc/group.  unless you can
> figure out where/how/when it got modified, just fix it and be done.
> 

So to fix the file, changing
5Aroot::0:root
to
root::0:root

should suffice right?

As for the files with group as 5Aroot instead of root, I need to recursively change all files to group root IF they are of group 5Aroot. I'm not as good with bash scripting as I should be. How can I do this?

[Comment 5 Doug Goldstein (RETIRED) 2008-05-13 16:24:50 UTC]

I've seen a "5A" in files before from nano users when they hit some bad key combo

[Comment 6 SpanKY 2008-05-13 17:50:36 UTC]

nothing knows about group "5Aroot".  the system encodes the gid of "0".  when user utilities want to print out something human readable, they convert the numeric gid to a string via /etc/group.  so just fix that one file and that's it.

[Comment 7 joe 2008-05-13 18:04:53 UTC]

(In reply to comment #6)
> nothing knows about group "5Aroot".  the system encodes the gid of "0".  when
> user utilities want to print out something human readable, they convert the
> numeric gid to a string via /etc/group.  so just fix that one file and that's
> it.
> 

You're right. I've done just that, and device-mapper emerges just fine. Thanks for your help!