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