From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Please help me with an emerge "slot" problem.
Date: Sun, 14 Jul 2013 17:00:33 +0200 [thread overview]
Message-ID: <51E2BD11.2000609@gmail.com> (raw)
In-Reply-To: <20130714125916.GA5164@acm.acm>
On 14/07/2013 14:59, Alan Mackenzie wrote:
> Hello, Philip,
>
> On Sat, Jul 13, 2013 at 09:00:34PM -0400, Philip Webb wrote:
>> 130713 Alan Mackenzie wrote:
>>> When I try "emerge -puND libgcrypt", I get
>>> !!! Multiple package instances within a single package slot have been pulled
>>> !!! into the dependency graph, resulting in a slot conflict:
>>> dev-libs/libgcrypt:0
>>> (dev-libs/libgcrypt-1.5.2-r1::gentoo, ebuild scheduled for merge) pulled in by
>>> (no parents that aren't satisfied by other packages in this slot)
>>> (dev-libs/libgcrypt-1.5.0-r2::gentoo, installed) pulled in by
>>> >=dev-libs/libgcrypt-1.1.90:0/0= required by (net-misc/vino-2.32.2-r1::gentoo, installed)
>
>> It looks like one of those standard conflicts,
>> which you resolve by unmerging Libgcrypt before merging the new version ;
>> after that, you may also need to remerge Vino .
>
> Thanks! I unmerged libgcrypt, then remerged it, then had some fun with
> pambase and shadow (whatever they are)
Oh dear, you don't know what those are, without them you have no user
accounts and can't log in :-)
shadow implements the Unix password scheme using /etc/shadow, plus all
the helper commands like useradd|mod|del etc
PAM is Pluggable Authentication Modules - a bunch of rules and configs
where you determine what exactly comprises a successful authentication.
If you wanted to implement a fingerprint swiper and retina scanner,
easiest would to be fit all that plumbing into PAM and tell the system
to use it. PAM ships out of the box using shadow as the default way to
auth users (i.e. by password).
pambase is what implements this default method. pam (the full thing)
implements the plumbing you need for everything else.
shadow and pam are renowned for causing blockers that can't be
automagically resolved, it's because they slot in at very low levels.
not liking eachother. I managed
> to get fully updated in the end, including merging the new libreoffice.
> It took a while.
Indeed. I find the only thing worse is icu. Even though the only docs I
have ever read are in English (usually the Queen's version), I still
can't get that thing off the system - libreoffice insists
--
Alan McKinnon
alan.mckinnon@gmail.com
prev parent reply other threads:[~2013-07-14 15:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-13 18:55 [gentoo-user] Please help me with an emerge "slot" problem Alan Mackenzie
2013-07-13 21:27 ` Bruce Hill
2013-07-14 1:00 ` Philip Webb
2013-07-14 12:59 ` Alan Mackenzie
2013-07-14 15:00 ` Alan McKinnon [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=51E2BD11.2000609@gmail.com \
--to=alan.mckinnon@gmail.com \
--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