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

2011-12-30 Thread Ritesh Raj Sarraf
I will be able to look into it only in Jan 2nd week. If there is consensus, please feel free to change it. On Friday, December 30, 2011, Julian Taylor wrote: > tags 653650 + wontfix > thanks > > On 12/30/2011 12:29 AM, Adrian Bunk wrote: > > Source: ipython > > Version: 0.11-2 > > Severity: norma

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

2011-12-30 Thread Ritesh Raj Sarraf
I will be able to look into it only in Jan 2nd week. If there is consensus, please feel free to change it. On Friday, December 30, 2011, Julian Taylor wrote: > tags 653650 + wontfix > thanks > > On 12/30/2011 12:29 AM, Adrian Bunk wrote: > > Source: ipython > > Version: 0.11-2 > > Severity: norma

Mysterious double python dependency

2011-12-30 Thread Nikolaus Rath
Hello, When creating the S3QL package, I somehow get a dependency on both python and python2.7: Depends: python (>= 2.6.6-7~), [...], python2.7 This seems to come from the python:Depends substitution variable: python:Depends=python, python (>= 2.6.6-7~), python (>= 2.6), python-apsw, python-py

Re: Mysterious double python dependency

2011-12-30 Thread Jakub Wilk
* Nikolaus Rath , 2011-12-30, 10:14: When creating the S3QL package, I somehow get a dependency on both python and python2.7: Depends: python (>= 2.6.6-7~), [...], python2.7 They were both generated by dh_python2. And they are both needed to run the postinst script: 1) "python (>= 2.6.6-7~

the logo

2011-12-30 Thread Yaroslav Halchenko
Hi Everyone, I have lingered long enough and had no excuse to make the logo available properly. So, due to PSF regulation we could not use any logo containing the derivative of the official python logo. So, blue yellow Debian-in-a-Python won by voting, I have moved it the source .svg under acces

Re: RFS: python-mplayer

2011-12-30 Thread Olivier Schwander
Le 18 Dec 2011 23:12, Jakub Wilk a écrit: > (I don't intend to sponsor this package.) > > I'd recommend using the upstream name (mplayer.py) for the source > package name. The upstream author seems to change the name of the project nearly at each release but, ok, I'll try to stick to it. Actuall

Re: Mysterious double python dependency

2011-12-30 Thread Nikolaus Rath
Nikolaus Rath writes: > Hello, > > When creating the S3QL package, I somehow get a dependency on both > python and python2.7: > > Depends: python (>= 2.6.6-7~), [...], python2.7 Apparently the culprit is bug #625740. Best, -Nikolaus -- »Time flies like an arrow, fruit flies like a Banan

Re: Mysterious double python dependency

2011-12-30 Thread Jakub Wilk
* Nikolaus Rath , 2011-12-30, 11:32: When creating the S3QL package, I somehow get a dependency on both python and python2.7: Depends: python (>= 2.6.6-7~), [...], python2.7 Apparently the culprit is bug #625740. No, #625740 is about dependency generated for public Python modules, which s