1 |
On Fri, 01 Aug 2014 10:07:18 +0200 |
2 |
"J. Roeleveld" <joost@××××××××.org> wrote: |
3 |
|
4 |
> On Friday, August 01, 2014 07:11:59 AM Gevisz wrote: |
5 |
> > On Thu, 31 Jul 2014 20:17:54 +0200 |
6 |
> > |
7 |
> > "J. Roeleveld" <joost@××××××××.org> wrote: |
8 |
> > > On 31 July 2014 16:19:21 CEST, Gevisz <gevisz@×××××.com> wrote: |
9 |
> > > >On Thu, 31 Jul 2014 10:03:09 -0400 |
10 |
> > > > |
11 |
> > > >Alec Ten Harmsel <alec@××××××××××××××.com> wrote: |
12 |
> > > >> I can't comment on a long-term, real, proper solution, but for |
13 |
> > > >> right now |
14 |
> > > >> |
15 |
> > > >> emerge --oneshot dev-perl/XML-Parser |
16 |
> > > >> |
17 |
> > > >> should at least allow you to continue building colord. |
18 |
> > > > |
19 |
> > > >It seems that it helped, but not the suggestions from |
20 |
> > > > |
21 |
> > > > # perl-cleaner --all |
22 |
> > > > |
23 |
> > > >output. |
24 |
> > > > |
25 |
> > > >Thank you. |
26 |
> > > |
27 |
> > > Did you run the commands and then rerun perlcleaner as the output |
28 |
> > > mentions at the end of the text? |
29 |
> > |
30 |
> > No. I did not run perl-cleaner just after those 2 suggested commands |
31 |
> > because I had not noted that demand. So, my complaint that the |
32 |
> > suggested "long-term" solution does not work may be incorrect. |
33 |
> |
34 |
> The claim is incorrect. I did what it said in the output and it |
35 |
> resolved the issue on my systems. |
36 |
> |
37 |
> > However, I run perl-cleaner after |
38 |
> > |
39 |
> > # emerge --oneshot dev-perl/XML-Parser |
40 |
> > # emerge --update --deep --with-bdeps=y --newuse --backtrack=60 |
41 |
> > --ask |
42 |
> world |
43 |
> > # emerge --depclean --ask |
44 |
> > |
45 |
> > So, I hope that the problem was fixed. |
46 |
> |
47 |
> It should be resolved now. |
48 |
> I don't add the "--backtrack" part. |
49 |
> It hasn't been needed for me ever since I started using Gentoo |
50 |
> sometime in 2004. (Not sure when it got introduced?) |
51 |
|
52 |
I am not sure if it was needed this time, but only this option |
53 |
helped me to fix the problem with my previous system update when |
54 |
I deviated a bit from my usual system update routine and got a similar |
55 |
message about blocked packages. |