public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] emerge conflict
Date: Fri, 13 Aug 2010 14:15:59 +0200	[thread overview]
Message-ID: <201008131416.00108.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <20100813140452.GA8350@BiggerBoxer>

On Friday 13 August 2010 16:04:53 Frank Schwidom wrote:
> Hi
> 
> i get the error:
> 
> {
> !!! Multiple package instances within a single package slot have been
> pulled
> !!! into the dependency graph, resulting in a slot conflict:
> 
> media-libs/libpng:0
> 
>   ('ebuild', '/', 'media-libs/libpng-1.4.3', 'merge') pulled in by
> 
>     >=media-libs/libpng-1.2.43-r2:0 required by ('ebuild', '/',
>     >'x11-libs/cairo-1.8.10', 'merge')
>     >=media-libs/libpng-1.4 required by ('ebuild', '/',
>     >'x11-libs/gtk+-2.20.1-r1', 'merge')
> 
>     (and 27 more)
> }
> 
> And i wonder that it seems not to be possible to install both libs
> (libpng-1.2.43-r2:0, libpng-1.4) in the same time. Linux is actually
> able to manage this by the lib-version and links.

You have misread the portage output. It does not say it wants those versions. 
It says this:

  >=media-libs/libpng-1.2.43-r2:0
  >=media-libs/libpng-1.4

Note the greater than or equal to.

The limiting factor to multiple versions is not Linux, it is portage. Portage 
will not co-install two versions in the same SLOT.

> Did i have overseen any gentoo switch that makes is possible? Or is
> there any other option?

This whole libpng mess was a right royal fuck up several months ago. I forget 
the specifics but IIRC a decent solution was

emerge -C libpng
emerge libpng
revdep-rebuild

The last step takes some time to complete, there is a lot of fall-out to deal 
with. 

As you are only hitting this now, I assume you have a stable system and are 
not using the masked versions of portage. @preserved-rebuild would save you 
lots of pain, but that feature is not available in stable versions of portage.

For more info, check the archives. There is more mail there about this than 
you could ever possibly want to read.

-- 
alan dot mckinnon at gmail dot com



  reply	other threads:[~2010-08-13 13:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-13 14:04 [gentoo-user] emerge conflict Frank Schwidom
2010-08-13 12:15 ` Alan McKinnon [this message]
2010-08-13 13:17   ` J. Roeleveld
2010-08-13 13:36     ` Daniel Wagener
2010-08-13 14:32       ` J. Roeleveld
2010-08-13 16:31       ` Alan McKinnon
2010-08-13 22:52         ` Dale
2010-08-13 13:06 ` Mark Knecht
  -- strict thread matches above, loose matches on Subject: below --
2016-09-17 23:12 Philip Webb
2016-09-18  0:58 ` Daniel Frey
2016-09-18  1:55   ` Adam Carter
2016-09-18  4:35     ` Gregory Woodbury
2016-09-18  9:50 ` Neil Bothwick

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=201008131416.00108.alan.mckinnon@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