> Simplest I can think of would be to build the extensions inplace
> followed by the call to build_man. Something like:
> override_dh_auto_build:
> dh_auto_build
> python3 setup.py build_ext --inplace
> python3 setup.py build_man
I do not want to build once more the ext
[PICCA Frederic-Emmanuel, 2017-08-01]
> This pacakge contain one module with extensions (the important point)
>
> The new upstream version 0.14.0 provide a build_man target via the setup.py
>
> So in ordert to generate the doc I need to do
>
> python setup.py build_man
>
[...]
> So what should
On 01/08/17 15:15, PICCA Frederic-Emmanuel wrote:
Hello,
I am working on the pyfai package.
This pacakge contain one module with extensions (the important point)
The new upstream version 0.14.0 provide a build_man target via the setup.py
So in ordert to generate the doc I need to do
python
Hello,
I am working on the pyfai package.
This pacakge contain one module with extensions (the important point)
The new upstream version 0.14.0 provide a build_man target via the setup.py
So in ordert to generate the doc I need to do
python setup.py build_man
Now if I look at this target, I
Christopher Hoskin writes:
> What's the plan for moving them to unstable? Are they still using git
> pq rather than git-dpm?
I have updated celery to use git pq. Not done kombu or python-amqp yet
however.
--
Brian May
Great, thanks!
What's the plan for moving them to unstable? Are they still using git
pq rather than git-dpm?
Christopher
On 1 August 2017 at 09:22, Michael Fladischer wrote:
> Hi guys,
>
> On 2017-07-29 12:48, Christopher Hoskin wrote:
>> I was going to look at updating
Hi guys,
On 2017-07-29 12:48, Christopher Hoskin wrote:
> I was going to look at updating vine, kombu and python-ampq this
> weekend, but the upstream tarballs have been signed by a different key
> pair than the one advertised at:
>
>
7 matches
Mail list logo