Michael wrote: > On Thursday, 11 April 2024 02:23:22 BST Dale wrote: >> Howdy, >> >> This failed once before but I didn't worry about it. However, since the >> profile update, it still fails. I'd like to figure out how to fix it. >> I tried doing a emerge -C and then emerging it again. No help. This is >> the output. It's not to long, whole thing. :-D > >>>>> Completed installing acct-user/man-1-r3 into >> /var/tmp/portage/acct-user/man-1-r3/image > OK, so far so good. :-) > > >> * Final size of build directory: 0 KiB >> * Final size of installed tree: 4 KiB >> >> ./ >> ./usr/ >> ./usr/lib/ >> ./usr/lib/sysusers.d/ >> ./usr/lib/sysusers.d/acct-user-man.conf >> >>>>> Done. >> * checking 1 files for package collisions >> >>>>> Merging acct-user/man-1-r3 to / >> error writing passwd entry: Invalid argument >> * User man already exists >> --- /usr/ >> --- /usr/lib/ >> --- /usr/lib/sysusers.d/ >> >>>>> /usr/lib/sysusers.d/acct-user-man.conf >> * Removing user man from group(s): root > What?! Group 'root' should only have user 'root' as its member: > > # grep root:x /etc/group > root:x:0:root > > >> * To retain the user's group membership in the local system >> * config, override with ACCT_USER_MAN_GROUPS or >> * ACCT_USER_MAN_GROUPS_ADD in make.conf. >> * Documentation reference: >> * >> https://wiki.gentoo.org/wiki/Practical_guide_to_the_GLEP_81_migration#Overri >> de_user_groups * Updating user man >> usermod: user 'man' does not exist in /etc/passwd > This is not right, unless you removed 'man' manually? > > # grep man /etc/passwd > man:x:13:15:System user; man:/dev/null:/sbin/nologin > > >> usermod: failed to unlock /etc/gshadow >> * usermod: user 'man' does not exist in /etc/passwd >> * usermod: failed to unlock /etc/gshadow > # stat /etc/passwd > File: /etc/passwd > Size: 1636 Blocks: 4 IO Block: 4096 regular file > Device: 259,2 Inode: 18587 Links: 1 > Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root) > > # stat /etc/shadow > File: /etc/shadow > Size: 815 Blocks: 2 IO Block: 4096 regular file > Device: 259,2 Inode: 18602 Links: 1 > Access: (0640/-rw-r-----) Uid: ( 0/ root) Gid: ( 0/ root) > > # stat /etc/gshadow > File: /etc/gshadow > Size: 636 Blocks: 2 IO Block: 4096 regular file > Device: 259,2 Inode: 18562 Links: 1 > Access: (0400/-r--------) Uid: ( 0/ root) Gid: ( 0/ root) > > Check what yours look like, then try to correct them. It would be a good > idea > to fsck the partition too and check smartctl, in case you have fs corruption.
I fixed it by commenting out the entry in the passwd file. It then created a new entry. I guess it was set wrong at some point. Just looks like emerge would be able to update it tho. Joost showing my setting was different gave me the clue that my current entry was wrong. I was kinda chicken to comment it out or remove it before then. ;-) Dale :-) :-)
