1 |
On Sat, 09 Dec 2017 03:51:03 -0500, |
2 |
Alan McKinnon wrote: |
3 |
> |
4 |
> On 08/12/2017 21:12, John Covici wrote: |
5 |
> > On Fri, 08 Dec 2017 11:42:16 -0500, |
6 |
> > Alan McKinnon wrote: |
7 |
> >> |
8 |
> >> On 07/12/2017 17:46, John Covici wrote: |
9 |
> >>> On Thu, 07 Dec 2017 09:37:56 -0500, |
10 |
> >>> Alan McKinnon wrote: |
11 |
> >>>> |
12 |
> >>>> On 07/12/2017 07:44, John Covici wrote: |
13 |
> >>>>> Hi. In preparing for the profile switch and the emerge -e world, I |
14 |
> |
15 |
> |
16 |
> [snip] |
17 |
> |
18 |
> |
19 |
> >> No, I don't think you should revert the profile change. I understood |
20 |
> >> from your mail than you had not done that yet, and typed accordingly. |
21 |
> >> |
22 |
> >> I think Michael is on the right track with backtrack - set it to |
23 |
> >> something very high like 1000, see if that gets to a solution. |
24 |
> > |
25 |
> > |
26 |
> > I did switch back, but the only way I could do a "successful" update |
27 |
> > was to mask off 5.26 and then it skipped the update and would have |
28 |
> > been successful. If I switch to the new profile, I can do nothing as |
29 |
> > far as perl goes. I will show the output of just trying to emerge |
30 |
> > below, it seems there were many many packages still requiring 5.24. |
31 |
> |
32 |
> No, that's not right. The tree is consistent and portage can figure out |
33 |
> how to get from perl-5.24 to perl-5.26 |
34 |
> |
35 |
> You probably have a difference locally, I would search through |
36 |
> /etc/portage looking for entries that mask some perl modules and peg |
37 |
> them to 5.24 versions. |
38 |
> |
39 |
> Failing that, maybe you have a package installed that depends on a 5.24 |
40 |
> version of some module and this is the ripple effect |
41 |
> |
42 |
> Perhaps run emerge with "--verbose-conflicts" and also "emerge -e world" |
43 |
> and post the results |
44 |
> |
45 |
> |
46 |
> > This is with the new profile and backtrack set to 500. |
47 |
> > |
48 |
> > instances within a single package slot have been pulled |
49 |
> > !!! into the dependency graph, resulting in a slot conflict: |
50 |
> > |
51 |
> > dev-lang/perl:0 |
52 |
> > |
53 |
> > (dev-lang/perl-5.26.1-r1:0/5.26::gentoo, ebuild scheduled for merge) |
54 |
> > pulled in by |
55 |
> > =dev-lang/perl-5.26* required by |
56 |
> > (virtual/perl-ExtUtils-Manifest-1.700.0-r4:0/0::gentoo, installed) |
57 |
> > ^ ^^^^^ |
58 |
> > dev-lang/perl (Argument) |
59 |
> > (and 13 more with the same problems) |
60 |
> > |
61 |
> > (dev-lang/perl-5.24.3:0/5.24::gentoo, installed) pulled in by |
62 |
> > =dev-lang/perl-5.24* required by |
63 |
> > (virtual/perl-Term-ANSIColor-4.40.0-r1:0/0::gentoo, installed) |
64 |
> > ^ ^^^^^ |
65 |
> > dev-lang/perl:0/5.24= required by |
66 |
> > (dev-perl/XML-Twig-3.520.0:0/0::gentoo, installed) |
67 |
> > ^^^^^^^^ |
68 |
> > (and 260 more with the same problems) |
69 |
> > |
70 |
> > NOTE: Use the '--verbose-conflicts' option to display parents omitted |
71 |
> > above |
72 |
> > |
73 |
> > It may be possible to solve this problem by using package.mask to |
74 |
> > prevent one of those packages from being selected. However, it is also |
75 |
> > possible that conflicting dependencies exist such that they are |
76 |
> > impossible to satisfy simultaneously. If such a conflict exists in |
77 |
> > the dependencies of two different packages, then those packages can |
78 |
> > not be installed simultaneously. |
79 |
> > |
80 |
> > For more information, see MASKED PACKAGES section in the emerge man |
81 |
> > page or refer to the Gentoo Handbook. |
82 |
|
83 |
hmmm, nothing masked as far as perl modules, I will look at |
84 |
verbose-conflicts and maybe write down all those modules and start |
85 |
unmerging and see if eventually portage can figure out something -- I |
86 |
don't really want to do that, however I will look at the conflicts |
87 |
and see what I can find. |
88 |
|
89 |
|
90 |
-- |
91 |
Your life is like a penny. You're going to lose it. The question is: |
92 |
How do |
93 |
you spend it? |
94 |
|
95 |
John Covici |
96 |
covici@××××××××××.com |