[debian-pyt...@l.d.o added to To and Reply-To, citing whole mail for those who
don't read -devel, me included ]
First of all: thanks Matthias for your work on Python package(s)
[Matthias Klose, 2009-02-16]
Besides the normal pending update of the python version for the
unstable distribution,
Le lundi 16 février 2009 à 22:33 +0100, Matthias Klose a écrit :
current is also useful to only provide a public module for just the default
version. I'm unsure what you mean with when talking about the above mentioned
issue
Is it a joke? If you don’t know what this is about, why are you even
Piotr Oz.arowski schrieb:
- 2.5 is superseded by 2.6; currently there doesn't seem to be
a reason to ship 2.5 and modules for 2.5 with the next stable
release. The upstream 2.5 maintainance branch doesn't see bug
fixes anymore, only security releases will be made from this
Hi Matthias,
thanks for all the work you do. I have one question:
- 3.0/3.1: I do not plan to upload 3.0 to unstable or experimental,
but will prepare 3.1 packages for experimental and upload those
to unstable with the final release or a late release candidate.
The 3.1 release is
Ondrej Certik schrieb:
Hi Matthias,
thanks for all the work you do. I have one question:
- 3.0/3.1: I do not plan to upload 3.0 to unstable or experimental,
but will prepare 3.1 packages for experimental and upload those
to unstable with the final release or a late release candidate.
On Mon, Feb 16, 2009 at 2:15 PM, Matthias Klose d...@debian.org wrote:
Ondrej Certik schrieb:
Hi Matthias,
thanks for all the work you do. I have one question:
- 3.0/3.1: I do not plan to upload 3.0 to unstable or experimental,
but will prepare 3.1 packages for experimental and upload
Hi
[I agree that this should have have been sent also to debian-python]
Dne Mon, 16 Feb 2009 20:33:48 +0100
Matthias Klose d...@cs.tu-berlin.de napsal(a):
- 3.0/3.1: I do not plan to upload 3.0 to unstable or experimental,
but will prepare 3.1 packages for experimental and upload those
2009/2/16 Sandro Tosi mo...@debian.org:
you'd be welcome to so do :) You can find some documentation at [1]
[2] [3], and feel free to ask d-pyt...@l.d.o for clarification or, if
you hang around irc, we're on #debian-python at irc.debian.org.
[1]
Various
---
There are other things which may be worth a look.
- Can you guys please finally sit down and agree on one solution for
handling python modules? I still think that having two (slightly
different) ways of doing this task is not the way to go. I really do
not see technical
Josselin Mouette wrote:
Le lundi 16 février 2009 à 22:33 +0100, Matthias Klose a écrit :
current is also useful to only provide a public module for just the default
version. I'm unsure what you mean with when talking about the above mentioned
issue
Is it a joke? If you don’t know what this
10 matches
Mail list logo
