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.
if you dont have a root group in /etc/group, your system is broken
(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.
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.
(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?
I've seen a "5A" in files before from nano users when they hit some bad key combo
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.
(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!
