* Piotr Ożarowski , 2011-03-11, 10:15:
But I now get a warning and an error (complete log attached):
[...]
dh_python2
W: dh_python2:94: Python 2.6 should install files in
/usr/lib/python2.6/dist-packages/. Did you forget
"--install-layout=deb"?
E: dh_python2:146: you most probably have to build
Hi Piotr (2011.03.11_11:15:33_+0200)
> BTW: dh_python2 from experimental, when invoked with verbose option
> (DH_VERBOSE=1 or --verbose/-v) will print this message:
>
> | possible solutions are: building for all supported Python versions
> | (`pyversions -vr`); adjusting X-Python-Version field; pa
[Ludovic Rousseau, 2011-03-10]
> But I now get a warning and an error (complete log attached):
> [...]
>dh_python2
> W: dh_python2:94: Python 2.6 should install files in
> /usr/lib/python2.6/dist-packages/. Did you forget
> "--install-layout=deb"?
> E: dh_python2:146: you most probably have to
Hi
Dne Thu, 10 Mar 2011 17:08:41 -0500
Barry Warsaw napsal(a):
> On Mar 10, 2011, at 10:53 PM, Jakub Wilk wrote:
> >The upstream tarball contains both setup.py and Makefile. In such a case dh
> >uses Makefile-based build system. And then, it cannot possibly know that the
> >Makefile has anything
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
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
* 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
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
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
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
* 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
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
12 matches
Mail list logo
