1 |
On 01/22/2015 10:19, Peter Stuge wrote: |
2 |
> Joshua Kinard wrote: |
3 |
>> Using seed stage3 stages I built 6 months ago (but never released due |
4 |
>> to getting sidetracked), I run into errors like this: |
5 |
>> |
6 |
>> !!! Multiple package instances within a single package slot have been pulled |
7 |
>> !!! into the dependency graph, resulting in a slot conflict: |
8 |
>> |
9 |
>> dev-lang/perl:0 |
10 |
>> |
11 |
>> (dev-lang/perl-5.20.1-r4:0/5.20::gentoo, ebuild scheduled for merge) pulled in by |
12 |
>> =dev-lang/perl-5.20* required by |
13 |
>> (virtual/perl-ExtUtils-ParseXS-3.240.0:0/0::gentoo, ebuild scheduled for merge) |
14 |
>> ^ ^^^^^ |
15 |
>> (and 16 more with the same problem) |
16 |
>> |
17 |
>> (dev-lang/perl-5.18.2-r2:0/5.18::gentoo, ebuild scheduled for merge) pulled in by |
18 |
>> dev-lang/perl:0/5.18=[-build(-)] required by |
19 |
>> (dev-perl/libintl-perl-1.230.0:0/0::gentoo, installed) |
20 |
>> ^^^^^^^^ |
21 |
>> =dev-lang/perl-5.18* required by |
22 |
>> (virtual/perl-ExtUtils-Manifest-1.630.0-r1:0/0::gentoo, installed) |
23 |
>> ^ ^^^^^ |
24 |
>> (and 2 more with the same problems) |
25 |
>> |
26 |
>> It's hard to read mess like that and trace down the offending package, |
27 |
>> fix it, and make catalyst happy. |
28 |
> |
29 |
> Lots of dev-perl packages have specific minor version dependencies on |
30 |
> dev-lang/perl, maybe because sometimes the package is included in perl |
31 |
> and sometimes not. It's a f*ing mess. You have to look up all your |
32 |
> installed dev-perl packages manually and find which ones are either |
33 |
> too old to know about perl-5.20 or not compatible with it, and then |
34 |
> you have to unmerge those manually. |
35 |
|
36 |
In the past, it's been possible to have Portage deal with the updates to Perl, |
37 |
but only as long as you hit all of the packages in the same update run to |
38 |
satisfy the dependency chain. Newer portage seems to not do that anymore. But |
39 |
that output is horrible. Even with the color coding, it's not directly |
40 |
apparent which package is the problem package. |
41 |
|
42 |
I once had a Perl update issue bad enough that I removed all perl packages |
43 |
entirely, then remerged them from scratch. Took a while, but it fixed things. |
44 |
|
45 |
|
46 |
>> Kinda defeats the purpose of catalyst in the first place. |
47 |
> |
48 |
> The proper way is to build stage1+2+3 yourself, then this mess |
49 |
> doesn't happen. But like you I too cheat a little, and have to deal |
50 |
> with the mess. |
51 |
|
52 |
Well, I was trying to do it the right way by going stage1 -> stage2 -> stage3. |
53 |
I was using a stage3 that I built over the summer as the seed stage for the |
54 |
new stage1 when I started running into problems with Perl. I finally fixed |
55 |
that, got stage1 built, then got bit by Bug #447126 while trying to build the |
56 |
stage2. So now, I have to start a stage2 run, then after the unpack (but |
57 |
before catalyst drops into the chroot), edit the chroot's make.conf and remove |
58 |
sandbox from FEATURES, which is apparently part of the problem. |
59 |
|
60 |
Just irritating. And I know I'm earning no sympathy when I point out that my |
61 |
build machines (an Octane and an Onyx2) aren't the fastest things on the |
62 |
planet, nor the most power efficient (1 kW between the both of them). But I'd |
63 |
at least like to waste that power on actual compile jobs, not watching emerge's |
64 |
little spinner all the time as I try to fix various dependency bugs or other |
65 |
oddities that seemingly came out of nowhere (because the summertime stage runs |
66 |
were flawless in execution). |
67 |
|
68 |
-- |
69 |
Joshua Kinard |
70 |
Gentoo/MIPS |
71 |
kumba@g.o |
72 |
4096R/D25D95E3 2011-03-28 |
73 |
|
74 |
"The past tempts us, the present confuses us, the future frightens us. And our |
75 |
lives slip away, moment by moment, lost in that vast, terrible in-between." |
76 |
|
77 |
--Emperor Turhan, Centauri Republic |