Hi, I'm probably missing something big, but here are my thoughts:
Why mess with all these versioned python? Could we not have
python-base (that will be version 2.1 soon), and for the ones who
need, python-base-x.y? And the python-base will be the default/newest
available?
If packages install
Jérôme Marant:
The major question is: do we still need to ship 1.5.2? Unfortunately,
the old python seems to be necessary since some old packages are not
compatible with 2.x versions.
Do you know of any? If you can point them out I may be able to help fix
them.
Scott Moynes wrote:
For
On Tue, Sep 04, 2001 at 06:43:37PM -0400, Scott Moynes wrote:
* Robert Kern ([EMAIL PROTECTED]) wrote:
However, Zope 2.4.0 and up require Python 2.1.
However, Debian only has Zope 2.3.3, although this may soon be
remedied as a new stable version, 2.4.1, was released recently.
This is not
Jim Penny wrote:
This is not all that simple. python2.1 conflicts with zope2.3.x
and python1.5 conflicts with zope2.4.x.
In that case I think it's better to create python1.5 and zope2.3
legacy packages for people who can't upgrade.
Neil
Jim Penny [EMAIL PROTECTED] writes:
This is not all that simple. python2.1 conflicts with zope2.3.x
and python1.5 conflicts with zope2.4.x. Further, it is often
the case that there is a fair amount of internal breakage when
upgrading from one release of zope to another. It is not unusual
Matthias Klose [EMAIL PROTECTED] writes:
...
in June (2.1) and July (2.1.1). Gregor (the python-1.5 and python-2.0
maintainer) has put experimental packages at
http://people.debian.org/~flight/python and was asking for help
regarding the packaging (20010801). Jérôme Marant answered
Gregor Hoffleit [EMAIL PROTECTED] writes:
I'm still alive, I'm not lost ;-)
You're not dead, which is the most important ;-)
And that's the problem where I was stuck.
The dependencies of the current experimental python1.5 packages aren't
good enough to allow an easy upgrade from
7 matches
Mail list logo
