From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] colord failed to upgrade
Date: Fri, 01 Aug 2014 19:14:08 +0200 [thread overview]
Message-ID: <53DBCAE0.1050003@gmail.com> (raw)
In-Reply-To: <52108877.MzkzTK3Ytd@andromeda>
On 01/08/2014 10:07, J. Roeleveld wrote:
> On Friday, August 01, 2014 07:11:59 AM Gevisz wrote:
>
>> On Thu, 31 Jul 2014 20:17:54 +0200
>
>>
>
>> "J. Roeleveld" <joost@antarean.org> wrote:
>
>> > On 31 July 2014 16:19:21 CEST, Gevisz <gevisz@gmail.com> wrote:
>
>> > >On Thu, 31 Jul 2014 10:03:09 -0400
>
>> > >
>
>> > >Alec Ten Harmsel <alec@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?)
s/(Not sure when it got introduced)/$1 or even what it is for?/g
There ya go, fixed that for ya.
This appears to hold true for every Gentoo'er in the universe except <10
people in the magic $I_GROK_PORTAGE group.
I myself am not in that group.
--
Alan McKinnon
alan.mckinnon@gmail.com
next prev parent reply other threads:[~2014-08-01 17:15 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-31 13:29 [gentoo-user] colord failed to upgrade Gevisz
2014-07-31 13:36 ` Alan McKinnon
2014-07-31 13:58 ` Gevisz
2014-07-31 14:03 ` Alec Ten Harmsel
2014-07-31 14:19 ` Gevisz
2014-07-31 18:17 ` J. Roeleveld
2014-08-01 4:11 ` Gevisz
2014-08-01 8:07 ` J. Roeleveld
2014-08-01 8:29 ` Gevisz
2014-08-01 17:14 ` Alan McKinnon [this message]
2014-08-01 20:55 ` J. Roeleveld
2014-07-31 14:19 ` J. Roeleveld
2014-08-01 10:00 ` Peter Humphrey
2014-08-01 11:53 ` J. Roeleveld
2014-08-01 12:05 ` Tanstaafl
2014-08-01 12:42 ` J. Roeleveld
2014-08-01 12:44 ` Tanstaafl
2014-08-01 17:22 ` Alan McKinnon
2014-08-01 21:01 ` J. Roeleveld
2014-08-02 9:39 ` Alan McKinnon
2014-08-01 20:52 ` J. Roeleveld
2014-08-03 2:06 ` [gentoo-user] " walt
2014-08-01 17:19 ` [gentoo-user] " Alan McKinnon
2014-08-01 20:57 ` J. Roeleveld
2014-07-31 14:18 ` J. Roeleveld
2014-07-31 15:19 ` Gevisz
2014-07-31 18:16 ` J. Roeleveld
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53DBCAE0.1050003@gmail.com \
--to=alan.mckinnon@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox