From: n952162 <n952162@web.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] could there be a problem with acct-group/lp? [RESOLVED]
Date: Fri, 1 Jan 2021 21:13:52 +0100 [thread overview]
Message-ID: <eba48762-b3d4-c75d-b9f7-b028cfb7607c@web.de> (raw)
In-Reply-To: <d495dc5c-c623-1d09-abdd-9c41e76b91d0@web.de>
On 12/30/20 11:17 PM, n952162 wrote:
> When I try to restore my pkgs, after the --depclean, the emerge fails.
> It seems like there's an error in the pre-inst script of acct-group/lp?
> That's need by cups:
>
>
> 1270~/adm/gentoo/emerged>sudo cat
> /var/tmp/portage/acct-group/lp-0-r1/temp/build.log
> * Package: acct-group/lp-0-r1
> * Repository: gentoo
> * Maintainer: systemd@gentoo.org printing@gentoo.org
> * USE: abi_x86_64 amd64 elibc_glibc kernel_linux userland_GNU
> * FEATURES: network-sandbox preserve-libs sandbox userpriv usersandbox
> >>> Unpacking source...
> >>> Source unpacked in /var/tmp/portage/acct-group/lp-0-r1/work
> >>> Preparing source in /var/tmp/portage/acct-group/lp-0-r1/work ...
> >>> Source prepared.
> >>> Configuring source in /var/tmp/portage/acct-group/lp-0-r1/work ...
> >>> Source configured.
> >>> Compiling source in /var/tmp/portage/acct-group/lp-0-r1/work ...
> >>> Source compiled.
> >>> Test phase [not enabled]: acct-group/lp-0-r1
>
> >>> Install acct-group/lp-0-r1 into
> /var/tmp/portage/acct-group/lp-0-r1/image
> >>> Completed installing acct-group/lp-0-r1 into
> /var/tmp/portage/acct-group/lp-0-r1/image
>
> * Final size of build directory: 4 KiB
> * Final size of installed tree: 20 KiB
>
> * checking 1 files for package collisions
> >>> Merging acct-group/lp-0-r1 to /
> error writing group entry: Invalid argument
> * Adding group 'lp' to your system ...
> error writing group entry: Invalid argument
> * - Groupid: 7
> groupadd: group 'lp' already exists
> * ERROR: acct-group/lp-0-r1::gentoo failed (preinst phase):
> * (no error message)
> *
> * Call stack:
> * ebuild.sh, line 125: Called pkg_preinst
> * environment, line 1194: Called acct-group_pkg_preinst
> * environment, line 360: Called enewgroup 'lp' '7'
> * environment, line 735: Called die
> * The specific snippet of code:
> * groupadd -r ${opts} "${egroup}" || die
> *
> * If you need support, post the output of `emerge --info
> '=acct-group/lp-0-r1::gentoo'`,
> * the complete build log and the output of `emerge -pqv
> '=acct-group/lp-0-r1::gentoo'`.
> * The complete build log is located at
> '/var/tmp/portage/acct-group/lp-0-r1/temp/build.log'.
> * The ebuild environment file is located at
> '/var/tmp/portage/acct-group/lp-0-r1/temp/environment'.
> * Working directory: '/var/tmp/portage/acct-group/lp-0-r1/homedir'
> * S: '/var/tmp/portage/acct-group/lp-0-r1/work'
> !!! FAILED preinst: 1
>
>
>
Confirmed: I found a mistake on my system:
lp:x:7:lp:me
The last colon should be a comma.
prev parent reply other threads:[~2021-01-01 20:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-30 22:17 [gentoo-user] could there be a problem with acct-group/lp? n952162
2020-12-30 23:33 ` Jack
2020-12-31 0:29 ` Michael
2020-12-31 7:34 ` n952162
2020-12-31 9:31 ` Neil Bothwick
2020-12-31 11:03 ` Michael
2020-12-31 13:14 ` Michael Orlitzky
2021-01-01 19:47 ` n952162
2021-01-01 19:50 ` n952162
2021-01-01 20:01 ` n952162
2020-12-31 7:20 ` n952162
2020-12-31 9:33 ` Neil Bothwick
2021-01-01 20:13 ` n952162 [this message]
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=eba48762-b3d4-c75d-b9f7-b028cfb7607c@web.de \
--to=n952162@web.de \
--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