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: Fri, 1 Jan 2021 20:47:54 +0100 [thread overview]
Message-ID: <1ffb0a7b-2b35-4f48-2283-e75bbf8c94ec@web.de> (raw)
In-Reply-To: <a56be9aa-0dd1-dc35-27ef-f2e74f306f2a@gentoo.org>
On 12/31/20 2:14 PM, Michael Orlitzky wrote:
> On 12/31/20 2:34 AM, n952162 wrote:
>>
>> cups was already installed. I considered removing it, but several other
>> things, like ghostscript (!) are dependent on it. I'm using
>> --keep-going for now. I suspect a bug in acct-group/lp that will get
>> cleared up.
>>
>
> If it's a bug in the acct-user eclass, it's a rare one. It would help
> if you could pin down the root cause. It's not something easy like "it
> fails if the user already exists." Every user and group ebuild is
> already at "-r1", which means they've been reinstalled at least once
> on most peoples' machines.
>
Perhaps this is relevant:
https://forums.gentoo.org/viewtopic-p-7975642.html
I haven't tried commenting out the group yet because my update is still
in progress...
I'd considering removing the group, like, legally, but was afraid it
might erase things, like my cups ppd files. But just commenting the
group out is genius.
next prev parent reply other threads:[~2021-01-01 19:52 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 [this message]
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 ` [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=1ffb0a7b-2b35-4f48-2283-e75bbf8c94ec@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