From: "J. Roeleveld" <joost@antarean.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] acct-user/man usermod: user 'man' does not exist in /etc/passwd
Date: Thu, 11 Apr 2024 10:52:12 +0200 [thread overview]
Message-ID: <1890516.tdWV9SEqCh@persephone> (raw)
In-Reply-To: <2ce0c0dd-92a3-a22c-bda2-b75c62ca55fc@gmail.com>
On Thursday, 11 April 2024 10:16:52 CEST Dale wrote:
> J. Roeleveld wrote:
> > On Thursday, 11 April 2024 03:23:22 CEST 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
> >>
> >>>>> Failed to install acct-user/man-1-r3, Log file:
> >>>>> '/var/log/portage/acct-user:man-1-r3:20240411-011746.log'
> >>>>>
> >>>>> Jobs: 0 of 1 complete, 1 failed Load avg: 2.12,
> >
> > <snipped>
> >
> >> * FAILED postinst: 1
> >> *
> >> * The following package has failed to build, install, or execute
> >> postinst:
> >> *
> >> * (acct-user/man-1-r3:0/0::gentoo, ebuild scheduled for merge), Log
> >> file:
> >> * '/var/log/portage/acct-user:man-1-r3:20240411-011746.log'
> >> *
> >>
> >> * GNU info directory index is up-to-date.
> >>
> >> (chroot) root@fireball / #
> >>
> >>
> >>
> >> Any ideas? It did install once long ago when the group and user thing
> >> started.
> >>
> >> Ideas??
> >
> > First idea, if "man" exists, check if it matches current systems.
> >
> > This is on a system less then 1 month old:
> >
> > $ id man
> > uid=13(man) gid=15(man) groups=15(man)
> >
> > --
> > Joost
>
> Mine says:
>
>
> root@fireball / # id man
> uid=14357(man) gid=0(root) groups=0(root),15(man)
> root@fireball / #
>
>
> It doesn't match yours but it has something there. I'm surprised that
> doing a emerge -C and then emerging it again didn't fix it but I guess
> it adds something to those files but doesn't remove it when
> uninstalled. So, I did some editing. The old line, I commented it
> out. Then it emerged and added the new line.
>
>
> man:x:13:15:System user; man:/dev/null:/sbin/nologin
> #man:!:14357:0:99999:7:::
>
>
> With it set like that, it emerges. This is what the output of your
> command looks like now.
>
>
> root@fireball / # id man
> uid=13(man) gid=15(man) groups=15(man)
> root@fireball / #
>
>
> Now it matches yours.
>
> Is this a bug or something? I don't tend to mess with that file
> myself. :/
>
> Dale
>
> :-) :-)
You might have some files owned by an unknown user on your system now
(especially man-pages?)
Looking back at the original error message, it did complain about "man" being
part of the "root" group.
doing a usermod to remove that group would have worked as well.
--
Joost
next prev parent reply other threads:[~2024-04-11 8:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-11 1:23 [gentoo-user] acct-user/man usermod: user 'man' does not exist in /etc/passwd Dale
2024-04-11 5:22 ` J. Roeleveld
2024-04-11 8:16 ` Dale
2024-04-11 8:52 ` J. Roeleveld [this message]
2024-04-11 7:57 ` Michael
2024-04-11 9:22 ` Dale
2024-04-11 9:30 ` Michael
2024-04-11 11:58 ` Dale
2024-04-11 14:52 ` Michael
2024-04-11 15:08 ` Dale
2024-04-11 15:41 ` Michael
2024-04-12 14:32 ` Dale
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1890516.tdWV9SEqCh@persephone \
--to=joost@antarean.org \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox