Le mercredi 21 février 2007 à 11:12 -0800, Steve Langasek a écrit :
> 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.
This can be the case only if there is a smooth and automated transition
from zope2.7 to
* 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
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
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
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
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
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
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
* 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
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
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
* 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
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:
13 matches
Mail list logo
