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