public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Please help me with an emerge "slot" problem.
Date: Sun, 14 Jul 2013 12:59:16 +0000	[thread overview]
Message-ID: <20130714125916.GA5164@acm.acm> (raw)
In-Reply-To: <20130714010034.GA833@ca.inter.net>

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) not liking eachother.  I managed
to get fully updated in the end, including merging the new libreoffice.
It took a while.

-- 
Alan Mackenzie (Nuremberg, Germany).



  reply	other threads:[~2013-07-14 13:00 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 [this message]
2013-07-14 15:00     ` Alan McKinnon

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=20130714125916.GA5164@acm.acm \
    --to=acm@muc.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