public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: n952162 <n952162@web.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] could there be a problem with acct-group/lp?
Date: Thu, 31 Dec 2020 08:20:22 +0100	[thread overview]
Message-ID: <4f97efa4-f37f-cbde-4a66-e5e4685f1acf@web.de> (raw)
In-Reply-To: <T547GQ33.BIENHF3Q.PMELTLXL@M7MBCYNG.UJURXKC3.FYDSIOE4>

On 12/31/20 12:33 AM, Jack wrote:
> On 2020.12.30 17:17, 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
> This seems to be the basic cause.


Perhaps.  But there are two "invalid argument" error messages before the
"already exists" msg.


> However, I have no idea what that emerge should do if the group it
> wants to install does already exist.  I can re-emerge this package
> with no problems.


That's interesting!  Maybe re-emerge would behave differently from a
de-install/emerge?

In any case though, crashing if the group already exists would be a bug
the developers should be interested in.


> Is this a new install or reinstall?  All the logic is in the eclass
> which does have the comment "Creates the group if it does not exist."


I was looking for that ... I didn't find groupadd in
/var/db/pkg/acct-group/lp-0.  Where should I look?


>
> What happens if you just run "emerge -1 acct-group/lp"?


Same thing


> Have you done a successful "emerge -auDvN @system" ?


Yes


> There may well be something else required still missing, but not an
> explicit dependency because it is part of @system.
>
>

One thing I just re-discovered is --keep-going, which works, thank
goodness, so I'll should have a working system (sometime tomorrow!),
albeit, without cups.




  parent reply	other threads:[~2020-12-31  7:24 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 [this message]
2020-12-31  9:33     ` Neil Bothwick
2021-01-01 20:13 ` [gentoo-user] could there be a problem with acct-group/lp? [RESOLVED] n952162

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=4f97efa4-f37f-cbde-4a66-e5e4685f1acf@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