Le Mar 13 Juin 2006 20:38, Raphael Hertzog a écrit :
For NMUers, always start by filling a bug report refering to this
announce, register the bug number and your intent to work on it in
the wiki page, do the work, send the patch to the BTS and upload the
package appropriately (using a DELAYED
Hello!
[Tue, 13 Jun 2006] Raphael Hertzog wrote:
If you don't have time to do this now, please reply on
debian-python@lists.debian.org and allow us to make NMU of your packages.
I wont have much time to fix my packages so please feel free to NMU any
of them:
Robert Jordens [EMAIL PROTECTED]
Graham Wilson ([EMAIL PROTECTED]):
What if user will change his default python version (f.e. if his scripts
will use /usr/bin/env python, or simply he will start his script with
pythonX.Y)?
I'm not sure I understand your question. Why would the user change his
default Python version? How
On Tue, Jun 13, 2006 at 11:45:32PM +0200, Matthias Klose wrote:
that is correct. OTOH, each new upload to unstable may add a new
dependency on a newly uploaded library having a more strict dependency
or a new soname. If you build for the version we transition from, and
for the version we
On Wed, Jun 14, 2006 at 11:06:53PM +0200, Piotr Ozarowski wrote:
He can simply change /usr/bin/python symlink (that's very bad, but
it's possible)
To be honest, I don't think it's worth supporting that, since the user
is basically breaking his Python install.
or if he will need some features
On Tue, Jun 13, 2006 at 08:38:57PM +0200, Raphael Hertzog [EMAIL PROTECTED]
wrote:
Hello,
the Python team has agreed on a new policy [1]. As we want to do the
python 2.4 transition now, we need to make sure the packages match the
policy. This will limit the amount of broken packages when
* Mike Hommey ([EMAIL PROTECTED]) [060613 21:29]:
PPS: I'll take care of libxml2 and libxslt as soon as I understand what
I'm supposed to change.
Please don't upload libxml2 until the current version either hits
testing or is RC-buggy.
Thanks.
Cheers,
Andi
--
On Tue, 13 Jun 2006, Mike Hommey wrote:
So please check in the list at the end of this mail if you're concerned,
and if yes, please update your packages following these instructions:
http://wiki.debian.org/DebianPython/NewPolicy
http://people.debian.org/~piman/python-policy/
Maybe I'm
On Tue, Jun 13, 2006 at 09:55:08PM +0200, Raphael Hertzog [EMAIL PROTECTED]
wrote:
When you install some python extensions (.so), it is common that they come
with
associated .py files (modules). Those .py files usually are the same in
/usr/lib/python2.3 and /usr/lib/python2.4, that's why
On Tue, 2006-06-13 at 22:05 +0200, Mike Hommey wrote:
On Tue, Jun 13, 2006 at 09:55:08PM +0200, Raphael Hertzog [EMAIL PROTECTED]
wrote:
When you install some python extensions (.so), it is common that they come
with
associated .py files (modules). Those .py files usually are the same in
On Tue, Jun 13, 2006 at 09:55:08PM +0200, Raphael Hertzog wrote:
OK, then indicate current in XS-Python-Version and support only the
current version in python-xpcom (make sure to generate the provides
field).
Speaking of this, I have a module (python-pyx) that I think is only used
by end-users
Graham Wilson ([EMAIL PROTECTED]):
Speaking of this, I have a module (python-pyx) that I think is only used
by end-users (not applications), so I think it makes sense to only
install modules and extensions for the current version. Does this make
sense?
What if default python version will
Graham Wilson writes:
On Tue, Jun 13, 2006 at 11:22:27PM +0200, Piotr Ozarowski wrote:
Graham Wilson ([EMAIL PROTECTED]):
Speaking of this, I have a module (python-pyx) that I think is only used
by end-users (not applications), so I think it makes sense to only
install modules and
Mike Hommey writes:
On Tue, Jun 13, 2006 at 09:55:08PM +0200, Raphael Hertzog [EMAIL PROTECTED]
wrote:
When you install some python extensions (.so), it is common that they come
with
associated .py files (modules). Those .py files usually are the same in
/usr/lib/python2.3 and
14 matches
Mail list logo
