1 |
On 7/31/21 12:32 AM, William Kenworthy wrote: |
2 |
> |
3 |
> On 31/7/21 4:50 am, Michael Orlitzky wrote: |
4 |
>> On Fri, 2021-07-30 at 07:08 -0400, Michael Orlitzky wrote: |
5 |
>>> On Thu, 2021-07-29 at 20:42 -0600, thelma@×××××××××××.com wrote: |
6 |
>>>> I'm trying to run an upgrade but I got stuck on perl: |
7 |
>>>> |
8 |
>>>> !!! Multiple package instances within a single package slot have been |
9 |
>>>> pulled |
10 |
>>>> !!! into the dependency graph, resulting in a slot conflict: |
11 |
>>>> |
12 |
>>>> dev-lang/perl:0 |
13 |
>>>> |
14 |
>>> |
15 |
>>> Adding --backtrack=100 to emerge fixed this for me, but its |
16 |
>>> effectiveness will depend on how confused your portage is... |
17 |
>>> |
18 |
>> On a few servers, --backtrack=200 is needed... |
19 |
>> |
20 |
>> |
21 |
> |
22 |
> Hi, |
23 |
> |
24 |
> I have been hit by this on a few systems. Try upgrading perl with |
25 |
> --nodeps and then run "perlcleaner --all" then retry emerging any other |
26 |
> packages left finishing with "perlcleaner --all" again. |
27 |
> |
28 |
> |
29 |
> Other than one system with a missing g-cpan ebuild its worked out fine |
30 |
> so far. |
31 |
> |
32 |
> BillK |
33 |
|
34 |
What worked is: |
35 |
root # emerge -uDNavq --with-bdeps=y --backtrack=100 --autounmask-keep-masks=y @world |
36 |
root # perl-cleaner --all |