public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: JM <jmurray315@googlemail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Problem with python-updater ?
Date: Sun, 27 Mar 2011 20:19:24 +0100	[thread overview]
Message-ID: <AANLkTimbf6XBwkXk8hC3iVgaiYTdWfsB-_Ro4ndHmmSn@mail.gmail.com> (raw)
In-Reply-To: <4D8CC5F1.3010402@gmail.com>

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

I would look at python 3 - I couldn't emerge until only 2.6 was active. I
don't know how but on the new machine I set up, python3 was selected as
active, I set it back to 2.6 and everything was fine.  From the output I can
see there is a version of python 3 active. Maybe a red herring, if so, I
apologies :)

When I had the problem I went on irc and it was suggested that I do a
revdep-rebuild which I did also.



On 25 March 2011 16:42, Dale <rdalek1967@gmail.com> wrote:

> Jacques Montier wrote:
>
>> Hi all,
>>
>> I upgraded python2.6 to python2.7,
>> then i run eselect python set python2.7,
>> then python-updater.
>>
>> Here is the python-updater output :
>>
>> * Starting Python Updater...
>>  * Main active version of Python:  2.7
>>  * Active version of Python 2:     2.7
>>  * Active version of Python 3:     3.1
>>  *   Adding to list: app-emulation/emul-linux-x86-baselibs:0
>>  *   Adding to list: app-emulation/virtualbox-bin:0
>>  *   Adding to list: app-office/libreoffice-bin:0
>>  *   Adding to list: dev-libs/boost:1.42
>>  *     check: manual [Added to list manually, see CHECKS in manpage for
>> more information.]
>>  *   Adding to list: sys-libs/tdb:0
>>  *   Adding to list: x11-libs/vte:0
>>  *     check: manual [Added to list manually, see CHECKS in manpage for
>> more information.]
>>  * emerge -Dv1 --keep-going app-emulation/emul-linux-x86-baselibs:0
>> app-emulation/virtualbox-bin:0 app-office/libreoffice-bin:0
>> dev-libs/boost:1.42 sys-libs/tdb:0 x11-libs/vte:0
>> ...............................
>> Ok, everything emerge fine.
>>
>> If i run python-updater again, then i get exactly the same output as
>> before (emerging emul-linux-x86-baselibs:0, BOOST:1.42, etc...)
>>
>> What's wrong ??
>>
>> Thanks
>>
>>
>>
>
> That seems a bit odd but it depends on what you have installed.  I have KDE
> on mine and it is in the process of rebuilding a little over 50 packages.
>  Most of them are small except for OOo.  Natuarally when anything gets
> updated that monster has to be recompiled.  lol  If you have KDE, I would
> think it would rebuild more than that.  Also, it seems most of mine is
> @system packages.  I would not reboot or logout yet just to be safe.
>
> Anyone notice it wants to rebuild a binary on the OPs system?  Hmmm.
>
> Dale
>
> :-)  :-)
>
>

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

  reply	other threads:[~2011-03-27 19:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-25 16:17 [gentoo-user] Problem with python-updater ? Jacques Montier
2011-03-25 16:42 ` Dale
2011-03-27 19:19   ` JM [this message]
2011-03-25 17:23 ` Roman Zilka
2011-03-25 20:41 ` Neil Bothwick
2011-03-26 13:09   ` Jacques Montier
     [not found] <gAi3E-46i-5@gated-at.bofh.it>
     [not found] ` <gAiZH-5HR-1@gated-at.bofh.it>
2011-03-26  4:14   ` Elaine C. Sharpe

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=AANLkTimbf6XBwkXk8hC3iVgaiYTdWfsB-_Ro4ndHmmSn@mail.gmail.com \
    --to=jmurray315@googlemail.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