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

2007-02-23 Thread Fabio Tranchitella
* 2007-02-23 11:15, wrote: > hi, Hi! > In the next 4 hours I repeatedly tried to use the migration tool of Plone > to update my Plone site. It turned out that the new version of > exUserFolder 0.50 is completely different , so I removed from the > instance and manually put my old (patched) 0.20

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

2007-02-23 Thread A Mennucc
hi, as I already told, I have a Etch box (amd64) that I installed from scratch ; but I still keep my zope server in a Sarge i386 chroot (using zope 2.7, plone 2.0 (self installed) and other zope products). since the Etch release is near, and this bug is raising the question, I decided to try to p

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

2007-02-22 Thread A Mennucc
things are even worse than I would imagine the migratation of my Plone site from 2.0.5 (=Sarge) to 2.5.1 (=Etch) fails the main problem is that I was using I18NLayer to translate documents in many languages, and this product is not compatible with newer Plone a. -- Andrea Mennucc "The EULA s

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

2007-02-22 Thread A Mennucc
On Wed, Feb 21, 2007 at 11:12:17AM -0800, Steve Langasek wrote: > OTOH, I also don't see why it's important to avoid > removal of zope2.7 on upgrade, it /is/ an obsolete package from the etch > perspective. Because there is not a guaranteed a smooth upgrade between Zope packages, and products ther

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: 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