Gentoo Archives: gentoo-user

From: "J. Roeleveld" <joost@××××××××.org>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] emerge conflict
Date: Fri, 13 Aug 2010 15:06:47
Message-Id: 201008131632.44518.joost@antarean.org
In Reply to: Re: [gentoo-user] emerge conflict by Daniel Wagener
1 On Friday 13 August 2010 15:36:23 Daniel Wagener wrote:
2 > On Fri, 13 Aug 2010 15:17:50 +0200
3 >
4 > "J. Roeleveld" <joost@××××××××.org> wrote:
5 > > On Friday 13 August 2010 14:15:59 Alan McKinnon wrote:
6 > > > On Friday 13 August 2010 16:04:53 Frank Schwidom wrote:
7 > > > > Hi
8 > > > >
9 > > > > i get the error:
10 > > > >
11 > > > > {
12 > > > > !!! Multiple package instances within a single package slot have
13 > > > > been pulled
14 > > > > !!! into the dependency graph, resulting in a slot conflict:
15 > > > >
16 > > > > media-libs/libpng:0
17 > > > >
18 > > > > ('ebuild', '/', 'media-libs/libpng-1.4.3', 'merge') pulled in by
19 > > > >
20 > > > > >=media-libs/libpng-1.2.43-r2:0 required by ('ebuild', '/',
21 > > > > >'x11-libs/cairo-1.8.10', 'merge')
22 > > > > >=media-libs/libpng-1.4 required by ('ebuild', '/',
23 > > > > >'x11-libs/gtk+-2.20.1-r1', 'merge')
24 > > > >
25 > > > > (and 27 more)
26 > > > >
27 > > > > }
28 > > > >
29 > > > > And i wonder that it seems not to be possible to install both libs
30 > > > > (libpng-1.2.43-r2:0, libpng-1.4) in the same time. Linux is
31 > > > > actually able to manage this by the lib-version and links.
32 > > >
33 > > > You have misread the portage output. It does not say it wants those
34 > > > versions.
35 > > >
36 > > > It says this:
37 > > > >=media-libs/libpng-1.2.43-r2:0
38 > > > >=media-libs/libpng-1.4
39 > > >
40 > > > Note the greater than or equal to.
41 > > >
42 > > > The limiting factor to multiple versions is not Linux, it is
43 > > > portage. Portage will not co-install two versions in the same SLOT.
44 > > >
45 > > > > Did i have overseen any gentoo switch that makes is possible? Or
46 > > > > is there any other option?
47 > > >
48 > > > This whole libpng mess was a right royal fuck up several months
49 > > > ago. I forget the specifics but IIRC a decent solution was
50 > > >
51 > > > emerge -C libpng
52 > > > emerge libpng
53 > > > revdep-rebuild
54 > > >
55 > > > The last step takes some time to complete, there is a lot of
56 > > > fall-out to deal with.
57 > > >
58 > > > As you are only hitting this now, I assume you have a stable system
59 > > > and are not using the masked versions of portage.
60 > > > @preserved-rebuild would save you lots of pain, but that feature is
61 > > > not available in stable versions of portage.
62 > > >
63 > > > For more info, check the archives. There is more mail there about
64 > > > this than you could ever possibly want to read.
65 > >
66 > > I actually hit this myself yesterday.
67 > > When emerging "libpng", it mentions a script that needs to be run. I
68 > > would suggest running that script.
69 > >
70 > > I think the following commands were the ones that led to a properly
71 > > upgraded system. It is now working for me, but it did take quite a
72 > > while. **
73 > > emerge -vauD --newuse world
74 > > lafilefixer --justfixit
75 > > /usr/sbin/libpng-1.4.x-update.sh
76 > > emerge -vauD --newuse world
77 > > revdep-rebuild -- -va
78 > > emerge -vauD --newuse world
79 > > **
80 > >
81 > > Alternatively, you could always try to one that should always work:
82 > >
83 > > emerge -vae world
84 > > (NOTE: This will rebuild _everything_)
85 > >
86 > > Btw, if you are using KDE, you might, like me, also hit issues with
87 > > akonadi not starting (I couldn't not use it anymore)
88 > > Post on the list if you hit it, I still have these fresh in my mind :)
89 > >
90 > > --
91 > > Joost
92 >
93 > This script is hopefully not the hack, that is said to be a problem in
94 > the future?
95 >
96 > http://blog.flameeyes.eu/2010/06/29/stable-users-libpng-update
97
98 Eeerh....
99 Not sure, guess I stopped reading too soon as I managed to get it to appear to
100 be working...
101
102 Anyway, am currently doing a " emerge -vae world " as I want to get it all
103 compiled using GCC 4.4. Guess that should 'fix' whatever damage that script
104 does?
105
106 --
107 Joost