public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Stéphane Guedon" <stephane@22decembre.eu>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] python-2.7 && python-updater
Date: Fri, 25 Mar 2011 20:09:50 +0100	[thread overview]
Message-ID: <201103252009.50877.stephane@22decembre.eu> (raw)
In-Reply-To: <4D8BE1B3.80807@gmail.com>

[-- Attachment #1: Type: Text/Plain, Size: 953 bytes --]

On Friday 25 March 2011 01:28:35 Dale wrote:
> Mark Knecht wrote:
> > One of my machines just saw a python-2.7 update and the ebuild was
> > good enough to remind me to run python-updater, but it didn't suggest
> > that I run eselect python and set the active version to 2.7.
> > 
> > Should this new version python be selected first as the active python
> > 2 version and then run python-updater?
> > 
> > Thanks,
> > Mark
> 
> And if we should set python to 2.7, should we remove python-2.6?  I
> don't think we want to break something, portage in particular.  ;-)
> 
> Dale
> 
> :-)  :-)

I think wicd rely on python 2.6 currently. This is my setup on my laptop ! 
(trying other version break networking with wicd).

-- 
Stéphane Guedon
page web : http://www.22decembre.eu/
carte de visite : http://www.22decembre.eu/downloads/Stephane-Guedon.vcf
clé publique gpg : http://www.22decembre.eu/downloads/Stephane-Guedon.asc

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 316 bytes --]

  parent reply	other threads:[~2011-03-25 19:12 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   ` Stéphane Guedon [this message]
2011-03-25 19:21     ` [gentoo-user] " Grant
2011-03-25 20:38     ` Neil Bothwick
2011-03-26 19:10       ` Mark Knecht
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=201103252009.50877.stephane@22decembre.eu \
    --to=stephane@22decembre.eu \
    --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