Hugo van der Merwe writes:
> > I was just about to post a big explanation...again, when I saw you had
> > figured it out :-)
> >
> > Does anyone think the Python policy need a bit more explanation here? would
> > some "use-cases" help?
>
> I think that would be a good idea, probably. To try to av
> I was just about to post a big explanation...again, when I saw you had
> figured it out :-)
>
> Does anyone think the Python policy need a bit more explanation here? would
> some "use-cases" help?
I think that would be a good idea, probably. To try to avoid having too
many people asking the sam
On Wed, Sep 25, 2002 at 09:40:16PM +1000, Donovan Baarda wrote:
> Does anyone think the Python policy need a bit more explanation here? would
> some "use-cases" help?
Definitely. I am working on the 0.4 version of python-registrar (should
be ready next week), which will enable some more possibiliti
On Tue, Sep 24, 2002 at 07:03:21PM +0200, Hugo van der Merwe wrote:
> > On Tue, Sep 24, 2002 at 12:15:35PM +0200, Hugo van der Merwe wrote:
> > > I see python-numeric and python-numeric-ext have versioned dependencies
> > > on the python meta package. It doesn't look necessary to me, there are
> >
> On Tue, Sep 24, 2002 at 12:15:35PM +0200, Hugo van der Merwe wrote:
> > I see python-numeric and python-numeric-ext have versioned dependencies
> > on the python meta package. It doesn't look necessary to me, there are
> > python2.2-numeric and python2.1-numeric packages, these depend on the
> >
Hugo,
On Tue, Sep 24, 2002 at 12:15:35PM +0200, Hugo van der Merwe wrote:
> I see python-numeric and python-numeric-ext have versioned dependencies
> on the python meta package. It doesn't look necessary to me, there are
> python2.2-numeric and python2.1-numeric packages, these depend on the
> req
ioned, one could upgrade python-numeric before doing a full python
upgrade... (I still have a couple of packages holding my python on 2.1.)
Hugo van der Merwe
Sorry, I'm not on the list, please CC.
On Thu, Oct 18, 2001 at 07:25:04PM +0200, Matthias Klose wrote:
> hmm, seems I've been kicked of the debian lists. anyway, could you
> implement the scripts for your c) proposal? would it be a good idea to
> put the debian directories under CVS control, so we have access to it?
And I thought perha
On Oct 18, Matthias Klose wrote:
>
> > May I suggest a simpler alternative for (b) (or maybe an alternative "c"):
> >
> > Make package python-XXX containing support for both python 1.5 and
> > python 2.1. For each python {1.5,2.1} that is installed, bytecompile
> > the package's .py files on ins
> May I suggest a simpler alternative for (b) (or maybe an alternative "c"):
>
> Make package python-XXX containing support for both python 1.5 and
> python 2.1. For each python {1.5,2.1} that is installed, bytecompile
> the package's .py files on install. Since we use
> /usr/lib/pythonx.y/site
Quoting Matthias Klose <[EMAIL PROTECTED]>:
> With the last python-1.5.2-18.2 NMU we have non-conflicting python1.5,
> 2.0 and 2.1 packages in unstable, not more not less.
>
> Here two proposals, how to go further on. The first proposal is a
> safer proposal (but needs more uploads and needs loon
On Wed, Oct 17, 2001 at 11:06:37PM +0200, Matthias Klose wrote:
> 4) Packages not compatible with python2 need to be uploaded
>to use the python1.5 packages/binary. NMU's should be allowed
>to fix these ...
Possibly, you should reupload them renamed to be "python1.5-foo", as
well, so that
On Oct 17, Matthias Klose wrote:
> With the last python-1.5.2-18.2 NMU we have non-conflicting python1.5,
> 2.0 and 2.1 packages in unstable, not more not less.
>
> Here two proposals, how to go further on. The first proposal is a
> safer proposal (but needs more uploads and needs loong). The seco
With the last python-1.5.2-18.2 NMU we have non-conflicting python1.5,
2.0 and 2.1 packages in unstable, not more not less.
Here two proposals, how to go further on. The first proposal is a
safer proposal (but needs more uploads and needs loong). The second
proposal accepts some breakage during th
Gregor Hoffleit <[EMAIL PROTECTED]> writes:
> The Packages file at
> http://people.debian.org/~flight/python/snapshot/Packages.gz
> contains the first of several trials I made, but to no avail.
> I also tried to make idle-python1.5 "Replace: idle", and/or to "Provide:
> idle", but to no avail:
Hi,
I'm struggling with a simple case of 'What-APT-Does-Is-Not-What-I-mean'
while preparing the dependencies for the Python upgrade:
In potato, we had packages python-base and idle (and a variety of other
python-* packages). Now these packages will be renamed python1.5-base
and
16 matches
Mail list logo
