On Sun, Sep 18, 2011 at 23:58:26 +0200, Luca Falavigna wrote:
> Il 12/09/2011 09:53, Julien Cristau ha scritto:
> > So out of these, I'd expect that libimobiledevice, gobject-introspection
> > and pygobject (and maybe hplip?) need to be fixed, and the rest can
> > hopefully be removed if they stay
Il 12/09/2011 09:53, Julien Cristau ha scritto:
> So out of these, I'd expect that libimobiledevice, gobject-introspection
> and pygobject (and maybe hplip?) need to be fixed, and the rest can
> hopefully be removed if they stay broken.
libimobiledevice, pygobject and hplip are fixed, gobject-intr
On Mon, Sep 12, 2011 at 02:26:28 +0200, Stefano Rivera wrote:
> Hi Luca (2011.09.11_23:38:35_+0200)
> > Would it be possible to draw a map of things still to finish before
> > attempting to switch default to 2.7? There are a couple of resources
> > already ([0] and [1]), are there other useful bit
Hi Luca (2011.09.11_23:38:35_+0200)
> Would it be possible to draw a map of things still to finish before
> attempting to switch default to 2.7? There are a couple of resources
> already ([0] and [1]), are there other useful bits around?
>
> [0] http://bugs.debian.org/622279
> [1] http://release.d
On Sun, Sep 11, 2011 at 11:38 PM, Luca Falavigna wrote:
> Would it be possible to draw a map of things still to finish before
> attempting to switch default to 2.7? There are a couple of resources
> already ([0] and [1]), are there other useful bits around?
The same as the release.d.o bug, but:
Il 11/09/2011 19:24, Jakub Wilk ha scritto:
> To be honest, I don't expect Python 2.6 to go away any time soon. (For
> the simple reason that apparently nobody works on making 2.7 the
> default...)
Would it be possible to draw a map of things still to finish before
attempting to switch default to
6 matches
Mail list logo
