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