On Tue, Oct 16, 2001 at 11:39:06PM +0200, Matthias Klose wrote:
> Anthony Towns writes:
> > ] python-2.1_2.1.1
> > ] python_2.1.1 (depends on python-2.1) (does "ln /usr/bin/python{2.1,}")
> > ] python-2.1-_ (depends on python-2.1)
> > ] python-_ (depends on python and python-2.1-)
> > Hrm. That
Quoting Matthias Klose <[EMAIL PROTECTED]>:
> Anthony Towns writes:
> > ] python-2.1_2.1.1
> > ] python_2.1.1 (depends on python-2.1) (does "ln
> /usr/bin/python{2.1,}")
> > ] python-2.1-_ (depends on python-2.1)
> > ] python-_ (depends on python and
> python-2.1-)
> >
> > Hrm. That should be
Anthony Towns writes:
> ] python-2.1_2.1.1
> ] python_2.1.1 (depends on python-2.1) (does "ln /usr/bin/python{2.1,}")
> ] python-2.1-_ (depends on python-2.1)
> ] python-_ (depends on python and python-2.1-)
>
> Hrm. That should be:
>
> Package: python-
> Version:
> Depends
On Sun, Oct 14, 2001 at 10:57:25AM +0200, Matthias Klose wrote:
> Jérôme Marant writes:
> > What about proposal and policy from Neil and his efforts?
> - the proposed packaging scheme doesn't allow smooth upgrades between
> one python version and a next version. compare python-1.5 to libc5
>
Quoting Matthias Klose <[EMAIL PROTECTED]>:
> Donovan Baarda writes:
> > Quoting Matthias Klose <[EMAIL PROTECTED]>:
[...]
> > I don't see how this was such a showstopper. Getting the
> > dependancies right to ensure a clean transition would have been
> > fairly easy.
>
> Then again, why do we us
Donovan Baarda writes:
> Quoting Matthias Klose <[EMAIL PROTECTED]>:
>
> > Jérôme Marant writes:
> > > What about proposal and policy from Neil and his efforts?
> >
> > - the proposed packaging scheme doesn't allow smooth upgrades between
> > one python version and a next version. compare pyt
Quoting Matthias Klose <[EMAIL PROTECTED]>:
> Jérôme Marant writes:
> > What about proposal and policy from Neil and his efforts?
>
> - the proposed packaging scheme doesn't allow smooth upgrades between
> one python version and a next version. compare python-1.5 to libc5
> and python-2.1 t
On 14 Oct 2001, Jérôme Marant wrote:
> Matthias Klose <[EMAIL PROTECTED]> writes:
> > Jérôme Marant writes:
> > > What about proposal and policy from Neil and his efforts?
> >
> > - the proposed packaging scheme doesn't allow smooth upgrades between
> > one python version and a next version. co
Matthias Klose <[EMAIL PROTECTED]> writes:
>
> Reading
> http://lists.debian.org/debian-python/2001/debian-python-200109/msg3.html
> I don't see any response/reaction from Neil on Gregor's last
> proposal. So did he "silently ignore" Gregor's packages? I didn't
> "silently prepared the pack
Jérôme Marant writes:
> Matthias Klose <[EMAIL PROTECTED]> writes:
>
> > Jérôme Marant writes:
> > > What about proposal and policy from Neil and his efforts?
> >
> > - the proposed packaging scheme doesn't allow smooth upgrades between
> > one python version and a next version. compare pytho
Matthias Klose <[EMAIL PROTECTED]> writes:
> Jérôme Marant writes:
> > What about proposal and policy from Neil and his efforts?
>
> - the proposed packaging scheme doesn't allow smooth upgrades between
> one python version and a next version. compare python-1.5 to libc5
> and python-2.1 to
Jérôme Marant writes:
> What about proposal and policy from Neil and his efforts?
- the proposed packaging scheme doesn't allow smooth upgrades between
one python version and a next version. compare python-1.5 to libc5
and python-2.1 to libc6. there was a clear upgrade procedure to do
the
Hi,
I can see some new python packages in incoming.
It seems that they are from Gregor, the official maintainer.
What about proposal and policy from Neil and his efforts?
Cheers,
--
Jérôme Marant <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
CV consultable
13 matches
Mail list logo