Re: Packaging python-egenix-mx*

2001-10-28 Thread Donovan Baarda
G'day, On Sun, Oct 28, 2001 at 10:34:05PM +0100, Joel Rosdahl wrote: Hi, I have now finished Debianizing eGenix mx BASE (based on patch done by Federico Di Gregorio, see bug#56): http://www.lemburg.com/files/python/eGenix-mx-Extensions.html The upstream maintainer of the mx

Re: What should we do now?

2001-10-23 Thread Donovan Baarda
On Tue, Oct 23, 2001 at 01:27:22PM +1000, Anthony Towns wrote: On Mon, Oct 22, 2001 at 08:32:33AM -0700, Neil Schemenauer wrote: Anthony Towns wrote: On Mon, Oct 22, 2001 at 10:13:17AM +0200, Gregor Hoffleit wrote: Say, you would install 2.1.2 in /usr/local. How about we just say

Re: What should we do now?

2001-10-23 Thread Donovan Baarda
On Tue, Oct 23, 2001 at 02:42:42PM +0200, Gregor Hoffleit wrote: * Anthony Towns aj@azure.humbug.org.au [011023 09:07]: On Tue, Oct 23, 2001 at 01:31:50AM -0400, David M. Cooke wrote: At some point, Anthony Towns aj@azure.humbug.org.au wrote: [...] Just to make the discussion a little bit

Re: What should we do now?

2001-10-23 Thread Donovan Baarda
On Wed, Oct 24, 2001 at 01:42:12AM +1000, Anthony Towns wrote: On Tue, Oct 23, 2001 at 10:59:45PM +1000, Donovan Baarda wrote: [...] Uh, how many scripts rely on python 1.5? If Debian's main python is 2.1, why should a python 1.5 script remain available? I can't see any reason for this, and I

Re: Debian Python policy Upgrade Path (draft/proposal)

2001-10-21 Thread Donovan Baarda
On Sun, Oct 21, 2001 at 10:27:54AM +1300, Carey Evans wrote: Matthias Klose [EMAIL PROTECTED] writes: [...] exactly. But you see that these packages will break when you try to upgrade. We can't make 2.1 the default right now, because we will _silently_ break packages. Before python can

Re: python upgrade

2001-10-21 Thread Donovan Baarda
[EMAIL PROTECTED] for more info, including pgp key -- #! /bin/sh -e # # postinst script for the Debian python2.1-base package. # Written 1998 by Gregor Hoffleit [EMAIL PROTECTED]. # Modified 2001 by Donovan Baarda [EMAIL PROTECTED

Re: Python upgrade path (draft/proposal)

2001-10-18 Thread Donovan Baarda
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 loong).

Re: Second report: latest python in unstable broke my packages

2001-10-16 Thread Donovan Baarda
Quoting Bruce Sass [EMAIL PROTECTED]: Hi, On 16 Oct 2001, Jérôme Marant wrote: ... I installed both python1.5 and python2.1. And installing both on the same system broke _all_ my python 1.5 packages: this is the alternative issue Perl people have warned us about. I didn't

Re: Python packages in incoming

2001-10-16 Thread Donovan Baarda
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-module_version (depends on python-2.1) ] python-module_version (depends on python and python-2.1-module) Hrm.

Re: (another set of) experimental packages (1.5, 2.1, 2.2a4)

2001-10-07 Thread Donovan Baarda
Quoting Matthias Klose [EMAIL PROTECTED]: Donovan Baarda writes: Some other questions; what happens with other packages that might/might not have installed stuff into /usr/lib/python1.5? Will they break? No. However the priority of the python alternative from 1.5 should greater than

Re: (another set of) experimental packages (1.5, 2.1, 2.2a4)

2001-10-03 Thread Donovan Baarda
G'day, Hope you don't mind me Cc'ing to you guys. Let me know if you don't like it and I'll stop. Quoting Matthias Klose [EMAIL PROTECTED]: [...] Open issue(s): - didn't handle the conversion/recompilation of /usr/local python packages. Some other questions; what happens with other

Re: Debian Python Policy [draft]

2001-10-02 Thread Donovan Baarda
Quoting Neil Schemenauer [EMAIL PROTECTED]: Jim Penny wrote: [...] The python is a small package to create a link from /usr/bin/python2.2 to /usr/bin/python. python-eggs is a dummy package for dependencies (similar to what is done for GCC). When we upgrade Python to 2.2 we have:

Re: Debian Python policy.

2001-10-01 Thread Donovan Baarda
Quoting Neil Schemenauer [EMAIL PROTECTED]: Donovan Baarda wrote: Packages like extension modules _are_ tied to a particular version and hence should be in a python-X.Y-foo package that installs into /usr/lib/pythonX.Y. There would also be an empty package python-foo that simply

Re: Debian Python Policy [draft]

2001-09-30 Thread Donovan Baarda
On Sat, Sep 29, 2001 at 11:10:43PM -0700, Neil Schemenauer wrote: Carey Evans wrote: By way of example, suppose I have a package spam that embeds Python 2.1, and therefore depends on python-2.1. spam also uses the eggs module, and therefore depends on python-eggs, which depends on

Debian Python policy.

2001-09-27 Thread Donovan Baarda
G'day debian-python, Just read the DWN, saw mention of the Python policy, read it, and subscribed to this list to throw in some comments. I note that the policy was posted some time ago, so these comments might be too late. First off, you need to clarify what you are attempting to achieve.

<    1   2