On Tue, 4 Sep 2001, Neil Schemenauer wrote:
> 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
Jérôme Marant wrote:
> Would you please comment on this?
Looks reasonable to me.
Neil
See here:
http://people.debian.org/~nas/woody/
The source packages I have are:
python_2.1.1
python1.5_1.5.2
zope2.3.3
These create the following binary packages:
python-base
python-dev
python-elisp
python-examples
python-gdbm
python-mpz
python-regrte
Hi,
One month ago, I posted this:
http://lists.debian.org/debian-python/2001/debian-python-200108/msg3.html
but I got no reply.
Would you please comment on this?
Thanks.
--
Jérôme Marant <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
Mikael Hedin <[EMAIL PROTECTED]> writes:
[...]
> Why not the exciting name "python"? And confilcts with python-base?
> Then all the module that depend on python-base (xxx) to be either
> upgrader or removed. Am I right?
There's quite a few packages that depend on "python", which is a
virtual pa
On 4 Sep 2001, David Maslen wrote:
> Gregor Hoffleit <[EMAIL PROTECTED]> writes:
> > How does that sound ?
>
> I think it sounds like an awful lot of work. I still don't really
> understand why we keep python1.5, but presumably there are some good
> reasons, and I trust the debian team to have thr
Carey Evans <[EMAIL PROTECTED]> writes:
> Mikael Hedin <[EMAIL PROTECTED]> writes:
>
> [...]
>
> > 6) All packages with files in .../python1.5/ without versioned depends
> > get a critical bug.
>
> Unfortunately, this leaves someone's system broken if they just
> install some Python packages, a
Jérôme Marant wrote:
> Neil Schemenauer <[EMAIL PROTECTED]> writes:
> > Do you know of any? If you can point them out I may be able to help fix
> > them.
>
> Zope 2.3x was the most obvious example. I don't know if python-ldap can
> work with 2.x too. All python packages that provide binary mo
Mikael Hedin <[EMAIL PROTECTED]> writes:
[...]
> 6) All packages with files in .../python1.5/ without versioned depends
> get a critical bug.
Unfortunately, this leaves someone's system broken if they just
install some Python packages, and leave the packages that currently
depend on "python-base
Hi,
from the thread I started, I propose we try this:
1) Every package that depend on python checks if it works with python
2.1.
2) We upload python-base v. 2.1, and most of the packages will have to
make a new upload (depend on python-base (>=2.1 && << 2.2) if anything
installed in .../python2
Neil Schemenauer <[EMAIL PROTECTED]> writes:
> 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 o
Neil Schemenauer <[EMAIL PROTECTED]> writes:
> 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.
I p
12 matches
Mail list logo