On Fri, 01 Aug 2014 10:07:18 +0200 "J. Roeleveld" <jo...@antarean.org> wrote:
> On Friday, August 01, 2014 07:11:59 AM Gevisz wrote: > > On Thu, 31 Jul 2014 20:17:54 +0200 > > > > "J. Roeleveld" <jo...@antarean.org> wrote: > > > On 31 July 2014 16:19:21 CEST, Gevisz <gev...@gmail.com> wrote: > > > >On Thu, 31 Jul 2014 10:03:09 -0400 > > > > > > > >Alec Ten Harmsel <a...@alectenharmsel.com> wrote: > > > >> I can't comment on a long-term, real, proper solution, but for > > > >> right now > > > >> > > > >> emerge --oneshot dev-perl/XML-Parser > > > >> > > > >> should at least allow you to continue building colord. > > > > > > > >It seems that it helped, but not the suggestions from > > > > > > > > # perl-cleaner --all > > > > > > > >output. > > > > > > > >Thank you. > > > > > > Did you run the commands and then rerun perlcleaner as the output > > > mentions at the end of the text? > > > > No. I did not run perl-cleaner just after those 2 suggested commands > > because I had not noted that demand. So, my complaint that the > > suggested "long-term" solution does not work may be incorrect. > > The claim is incorrect. I did what it said in the output and it > resolved the issue on my systems. > > > However, I run perl-cleaner after > > > > # emerge --oneshot dev-perl/XML-Parser > > # emerge --update --deep --with-bdeps=y --newuse --backtrack=60 > > --ask > world > > # emerge --depclean --ask > > > > So, I hope that the problem was fixed. > > It should be resolved now. > I don't add the "--backtrack" part. > It hasn't been needed for me ever since I started using Gentoo > sometime in 2004. (Not sure when it got introduced?) I am not sure if it was needed this time, but only this option helped me to fix the problem with my previous system update when I deviated a bit from my usual system update routine and got a similar message about blocked packages.
