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
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
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
4 matches
Mail list logo