public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Gevisz <gevisz@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] colord failed to upgrade
Date: Fri, 1 Aug 2014 11:29:50 +0300	[thread overview]
Message-ID: <53db50a9.2405980a.7022.6c1b@mx.google.com> (raw)
In-Reply-To: <52108877.MzkzTK3Ytd@andromeda>

On Fri, 01 Aug 2014 10:07:18 +0200
"J. Roeleveld" <joost@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" <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?)

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.
  



  reply	other threads:[~2014-08-01  8:32 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 [this message]
2014-08-01 17:14               ` Alan McKinnon
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=53db50a9.2405980a.7022.6c1b@mx.google.com \
    --to=gevisz@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