public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jacques Montier <jmontier@gmail.com>
To: "gentoo-user@lists.gentoo.org" <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] emerge world problem with one package [solved]
Date: Sun, 26 Oct 2014 21:44:06 +0100	[thread overview]
Message-ID: <CAHVEG0CqTughbsYgd7f7Vz=D5qGavpmay4jgc1di57-TSb1ohw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1265 bytes --]

2014-10-26 19:47 GMT+01:00 Alexander Kapshuk <alexander.kapshuk@gmail.com>:

> On Sun, Oct 26, 2014 at 5:58 PM, Jacques Montier <jmontier@gmail.com>
> wrote:
> > [ebuild  rR   ~] media-gfx/hugin-2014.0.0-r1  USE="python -debug -lapack
> > -sift" LINGUAS="fr -cs -da -de -en_GB -es -eu -fi -hu -it -ja -nl -pl
> -pt_BR
> > -ro -ru -sk -sv -zh_CN -zh_TW" PYTHON_SINGLE_TARGET="python2_7
> (-python3_2)
> > -python3_3 -python3_4" PYTHON_TARGETS="python2_7 python3_3 (-python3_2)
> > -python3_4" 0 kB
> >
> > I don't have any PYTHON_SINGLE_TARGET and PYTHON_TARGETS lines in
> make.conf.
>
> Those are defined in your system profile:
> grep -i '^python_[st].*' /usr/portage/profiles/base/make.defaults
> PYTHON_TARGETS="python2_7 python3_3"
> PYTHON_SINGLE_TARGET="python2_7"
>
> See if this helps, http://forums.gentoo.org/viewtopic-t-949306.html.
>
>

Hello,

Yes Alexander your link helped me !
So i now understand what happened.
I upgraded hugin and his dependency  libpano13 from stable to ~ by setting
these two packages into package.keywords.
Then i (accidently) removed libpano13 from keywords... :-(
That's why i got the "rR" (force to be rebuilt Hugin) each time i ran
emerge -uvDN world.
Now everything is ok !

Thanks a lot to Alexander and Dan !

Regards,

[-- Attachment #2: Type: text/html, Size: 2427 bytes --]

             reply	other threads:[~2014-10-26 20:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-26 20:44 Jacques Montier [this message]
2014-10-26 20:51 ` [gentoo-user] emerge world problem with one package [solved] Alexander Kapshuk

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='CAHVEG0CqTughbsYgd7f7Vz=D5qGavpmay4jgc1di57-TSb1ohw@mail.gmail.com' \
    --to=jmontier@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