Re: E: dh_python2:146: you most probably have to build extension for python2.5.

2011-03-10 Thread Ludovic Rousseau
2011/3/10 Jakub Wilk : > * Ludovic Rousseau , 2011-03-10, 21:41: My package provides a binary extension so must be compiled for each supported Python versions: 2.5 and 2.6 as of now. >>> >>> ...your new debian/rules does *not* compile extensions for all supported >>> versions. (The o

Re: E: dh_python2:146: you most probably have to build extension for python2.5.

2011-03-10 Thread Barry Warsaw
On Mar 10, 2011, at 10:53 PM, Jakub Wilk wrote: >* Ludovic Rousseau , 2011-03-10, 21:41: My package provides a binary extension so must be compiled for each >>>supported Python versions: 2.5 and 2.6 as of now. >>> >>>...your new debian/rules does *not* compile extensions for all >>support

Re: E: dh_python2:146: you most probably have to build extension for python2.5.

2011-03-10 Thread Jakub Wilk
* Ludovic Rousseau , 2011-03-10, 21:41: My package provides a binary extension so must be compiled for each supported Python versions: 2.5 and 2.6 as of now. ...your new debian/rules does *not* compile extensions for all supported versions. (The old one did.) And dh is not (yet) smart enough

Re: E: dh_python2:146: you most probably have to build extension for python2.5.

2011-03-10 Thread Steve Langasek
On Thu, Mar 10, 2011 at 09:20:56PM +0100, Jan Dittberner wrote: > On Thu, Mar 10, 2011 at 09:03:03PM +0100, Ludovic Rousseau wrote: > > Hello, > > I moved my package pykcs11 [1] from dh_pycentral to dh_python2. The > > conversion was easy. The version in unstable uses dh_python2. > > I also wante

Re: E: dh_python2:146: you most probably have to build extension for python2.5.

2011-03-10 Thread Ludovic Rousseau
2011/3/10 Jakub Wilk : > * Ludovic Rousseau , 2011-03-10, 21:03: >> My package provides a binary extension so must be compiled for each >> supported Python versions: 2.5 and 2.6 as of now. > > ...your new debian/rules does *not* compile extensions for all supported > versions. (The old one did.) A

Re: E: dh_python2:146: you most probably have to build extension for python2.5.

2011-03-10 Thread Ludovic Rousseau
2011/3/10 Jan Dittberner : > On Thu, Mar 10, 2011 at 09:03:03PM +0100, Ludovic Rousseau wrote: >> Hello, >> >> I moved my package pykcs11 [1] from dh_pycentral to dh_python2. The >> conversion was easy. The version in unstable uses dh_python2. >> >> I also wanted to move my debian/rules file from t

Re: ${python:Breaks}

2011-03-10 Thread Barry Warsaw
On Mar 10, 2011, at 04:12 PM, Josselin Mouette wrote: >Le jeudi 10 mars 2011 à 09:00 -0500, Scott Kitterman a écrit : >> The upstream Python position is (I'll paraphrase), "There will not be >> a Python 2.8. If there is a new feature release of Python 2 it will be >> because someone forked it - it

Re: E: dh_python2:146: you most probably have to build extension for python2.5.

2011-03-10 Thread Jakub Wilk
* Ludovic Rousseau , 2011-03-10, 21:03: I also wanted to move my debian/rules file from the "heavy" version [2] to the minimal version using: #!/usr/bin/make -f %: dh $@ --with python2 But I now get a warning and an error (complete log attached): [...] dh_python2 W: dh_python2:94: Py

Re: E: dh_python2:146: you most probably have to build extension for python2.5.

2011-03-10 Thread Jan Dittberner
On Thu, Mar 10, 2011 at 09:03:03PM +0100, Ludovic Rousseau wrote: > Hello, > > I moved my package pykcs11 [1] from dh_pycentral to dh_python2. The > conversion was easy. The version in unstable uses dh_python2. > > I also wanted to move my debian/rules file from the "heavy" version > [2] to the m

Re: ${python:Breaks}

2011-03-10 Thread Barry Warsaw
On Mar 10, 2011, at 12:15 PM, Raphael Hertzog wrote: >On Thu, 10 Mar 2011, Piotr Ożarowski wrote: >> seriously, THERE WILL BE NO NEW PYTHON 2.X VERSION RELEASED UPSTREAM¹, >> we don't have to worry about 2.X transitions when 2.7 will become the >> only supported one. If you don't like Breaks, I wi

E: dh_python2:146: you most probably have to build extension for python2.5.

2011-03-10 Thread Ludovic Rousseau
Hello, I moved my package pykcs11 [1] from dh_pycentral to dh_python2. The conversion was easy. The version in unstable uses dh_python2. I also wanted to move my debian/rules file from the "heavy" version [2] to the minimal version using: #!/usr/bin/make -f %: dh $@ --with python2 But

Re: Switching to git

2011-03-10 Thread Bernd Zeimetz
On 03/06/2011 10:13 PM, Steve Langasek wrote: > On Mon, Mar 07, 2011 at 01:56:59AM +0500, Andrey Rahmatullin wrote: >> On Sun, Mar 06, 2011 at 01:33:45PM -0500, Barry Warsaw wrote: >>> Let me turn that around: why would you *not* want to use a Python based >>> dVCS? >>> >> Because the language of

Re: ${python:Breaks}

2011-03-10 Thread Josselin Mouette
Le jeudi 10 mars 2011 à 09:00 -0500, Scott Kitterman a écrit : > The upstream Python position is (I'll paraphrase), "There will not be > a Python 2.8. If there is a new feature release of Python 2 it will be > because someone forked it - it's Free software, so we can't prevent > that". > > There a

Re: Switching to git

2011-03-10 Thread Bernd Zeimetz
On 03/07/2011 11:19 AM, Nicolas Chauvat wrote: > Being a maintainer of Python packages often means you know Python > which enables you to make mercurial work the way want: write a plugin, > write a script that looks for information in the repo, etc. > > from mercurial import hg, ui > repo = hg

Re: ${python:Breaks}

2011-03-10 Thread Scott Kitterman
On Thursday, March 10, 2011 06:15:01 am Raphael Hertzog wrote: > On Thu, 10 Mar 2011, Piotr Ożarowski wrote: > > seriously, THERE WILL BE NO NEW PYTHON 2.X VERSION RELEASED UPSTREAM¹, > > we don't have to worry about 2.X transitions when 2.7 will become the > > only supported one. If you don't like

Re: ${python:Breaks}

2011-03-10 Thread Raphael Hertzog
On Thu, 10 Mar 2011, Piotr Ożarowski wrote: > seriously, THERE WILL BE NO NEW PYTHON 2.X VERSION RELEASED UPSTREAM¹, > we don't have to worry about 2.X transitions when 2.7 will become the > only supported one. If you don't like Breaks, I will remove it, it > really doesn't matter - that's why at t