Re: Strange *.so names in pbuild do require tricks for test suite (Was: Trying to run build time tests using nosetest for python-pysam)

2015-07-21 Thread Piotr Ożarowski
[Piotr Ożarowski, 2015-07-21] export PYBUILD_TEST_NOSE=1 if tests are not installed, add also: export PYBUILD_TEST_ARGS={dir}/tests -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint:

Strange *.so names in pbuild do require tricks for test suite (Was: Trying to run build time tests using nosetest for python-pysam)

2015-07-21 Thread Andreas Tille
Hi Bas, On Mon, Jul 20, 2015 at 11:06:22AM +0200, sebastic wrote: On 2015-07-20 10:54, Andreas Tille wrote: unfortunately I did not got any response from Debian Python team and I'm simply lost how to run the tests. Maybe change the dh_auto_test override to something like:

Re: Strange *.so names in pbuild do require tricks for test suite (Was: Trying to run build time tests using nosetest for python-pysam)

2015-07-21 Thread Andreas Tille
Hi Piotr, thanks for your quick help! On Tue, Jul 21, 2015 at 05:29:18PM +0200, Piotr Ożarowski wrote: [Piotr Ożarowski, 2015-07-21] export PYBUILD_TEST_NOSE=1 if tests are not installed, add also: export PYBUILD_TEST_ARGS={dir}/tests While it looks a lot more elegant if I do

Re: Strange *.so names in pbuild do require tricks for test suite (Was: Trying to run build time tests using nosetest for python-pysam)

2015-07-21 Thread Piotr Ożarowski
[1] https://anonscm.debian.org/cgit/debian-med/python-pysam.git/tree/debian/rules just a quick note (.so file names look correct and I didn't check anything further): you can simplyfy debian/rulels by adding this line: export PYBUILD_TEST_NOSE=1 and moving `make -C pysam_data` outside

pybuild and proxies -- could we make prohibition optional?

2015-07-21 Thread Yaroslav Halchenko
talking about this ;-) : $ grep -A3 http_proxy pybuild if 'http_proxy' not in env: env['http_proxy'] = 'http://127.0.0.1:9/' if 'https_proxy' not in env: env['https_proxy'] = 'https://127.0.0.1:9/' which is overall GREAT since now I can drop off all those manual

Re: pybuild and proxies -- could we make prohibition optional?

2015-07-21 Thread Dimitri John Ledkov
On 21 July 2015 at 20:17, Yaroslav Halchenko deb...@onerussian.com wrote: talking about this ;-) : $ grep -A3 http_proxy pybuild if 'http_proxy' not in env: env['http_proxy'] = 'http://127.0.0.1:9/' if 'https_proxy' not in env: env['https_proxy'] =

Re: pybuild and proxies -- could we make prohibition optional?

2015-07-21 Thread Yaroslav Halchenko
As I have mentioned some tools might not be smart about empty values in http_proxy, try e.g. git-annex under such settings On July 21, 2015 4:16:11 PM EDT, Piotr Ożarowski pi...@debian.org wrote: So, long story short... would it be ok if I propose/commit a change like no need, if you want to

Re: pybuild and proxies -- could we make prohibition optional?

2015-07-21 Thread Piotr Ożarowski
So, long story short... would it be ok if I propose/commit a change like no need, if you want to disable it, just set https_proxy to empty string f.e. if you want to enable it only in tests: override_dh_auto_test: http_proxy='' dh_auto_test -- Piotr Ożarowski