| 1 |
On 09/12/2017 17:28, Daniel Frey wrote: |
| 2 |
>> hmmm, nothing masked as far as perl modules, I will look at |
| 3 |
>> verbose-conflicts and maybe write down all those modules and start |
| 4 |
>> unmerging and see if eventually portage can figure out something -- I |
| 5 |
>> don't really want to do that, however I will look at the conflicts |
| 6 |
>> and see what I can find. |
| 7 |
>> |
| 8 |
>> |
| 9 |
> |
| 10 |
> I had a lot of problems with the perl updates as well, and could not get |
| 11 |
> it to resolve. I wasted over an hour trying to resolve it (my poor |
| 12 |
> Celeron would take 5-10 minutes trying to calculate dependencies, and I |
| 13 |
> had to do this 6-7 times.) |
| 14 |
> |
| 15 |
> Note, what I did worked for me and may not work for you, so use this |
| 16 |
> advice at your own risk: I emerged the new perl with --nodeps, and |
| 17 |
> invoked `perl-cleaner all` to fix the mess afterwards. It had everything |
| 18 |
> resolved in < 10 minutes. I didn't suffer any system breakage from using |
| 19 |
> the sledgehammer approach, but others may not be so lucky... so, as I |
| 20 |
> said, try it at your own risk. |
| 21 |
|
| 22 |
that is a very clever solution, one that never occured to me. Ought to |
| 23 |
be at the end of the wiki page, titled "when all else fails, you can |
| 24 |
always do it this way" |
| 25 |
|
| 26 |
It's good advice of last resort, really |
| 27 |
|
| 28 |
|
| 29 |
-- |
| 30 |
Alan McKinnon |
| 31 |
alan.mckinnon@×××××.com |
Archives