From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id AC9AD158041 for ; Thu, 11 Apr 2024 08:52:41 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 57437E2A1C; Thu, 11 Apr 2024 08:52:35 +0000 (UTC) Received: from gw2.antarean.org (gw2.antarean.org [141.105.125.208]) by pigeon.gentoo.org (Postfix) with ESMTP id C0B27E2A06 for ; Thu, 11 Apr 2024 08:52:34 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by gw2.antarean.org (Postfix) with ESMTP id 4VFYNx5pW0z8tYj for ; Thu, 11 Apr 2024 08:52:33 +0000 (UTC) X-Virus-Scanned: amavisd-new at antarean.org Received: from gw2.antarean.org ([127.0.0.1]) by localhost (gw2.antarean.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oRC5SC6SQsgD for ; Thu, 11 Apr 2024 08:52:33 +0000 (UTC) Received: from mailstore1.adm.antarean.org (localhost [127.0.0.1]) by gw2.antarean.org (Postfix) with ESMTP id 4VFYNx1GCQz8tJf for ; Thu, 11 Apr 2024 08:52:33 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mailstore1.adm.antarean.org (Postfix) with ESMTP id 4VFYNw73qyz1M for ; Thu, 11 Apr 2024 08:52:32 +0000 (UTC) X-Virus-Scanned: amavisd-new at antarean.org Received: from mailstore1.adm.antarean.org ([127.0.0.1]) by localhost (mailstore1.adm.antarean.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TF33xYjfMGPI for ; Thu, 11 Apr 2024 08:52:12 +0000 (UTC) Received: from persephone.localnet (persephone.adm.antarean.org [10.55.16.48]) by mailstore1.adm.antarean.org (Postfix) with ESMTPA id 4VFYNX5XNNz17 for ; Thu, 11 Apr 2024 08:52:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=antarean.org; s=default; t=1712825532; bh=USTl2JLvAWw8v3l8UYBDzrOoqhVDgZdV3WF/R/BftkI=; h=From:To:Subject:Date:In-Reply-To:References; b=Ycx7M43xw9h0CYiscdBqX9Bu8/Q16nWtFaU8m5rOZrQShBs1Eb+gohogSL/coMii6 bre6DyWpI2ntenJdmrxCq+q4hK137GENp08k2TdAByiPTPXuEkGkmpxlcgJfh6CVQR 1yLAY3W+tKsRQUSriJdo30G7Votw3ReQ91m01QoA= From: "J. Roeleveld" 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 Message-ID: <1890516.tdWV9SEqCh@persephone> In-Reply-To: <2ce0c0dd-92a3-a22c-bda2-b75c62ca55fc@gmail.com> References: <8f2f20df-05f5-b512-c30b-f7b90614ca11@gmail.com> <2328101.ElGaqSPkdT@persephone> <2ce0c0dd-92a3-a22c-bda2-b75c62ca55fc@gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Archives-Salt: 2f7ec414-14cc-4780-99c4-d949301c4ece X-Archives-Hash: 75fd958e0b3ef834db929d1ae204183e 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, > > > > > > > >> * 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