Re: python transition incomplete

2010-09-27 Thread Adam D. Barratt
On Mon, 2010-09-27 at 09:51 +0200, Josselin Mouette wrote: > Le dimanche 26 septembre 2010 à 23:53 +0200, Jakub Wilk a écrit : > > >gnome-python-extras 2.25.3-5 > > python-gda depends on both python2.5 and libpython2.6. > > Fixed in 2.25.3-6. Please unblock. I thought such cases were, according

Re: python transition incomplete

2010-09-29 Thread Adam D. Barratt
On Wed, 2010-09-29 at 09:33 +0200, Josselin Mouette wrote: > Le lundi 27 septembre 2010 à 20:02 +0100, Adam D. Barratt a écrit : > > On Mon, 2010-09-27 at 09:51 +0200, Josselin Mouette wrote: > > > Le dimanche 26 septembre 2010 à 23:53 +0200, Jakub Wilk a écrit : > >

Re: Upload permission for PySide

2010-10-11 Thread Adam D. Barratt
On Sun, 2010-09-26 at 10:46 +0200, Julien Cristau wrote: > On Sat, Sep 11, 2010 at 21:49:33 +0200, Didier 'OdyX' Raboud wrote: > > So from here I see some options (with my opinion in parentheses) > > i) Removing PySide from Squeeze > > (I think it would be sad). > > ii) Keeping the current PyS

Re: Upload permission for PySide

2010-10-12 Thread Adam D. Barratt
On Tue, 2010-10-12 at 10:33 +0200, Didier 'OdyX' Raboud wrote: > I was hard to convince, but now I am: let's remove those 4 from testing. In > order to allow Squeeze users to use PySide, I will probably handle backports. > In > the meantime, new upstream versions will land in unstable. > > This

Re: Bug#623820: Status of python2.5 removal

2011-05-18 Thread Adam D. Barratt
On Wed, May 18, 2011 01:27, Ben Finney wrote: > Luca Falavigna writes: > >> Status update: >> >> The following packages are not available in Wheezy and have longstanding >> RC bugs filed, so they can be safely ignored: > > Can you please list the RC bugs you're referring to? > >> * libopensync-plu

Re: Bug#637892: ITP: python-formalchemy -- auto-generation and customizable form

2011-08-17 Thread Adam D. Barratt
On Wed, 17 Aug 2011 18:18:09 +0800, Liang Guo wrote: On Wed, Aug 17, 2011 at 5:39 PM, Shell Xu wrote: And, I almost finish my job. But which bugnumber should I fill into changelog? The new one or both? Thanks for help. You can close both bug in debian/changelog You can, but you'll just gene