doing evil: "support" 2.3 on a box

2007-02-21 Thread Yaroslav Halchenko
Dear All, Please pardon my ignorance if now I will ask for something silly ;-) ok - we have some python library+extension which was built only for 2.3 (due to reliance on patched sip etc etc). So we keep it that way. Now that etch doesn't support 2.3 I am wondering: since we have now such bette

Re: Bug#411657: Transition from sarge-etch for zope packages

2007-02-21 Thread Fabio Tranchitella
Hi Steve, first of all, thanks for your reply. * 2007-02-21 21:10, Steve Langasek wrote: > > I think that changing the dependency on zope-common to something like: > > Depends: python (>= 2.4) | python2.4, ... > > would do the trick, > > No, this would definitely be wrong. The package either use

Re: Transition from sarge-etch for zope packages

2007-02-21 Thread Steve Langasek
On Wed, Feb 21, 2007 at 12:41:52PM +0100, Fabio Tranchitella wrote: > Hello all, > I need some help to find a fix for #411657. The problem is that sarge > included the zope2.7 package which requires python2.3, but python2.3 will > not be shipped with etch and the current python package conflicts

Re: Bug#411657: Transition from sarge-etch for zope packages

2007-02-21 Thread Jonas Meurer
On 21/02/2007 Fabio Tranchitella wrote: > * 2007-02-21 17:33, Jonas Meurer wrote: > > If i understand it correctly, zope-common should depend on python2.4, > > but not on python (>= 2.4), and use python2.4 directly. > > > > This would avoid an upgrade of the default python package and just > > int

Re: Bug#411657: Transition from sarge-etch for zope packages

2007-02-21 Thread Fabio Tranchitella
* 2007-02-21 17:33, Jonas Meurer wrote: > If i understand it correctly, zope-common should depend on python2.4, > but not on python (>= 2.4), and use python2.4 directly. > > This would avoid an upgrade of the default python package and just > introduce the new python2.4 package. This way, the old

Re: Bug#411657: Transition from sarge-etch for zope packages

2007-02-21 Thread Jonas Meurer
On 21/02/2007 Fabio Tranchitella wrote: > * 2007-02-21 15:17, A Mennucc wrote: > > > > > > Depends: python (>= 2.4) | python2.4, ... > > > > > > would do the trick, leaving the old python package around without removing > > > python2.3, but I'm not even sure and to say the truth I do not understa

Re: Bug#411657: Transition from sarge-etch for zope packages

2007-02-21 Thread A Mennucc
hi I agree : forcing a removal of zope2.7 on upgrade Sarge -> Etch is really a bad idea On Wed, Feb 21, 2007 at 12:41:52PM +0100, Fabio Tranchitella wrote: > I think that changing the dependency on zope-common to something like: > > Depends: python (>= 2.4) | python2.4, ... > > would do the t

Re: Bug#411657: Transition from sarge-etch for zope packages

2007-02-21 Thread Fabio Tranchitella
* 2007-02-21 15:17, A Mennucc wrote: > > > > Depends: python (>= 2.4) | python2.4, ... > > > > would do the trick, leaving the old python package around without removing > > python2.3, but I'm not even sure and to say the truth I do not understand > > why the dependency on python2.4 has been repl

Transition from sarge-etch for zope packages

2007-02-21 Thread Fabio Tranchitella
Hello all, I need some help to find a fix for #411657. The problem is that sarge included the zope2.7 package which requires python2.3, but python2.3 will not be shipped with etch and the current python package conflicts with it. Matthias uploaded zope-common 0.5.31 with the following change: