Re: Bug#653650: ipython: Please depend on "python (>= 2.7) | python-argparse"

2012-01-08 Thread Jakub Wilk

* Ritesh Raj Sarraf , 2012-01-08, 13:08:

argparse was included in python2.7

Please change the argparse dependency to
  python (>= 2.7) | python-argparse

The same change also makes sense for the build dependencies.
This will not install python-argparse needed for the 2.6 variants. The 
only really satisfying option is adding explicit ipython2.6 packages 
which I'm not going to do that as 2.6 will disappear at some point and 
packaging is complex enough as is.


How about using "python (>= 2.7) | python-argparse" in Depends and 
"python-argparse" in Recommends or Suggests?


The current Depends doesn't guarantee that ipython is usable with 
non-default Python version anyway (e.g. you don't depend on 
python2.6, you have little control over versions supported by your 
dependencies, etc.).



It is my opinion that argparse should revert the 2.6 only change


That said, I agree that the argparse 2.6-only change should be reverted.

--
Jakub Wilk


--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120108120009.gb5...@jwilk.net



Re: Bug#653650: ipython: Please depend on "python (>= 2.7) | python-argparse"

2012-01-08 Thread Julian Taylor
On 01/08/2012 01:00 PM, Jakub Wilk wrote:
> 
> 
> The current Depends doesn't guarantee that ipython is usable with
> non-default Python version anyway (e.g. you don't depend on python2.6,
> you have little control over versions supported by your dependencies,
> etc.).

you get a helpful error message when you try the 2.6 script it without
2.6 installed.
I'd have to patch the source to do the same for missing argparse.



signature.asc
Description: OpenPGP digital signature


Re: Comments regarding xen-api_1.3-14_amd64.changes

2012-01-08 Thread Piotr Ożarowski
[Thomas Goirand, 2012-01-08]
> override_dh_python2:
>   dh_python2
>   dh_python2 --skip-private /usr/lib/xcp


override_dh_python2:
dh_python2
dh_python2 /usr/lib/xcp

is the way to go (assuming "xcp" is *not* binary package name, otherwise
extra call is not needed at all). dh_python2 is checking some private
directories by default (see manpage for details) - if you want to use
different options for these directories (f.e. if public modules support
Python >= 2.4 and private ones Python >= 2.6), use --skip-private like
this:

override_dh_python2:
dh_python2 --skip-private
dh_python2 /usr/lib/xcp

(assuming "xcp" is binary package name)
-- 
Piotr Ożarowski Debian GNU/Linux Developer
www.ozarowski.pl  www.griffith.cc   www.debian.org
GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645


-- 
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120108163525.ga23...@piotro.eu



Fwd: (forw) Re: Future of python2.6 in Debian (python-newt)

2012-01-08 Thread Alastair McKinstry
Hi,

Thanks to Christian for forwarding this. python-newt uses a depends line
that generates:

amckinstry@debian:~/deb-packages/newt/newt-0.52.14/debian$ cat
python-newt.substvars
python:Versions=2.6, 2.7
python:Provides=python2.6-newt, python2.7-newt
python:Depends=python2.7 | python2.6, python (>= 2.6), python (<< 2.8),
python (>= 2.6.6-7~)
shlibs:Depends=libc6 (>= 2.1.3), libc6 (>= 2.3.6-6~), libnewt0.52,
libpython2.6 (>= 2.6), libpython2.7 (>= 2.7), libslang2 (>= 2.0.7-1)
misc:Depends=

The ${python:Depends} is fine, but ${shlibs:Depends} generates
dependencies on libpython that are superfluous,
as well as the necessary libslang, libnewt dependencies. I _could_ drop
the ${shlibs:Depends} and replace it with
just 'libnewt0.52', (the libc and libslang dependencies will be pulled
in from it), but I suspect it would be best
to somehow tell debhelper that I don't need libpython*.
Any ideas?

please CC: me in any response as I'm not currently subscribed to
debian-python

regards
Alastair McKinstry


 Original Message 
Subject:(forw) Re: Future of python2.6 in Debian (python-newt)
Date:   Sun, 8 Jan 2012 08:00:05 +0100
From:   Christian PERRIER 
To: mckins...@debian.org



Hi Alastair,

In case you hadn't noticed

- Forwarded message from Axel Beckert  -

Date: Sun, 8 Jan 2012 03:20:01 +0100
From: Axel Beckert 
To: Matthias Klose 
Cc: debian-python@lists.debian.org, Debian Release 

Subject: Re: Future of python2.6 in Debian
Organization: The Debian Project
X-Mailing-List:  archive/latest/50451
X-CRM114-Status: Good  ( pR: 999.99  )

Hi,

JFYI:

Matthias Klose wrote:
> see
> http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=python2.6-removal;users=debian-python@lists.debian.org,
> the only blocker is packaging of zope2.13. feedback from the zope2 packagers 
> is
> outstanding.

There's one issue which is  not listed there but into which I ran into on
i386 recently:

python-newt depends on libpython-2.6 since very recently only and only
on some architectures. Noticed it, because it wants to pull in
python2.6 again. See also http://packages.debian.org/sid/python-newt

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE
  `-|  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120108022001.gc27...@sym.noone.org



 ** CRM114 Whitelisted by: From: Axel Beckert  **

- End forwarded message -

-- 






Re: Fwd: (forw) Re: Future of python2.6 in Debian (python-newt)

2012-01-08 Thread Piotr Ożarowski
[Alastair McKinstry, 2012-01-08]
> The ${python:Depends} is fine, but ${shlibs:Depends} generates
> dependencies on libpython that are superfluous,
> as well as the necessary libslang, libnewt dependencies. I _could_ drop
> the ${shlibs:Depends} and replace it with
> just 'libnewt0.52', (the libc and libslang dependencies will be pulled
> in from it), but I suspect it would be best
> to somehow tell debhelper that I don't need libpython*.
> Any ideas?

from mod-wsgi package:
( for i in 2.4 2.5; do echo libpython$$i 1.0; done ) > debian/shlibs.local
-- 
Piotr Ożarowski Debian GNU/Linux Developer
www.ozarowski.pl  www.griffith.cc   www.debian.org
GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645


-- 
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120108215354.gb23...@piotro.eu