public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Cc: Neil Bothwick <neil@digimed.co.uk>
Subject: Re: [gentoo-user] python-2.7 && python-updater
Date: Sat, 26 Mar 2011 12:10:12 -0700	[thread overview]
Message-ID: <AANLkTikhhx_J5d0F3O9J9SR86YRT=tLPUdpZ_UkO=0FD@mail.gmail.com> (raw)
In-Reply-To: <20110325203811.3239e4fc@zaphod.digimed.co.uk>

On Fri, Mar 25, 2011 at 1:38 PM, Neil Bothwick <neil@digimed.co.uk> wrote:
> On Fri, 25 Mar 2011 20:09:50 +0100, Stéphane Guedon wrote:
>
>> I think wicd rely on python 2.6 currently. This is my setup on my
>> laptop ! (trying other version break networking with wicd).
>
> Wicd works fine with 2.7. There was a problem when 2,7 was first
> released, but that was fixed in a Wicd update.
>
>
> --
> Neil Bothwick

I've been through this 2.7 update process on 4 machines now. It seems
on all of my machines the python-updater thing is pretty much always
broken with respect to:

openoffice-bin
boost
emul-linux-x86-baselibs

No matter how many times I rerun things it just wants to keep rebuilding them.

What's weird is that no two machine see exactly the same. Some only
fail with one of those packages, others fail with 2 or 3. Rerunning
phython-updater, or lafilefixer, or revdep-rebuild or removing them
completely and letting emerge -DuN @world reinstall them changes
nothing. They just go on failing the same way.

Waste of time so far...

- Mark



  reply	other threads:[~2011-03-26 19:13 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-25  0:11 [gentoo-user] python-2.7 && python-updater Mark Knecht
2011-03-25  0:28 ` Dale
2011-03-25  3:42   ` Amankwah
2011-03-25  4:48   ` Paul Hartman
2011-03-25  9:37     ` Dale
2011-03-25  9:50       ` Neil Bothwick
2011-03-25 13:56         ` Mark Knecht
2011-03-25 14:26           ` Neil Bothwick
2011-03-25 18:14             ` [gentoo-user] humor: " James
2011-03-25 14:33           ` [gentoo-user] " Roman Zilka
2011-03-25 16:44             ` Dale
2011-03-25 14:33       ` Paul Hartman
2011-03-25 16:46         ` Dale
2011-03-28 13:22     ` KH
2011-03-28 15:02       ` Mark Knecht
2011-03-28 15:41       ` Roman Zilka
2011-03-29  8:26         ` KH
2011-03-25 13:02   ` [gentoo-user] " Simon Siemonsma
2011-03-25 16:50     ` Dale
2011-03-25 19:09   ` [gentoo-user] " Stéphane Guedon
2011-03-25 19:21     ` Grant
2011-03-25 20:38     ` Neil Bothwick
2011-03-26 19:10       ` Mark Knecht [this message]
2011-03-26 19:22         ` Mick
2011-03-26 19:56           ` Mark Knecht
2011-03-26 20:36             ` Bill Longman
2011-03-26 20:53               ` Mark Knecht
2011-03-26 21:12                 ` Mick
2011-03-26 21:16         ` Neil Bothwick
2011-03-26 21:33           ` Mark Knecht
2011-03-26 23:06             ` Adam Carter
2011-03-27  0:44             ` Neil Bothwick
2011-03-27 15:26               ` Mark Knecht
2011-03-27 15:47                 ` Jacques Montier
2011-03-27 19:25                 ` Neil Bothwick
2011-03-27 19:50                   ` Mark Knecht
2011-03-27 20:05                     ` Neil Bothwick
2011-03-28  0:45                       ` Adam Carter

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='AANLkTikhhx_J5d0F3O9J9SR86YRT=tLPUdpZ_UkO=0FD@mail.gmail.com' \
    --to=markknecht@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    --cc=neil@digimed.co.uk \
    /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