J. Roeleveld <jo...@antarean.org> wrote:
> On Thursday, August 07, 2014 11:33:34 PM gottl...@nyu.edu wrote:
> > I was away for two weeks and now one of my systems cannot be updated due
> > to conflicts. The entire (long) emerge output is at the end of
> > this msg.
> >
> >
> > ------------------ The first conflict is -------------------
>
> <snipped long list of conflicts>
>
> I notice a few perl blockers.
> You could try the following:
>
> # emerge -vuD1 $(qlist -IC 'virtual/perl-*')
> # perl-cleaner --all -v -- -v
>
> And then retry to update world.
> I've been encountering some perl blockages myself, and this cleared it up for
> me.
If I encounter an update of Perl like that, I always do it first and do
the perl-cleaner thing before anything else. Otherwise portage will
crap out soon after the perl update is done because it seems to
automatically use the newer version before perl-cleaner is run.
--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?
John Covici
cov...@ccs.covici.com
