Bug#915638: bloscpack: FTBFS on i386: FAIL: test_numpy_io.test_itemsize_chunk_size_mismatch

2018-12-05 Thread Daniel Stender
Package: bloscpack
Version: 0.15.0-1
Severity: serious
Justification: fails to build from source

Building on i386 there are two test failures:


==
FAIL: test_numpy_io.test_itemsize_chunk_size_mismatch(, , array([  0,   1,   2,   3,   4,   5,   6,   7,   8,   9,  10,  
11,  12,
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
AssertionError: ChunkSizeTypeSizeMismatch not raised by pack_ndarray_str

==
FAIL: test_numpy_io.test_itemsize_chunk_size_mismatch(, , array([  0,   1,   2,   3,   4,   5,   6,   7,   8,   9,  10,  
11,  12,
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
AssertionError: ChunkSizeTypeSizeMismatch not raised by pack_ndarray_str

--
Ran 582 tests in 7.203s

FAILED (failures=2)


DS

-- System Information:
Debian Release: 9.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages bloscpack depends on:
ii  python33.5.3-1
ii  python3-blosc  1.4.4+ds1-3
ii  python3-numpy  1:1.12.1-3
ii  python3-six1.10.0-3

bloscpack recommends no packages.

bloscpack suggests no packages.

-- no debconf information



Bug#889297: debops: New upstream release v0.6.0

2018-12-02 Thread Daniel Stender

I've begun to work on updating the package to 0.8.0, but I have given up now.

There are dozens over dozens of separately licensed templated config files 
included in the
roles. Researching the new ones and registering them properly in deb/copyright 
like I did
for the debops-playbooks package takes *a lot* of time. If somebody wants to 
jump on,
please be my guest.

DS

--
4096R/DF5182C8 (sten...@debian.org)
http://www.danielstender.com/



Bug#897757: gamera: ftbfs with GCC-8

2018-08-11 Thread Daniel Stender

Related to this was: https://bugs.debian.org/766740

Thanks for reporting,
DS

--
4096R/DF5182C8 (sten...@debian.org)
http://www.danielstender.com/



Bug#893403: afl: Please use llvm-defaults (or at least

2018-08-08 Thread Daniel Stender

AFL on clang/llvm 6.0 currently fails:


[+] All set and ready to build.
clang-6.0  -Wall -D_FORTIFY_SOURCE=2 -g -Wno-pointer-sign -DAFL_PATH=\"/usr/lib/afl\" 
-DBIN_PATH=\"/usr/bin\" -DVERSION=\"2.52b\"  afl-clang-fast.c -o ../afl-clang-fast 
-Wl,-z,relro -Wl,-z,now
ln -sf afl-clang-fast ../afl-clang-fast++
clang++-6.0 `llvm-config-6.0 --cxxflags` -fno-rtti -fpic  -Wall -D_FORTIFY_SOURCE=2 -g 
-Wno-pointer-sign -DVERSION=\"2.52b\" -Wno-variadic-macros -shared 
afl-llvm-pass.so.cc -o ../afl-llvm-pass.so `llvm-config-6.0 --ldflags` -Wl,-z,relro 
-Wl,-z,now
warning: unknown warning option '-Wno-maybe-uninitialized'; did you mean 
'-Wno-uninitialized'? [-Wunknown-warning-option]
1 warning generated.
clang-6.0  -Wall -D_FORTIFY_SOURCE=2 -g -Wno-pointer-sign -DAFL_PATH=\"/usr/lib/afl\" 
-DBIN_PATH=\"/usr/bin\" -DVERSION=\"2.52b\"  -fPIC -c afl-llvm-rt.o.c -o ../afl-llvm-rt.o
[*] Building 32-bit variant of the runtime (-m32)... failed (that's fine)
[*] Building 64-bit variant of the runtime (-m64)... success!
[*] Testing the CC wrapper and instrumentation output...
unset AFL_USE_ASAN AFL_USE_MSAN AFL_INST_RATIO; AFL_QUIET=1 AFL_PATH=. AFL_CC=clang-6.0 ../afl-clang-fast  
-Wall -D_FORTIFY_SOURCE=2 -g -Wno-pointer-sign -DAFL_PATH=\"/usr/lib/afl\" 
-DBIN_PATH=\"/usr/bin\" -DVERSION=\"2.52b\"  ../test-instr.c -o test-instr -Wl,-z,relro 
-Wl,-z,now
clang: error: unable to execute command: Segmentation fault
clang: error: clang frontend command failed due to signal (use -v to see 
invocation)
clang version 6.0.1-2 (tags/RELEASE_601/final)
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
clang: note: diagnostic msg: PLEASE submit a bug report to 
http://llvm.org/bugs/ and include the crash backtrace, preprocessed source, and 
associated run script.
clang: error: unable to execute command: Segmentation fault
clang: note: diagnostic msg: Error generating preprocessed source(s).
make[2]: *** [Makefile:98: test_build] Error 254
make[2]: Leaving directory '/<>/llvm_mode'
make[1]: *** [debian/rules:30: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:24: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2


Unfortunately, 5.0 also:


[+] All set and ready to build.
clang-5.0  -Wall -D_FORTIFY_SOURCE=2 -g -Wno-pointer-sign -DAFL_PATH=\"/usr/lib/afl\" 
-DBIN_PATH=\"/usr/bin\" -DVERSION=\"2.52b\"  afl-clang-fast.c -o ../afl-clang-fast 
-Wl,-z,relro -Wl,-z,now
ln -sf afl-clang-fast ../afl-clang-fast++
clang++-5.0 `llvm-config-5.0 --cxxflags` -fno-rtti -fpic  -Wall -D_FORTIFY_SOURCE=2 -g 
-Wno-pointer-sign -DVERSION=\"2.52b\" -Wno-variadic-macros -shared 
afl-llvm-pass.so.cc -o ../afl-llvm-pass.so `llvm-config-5.0 --ldflags` -Wl,-z,relro 
-Wl,-z,now
warning: unknown warning option '-Wno-maybe-uninitialized'; did you mean 
'-Wno-uninitialized'? [-Wunknown-warning-option]
1 warning generated.
clang-5.0  -Wall -D_FORTIFY_SOURCE=2 -g -Wno-pointer-sign -DAFL_PATH=\"/usr/lib/afl\" 
-DBIN_PATH=\"/usr/bin\" -DVERSION=\"2.52b\"  -fPIC -c afl-llvm-rt.o.c -o ../afl-llvm-rt.o
[*] Building 32-bit variant of the runtime (-m32)... failed (that's fine)
[*] Building 64-bit variant of the runtime (-m64)... success!
[*] Testing the CC wrapper and instrumentation output...
unset AFL_USE_ASAN AFL_USE_MSAN AFL_INST_RATIO; AFL_QUIET=1 AFL_PATH=. AFL_CC=clang-5.0 ../afl-clang-fast  
-Wall -D_FORTIFY_SOURCE=2 -g -Wno-pointer-sign -DAFL_PATH=\"/usr/lib/afl\" 
-DBIN_PATH=\"/usr/bin\" -DVERSION=\"2.52b\"  ../test-instr.c -o test-instr -Wl,-z,relro 
-Wl,-z,now
clang: error: unable to execute command: Segmentation fault
clang: error: clang frontend command failed due to signal (use -v to see 
invocation)
clang version 5.0.2-2 (tags/RELEASE_502/final)
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
clang: note: diagnostic msg: PLEASE submit a bug report to 
http://llvm.org/bugs/ and include the crash backtrace, preprocessed source, and 
associated run script.
clang: error: unable to execute command: Segmentation fault
clang: note: diagnostic msg: Error generating preprocessed source(s).
make[2]: *** [Makefile:98: test_build] Error 254
make[2]: Leaving directory '/<>/llvm_mode'
make[1]: *** [debian/rules:30: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:24: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2


DS

--
4096R/DF5182C8 (sten...@debian.org)
http://www.danielstender.com/



Bug#892741: llvmlite: FTBFS on mips64el - testsuite segfaults

2018-05-06 Thread Daniel Stender
On 05/06/2018 08:56 PM, Adrian Bunk wrote:
> Control: severity -1 serious
> 
> On Sat, May 05, 2018 at 05:58:21PM +0200, Daniel Stender wrote:
>> Control: severity -1 important
>>
>> I'm lowering the severity of this bug report now to unblock the migration to 
>> testing.
> 
> The failed mips64el build does block testing migration in any case:
> https://tracker.debian.org/pkg/llvmlite

#898002

> The easiest way forward might be going from 5.0 to 6.0?

#898004
 
>> DS
> 
> cu
> Adrian

DS

-- 
4096R/DF5182C8 (sten...@debian.org)
http://www.danielstender.com/



Bug#892741: llvmlite: FTBFS on mips64el - testsuite segfaults

2018-05-05 Thread Daniel Stender
Control: severity -1 important

I'm lowering the severity of this bug report now to unblock the migration to 
testing.

DS

-- 
4096R/DF5182C8 (sten...@debian.org)
http://www.danielstender.com/



Bug#897251: pdf2djvu: FAIL: test-1px-font.test.test

2018-04-30 Thread Daniel Stender
Package: pdf2djvu
Version: 0.9.8-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

A recent rebuild revealed this problem:


==
FAIL: test-1px-font.test.test
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File "/<>/tests/test-1px-font.py", line 25, in test
self.pdf2djvu().assert_()
  File "/<>/tests/tools.py", line 143, in assert_
assert_multi_line_equal(self.stderr, stderr)
AssertionError: 'Unable to revert mtime: /usr/local/share/fonts\n' != ''
- Unable to revert mtime: /usr/local/share/fonts

 >> begin captured stdout << -
$ ../pdf2djvu -q /<>/tests/test-1px-font.pdf -o 
/<>/tests/test-1px-font.djvu

- >> end captured stdout << --

--
Ran 84 tests in 7.662s


Thanks,
DS

-- System Information:
Debian Release: 9.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-6-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages pdf2djvu depends on:
ii  djvulibre-bin   3.5.27.1-7
ii  libc6   2.24-11+deb9u3
ii  libdjvulibre21  3.5.27.1-7
ii  libexiv2-14 0.25-3.1
ii  libgcc1 1:6.3.0-18+deb9u1
ii  libgomp16.3.0-18+deb9u1
ii  libgraphicsmagick++-q16-12  1.3.25-8
ii  libgraphicsmagick-q16-3 1.3.25-8
ii  libpoppler640.48.0-2+deb9u2
ii  libstdc++6  6.3.0-18+deb9u1
ii  libuuid12.29.2-1+deb9u1

pdf2djvu recommends no packages.

Versions of packages pdf2djvu suggests:
ii  poppler-data  0.4.7-8

-- no debconf information



Bug#895618: FTBFS: the instrumentation does not seem to be behaving correctly

2018-04-13 Thread Daniel Stender
Source: afl
Version: 2.52b-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

AFL currently FTBFS:


cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -D_FORTIFY_SOURCE=2 -g -Wno-pointer-sign 
-DAFL_PATH=\"/usr/lib/afl\" -DDOC_PATH=\"/usr/share/doc/afl-doc/docs\" 
-DBIN_PATH=\"/usr/bin\" afl-analyze.c -o afl-analyze -Wl,-z,relro -Wl,-z,now 
-ldl
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -D_FORTIFY_SOURCE=2 -g -Wno-pointer-sign 
-DAFL_PATH=\"/usr/lib/afl\" -DDOC_PATH=\"/usr/share/doc/afl-doc/docs\" 
-DBIN_PATH=\"/usr/bin\" afl-as.c -o afl-as -Wl,-z,relro -Wl,-z,now -ldl
ln -sf afl-as as
[*] Testing the CC wrapper and instrumentation output...
unset AFL_USE_ASAN AFL_USE_MSAN; AFL_QUIET=1 AFL_INST_RATIO=100 AFL_PATH=. 
./afl-gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -D_FORTIFY_SOURCE=2 -g -Wno-pointer-sign 
-DAFL_PATH=\"/usr/lib/afl\" -DDOC_PATH=\"/usr/share/doc/afl-doc/docs\" 
-DBIN_PATH=\"/usr/bin\" test-instr.c -o test-instr -Wl,-z,relro -Wl,-z,now -ldl
echo 0 | ./afl-showmap -m none -q -o .test-instr0 ./test-instr
echo 1 | ./afl-showmap -m none -q -o .test-instr1 ./test-instr

Oops, the instrumentation does not seem to be behaving correctly!

Please ping  to troubleshoot the issue.

make[2]: *** [Makefile:95: test_build] Error 1
make[2]: Leaving directory '/<>'
make[1]: *** [debian/rules:27: override_dh_auto_build] Error 2


DS

-- System Information:
Debian Release: 9.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-6-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)



Bug#893273: bcolz: FTBFS and Debci failure

2018-03-20 Thread Daniel Stender

A couple of failures like this also with 1.1.2/blosc 1.14.2:


==
FAIL: test01b (bcolz.tests.test_carray.bloscFiltersTest)
Testing all available filters in big arrays (bcolz.defaults)
--
Traceback (most recent call last):
  File "bcolz/tests/test_carray.py", line 2322, in test01b
"carray does not seem to compress at all")
AssertionError: carray does not seem to compress at all

==
FAIL: test01c (bcolz.tests.test_carray.bloscFiltersTest)
Testing all available filters in big arrays (context)
--
Traceback (most recent call last):
  File "bcolz/tests/test_carray.py", line 2344, in test01c
self.assertTrue(bcolz.defaults.cparams['shuffle'] == bcolz.SHUFFLE)
AssertionError: False is not true

==
FAIL: test01b (bcolz.tests.test_carray.filtersDiskTest)
Testing all available filters in big arrays (bcolz.defaults)
--
Traceback (most recent call last):
  File "bcolz/tests/test_carray.py", line 2322, in test01b
"carray does not seem to compress at all")
AssertionError: carray does not seem to compress at all

==
FAIL: test01c (bcolz.tests.test_carray.filtersDiskTest)
Testing all available filters in big arrays (context)
--
Traceback (most recent call last):
  File "bcolz/tests/test_carray.py", line 2344, in test01c
self.assertTrue(bcolz.defaults.cparams['shuffle'] == bcolz.SHUFFLE)
AssertionError: False is not true

==
FAIL: test01a (bcolz.tests.test_carray.filtersMemoryTest)
Testing all available filters in big arrays (setdefaults)
--
Traceback (most recent call last):
  File "bcolz/tests/test_carray.py", line 2302, in test01a
"carray does not seem to compress at all")
AssertionError: carray does not seem to compress at all

==
FAIL: test01b (bcolz.tests.test_carray.filtersMemoryTest)
Testing all available filters in big arrays (bcolz.defaults)
--
Traceback (most recent call last):
  File "bcolz/tests/test_carray.py", line 2322, in test01b
"carray does not seem to compress at all")
AssertionError: carray does not seem to compress at all

==
FAIL: test01c (bcolz.tests.test_carray.filtersMemoryTest)
Testing all available filters in big arrays (context)
--
Traceback (most recent call last):
  File "bcolz/tests/test_carray.py", line 2344, in test01c
self.assertTrue(bcolz.defaults.cparams['shuffle'] == bcolz.SHUFFLE)
AssertionError: False is not true

==
FAIL: test01 (bcolz.tests.test_carray.miscDiskTest)
Testing __sizeof__() (big carrays)
--
Traceback (most recent call last):
  File "bcolz/tests/test_carray.py", line 639, in test01
"carray does not seem to compress at all")
AssertionError: carray does not seem to compress at all

==
FAIL: test01 (bcolz.tests.test_carray.miscMemoryTest)
Testing __sizeof__() (big carrays)
--
Traceback (most recent call last):
  File "bcolz/tests/test_carray.py", line 639, in test01
"carray does not seem to compress at all")
AssertionError: carray does not seem to compress at all

==
FAIL: test_repr_disk_array_append (bcolz.tests.test_carray.reprDiskTest)
--
Traceback (most recent call last):
  File "bcolz/tests/test_carray.py", line 2430, in test_repr_disk_array_append
self.assertEqual(expected, repr(y))
AssertionError: "carray((0,), float64)\n  nbytes := 0; cbytes := 16.00 KB; ratio: 0.00\n  
cparams := cparams(clevel=5, shuffle=1, cname='blosclz', quantize=0)\n  chunklen := 2048; 
chunksize: 16384; blocksize: 0\n  rootdir := '/tmp/bcolz-reprDiskTestDqkqDw'\n  mode:= 
'a'\n[]" != "carray((0,), float64)\n  nbytes := 0; cbytes := 16.00 KB; ratio: 0.00\n  
cparams := cparams(clevel=9, shuffle=0, cname='blosclz', quantize=0)\n  chunklen := 2048; 
chunksize: 16384; blocksize: 0\n  rootdir := 

Bug#892741: llvmlite: FTBFS on mips64el - testsuite segfaults

2018-03-12 Thread Daniel Stender

On 03/12/2018 02:03 PM, James Cowgill wrote:

Source: llvmlite
Version: 0.22.0-1
Severity: serious
Tags: sid buster

Hi,

llvmlite FTBFS on mips64el with this segmentation fault:

debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
PYBUILD_SYSTEM=custom PYBUILD_TEST_ARGS="{interpreter} -m unittest discover -v" 
dh_auto_test
I: pybuild base:184: python2.7 -m unittest discover -v
test_function_cfg_on_llvm_value (llvmlite.tests.test_binding.TestAnalysis) ... 
ok
test_get_function_cfg_on_ir (llvmlite.tests.test_binding.TestAnalysis) ... ok
test_linux (llvmlite.tests.test_binding.TestDependencies) ... skipped 
'Distribution-specific test'
test_bad_library (llvmlite.tests.test_binding.TestDylib) ... ok
test_libm (llvmlite.tests.test_binding.TestDylib) ... ok
test_close (llvmlite.tests.test_binding.TestFunctionPassManager) ... ok
test_initfini (llvmlite.tests.test_binding.TestFunctionPassManager) ... ok
test_run (llvmlite.tests.test_binding.TestFunctionPassManager) ... ok
test_add_module (llvmlite.tests.test_binding.TestGlobalConstructors) ... ok
test_add_module_lifetime (llvmlite.tests.test_binding.TestGlobalConstructors) 
... ok
test_add_module_lifetime2 (llvmlite.tests.test_binding.TestGlobalConstructors) 
... ok
test_close (llvmlite.tests.test_binding.TestGlobalConstructors) ... ok
test_emit_assembly (llvmlite.tests.test_binding.TestGlobalConstructors)
Test TargetMachineRef.emit_assembly() ... ok
test_emit_object (llvmlite.tests.test_binding.TestGlobalConstructors)
Test TargetMachineRef.emit_object() ... ok
test_global_ctors_dtors (llvmlite.tests.test_binding.TestGlobalConstructors) 
... Segmentation fault
E: pybuild pybuild:283: test: plugin custom failed with: exit code=139: 
python2.7 -m unittest discover -v
dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
make[1]: *** [debian/rules:11: override_dh_auto_test] Error 25


I did a bit of investigation and I'm fairly certain this is an LLVM bug
which was fixed in LLVM 6 (although I'm not sure what commit fixes it).
Since LLVM 6 has now been released, I suspect you will be upgrading soon
so I have not tried to backport anything to LLVM 5 at this time.

James


Thanks for checking that over. It appears current LLVMlite doesn't support later
versions of LLVM but no problem it could be removed until it builds again in 
the future.

DS

--
4096R/DF5182C8 (sten...@debian.org)
http://www.danielstender.com/



Bug#892109: pdf2djvu FTBFS with libpoppler-dev 0.62.0-2

2018-03-06 Thread Daniel Stender

Please hang on, I'll update this shortly.

DS

--
4096R/DF5182C8 (sten...@debian.org)
http://www.danielstender.com/



Bug#889297: debops: New upstream release v0.6.0

2018-02-03 Thread Daniel Stender
On 02/03/2018 02:49 PM, Frans van Berckel wrote:
> Package: debops
> Version: 0.4.3-1
> Severity: serious
> 
> There a new upstream version v0.6.0, in Github releases available.
> 
> https://github.com/debops/debops/releases
> 
> If i am well, this one doesn't depends on the debops-playbooks package
> any more, as spoked about in debbug 880102.
> 
> RM: debops-playbooks/experimental -- ROM; not needed anymore
> https://bugs.debian.org/880102
> 
> But there a problem with this old one. Check debbug 880102 
> 
> debops: Uninstallable due to debops-playbooks removal
> https://bugs.debian.org/884639
> 
> So please, are you willing to update Debian VCS / Git? Good to know
> v1.0.0 is planned for spring 2018.
> 
> Thanks,
> 
> Frans van Berckel

Thanks for posting this bug report. The package update is coming up in the next 
weeks.

DS

-- 
4096R/DF5182C8 (sten...@debian.org)
http://www.danielstender.com/



Bug#884432: pytest-httpbin: test_httpbin_accepts_lots_of_get_requests_in_single_session FAILED

2017-12-15 Thread Daniel Stender
Source: pytest-httpbin
Version: 0.2.3-1
Severity: serious
Justification: fails to build from source

pytest-httpbin currently FTBFS:

tests/test_httpbin.py::test_httpbin_accepts_lots_of_get_requests_in_single_session
 FAILED

=== FAILURES ===
_ test_httpbin_accepts_lots_of_get_requests_in_single_session __

self = 
func =  at 0x7f15929881b8>, when = 'call'

def __init__(self, func, when):
#: context of invocation: one of "setup", "call",
#: "teardown", "memocollect"
self.when = when
self.start = time()
try:
>   self.result = func()

/usr/lib/python2.7/dist-packages/_pytest/runner.py:196: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib/python2.7/dist-packages/_pytest/runner.py:182: in 
return CallInfo(lambda: ihook(item=item, **kwds), when=when)
/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py:745: in 
__call__
return self._hookexec(self, self._nonwrappers + self._wrappers, kwargs)
/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py:339: in 
_hookexec
return self._inner_hookexec(hook, methods, kwargs)
/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py:334: in 

_MultiCall(methods, kwargs, hook.spec_opts).execute()
/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py:613: in 
execute
return _wrapped_call(hook_impl.function(*args), self.execute)
/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py:250: in 
_wrapped_call
wrap_controller.send(call_outcome)
/usr/lib/python2.7/dist-packages/_pytest/capture.py:139: in pytest_runtest_call
self.suspendcapture_item(item, "call")
/usr/lib/python2.7/dist-packages/_pytest/capture.py:156: in suspendcapture_item
out, err = self.suspendcapture(in_=in_)
/usr/lib/python2.7/dist-packages/_pytest/capture.py:97: in suspendcapture
outerr = cap.readouterr()
/usr/lib/python2.7/dist-packages/_pytest/capture.py:327: in readouterr
self.err.snap() if self.err is not None else "")
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = 

def snap(self):
f = self.tmpfile
>   f.seek(0)
E   IOError: seek() called during concurrent operation on the same file 
object

/usr/lib/python2.7/dist-packages/_pytest/capture.py:375: IOError
--- Captured stderr teardown ---
127.0.0.1 - - [15/Dec/2017 07:58:18] "GET /get HTTP/1.1" 200 302
127.0.0.1 - - [15/Dec/2017 07:58:18] "GET /get HTTP/1.1" 200 302
127.0.0.1 - - [15/Dec/2017 07:58:18] "GET /get HTTP/1.1" 200 302
127.0.0.1 - - [15/Dec/2017 07:58:18] "GET /get HTTP/1.1" 200 302
127.0.0.1 - - [15/Dec/2017 07:58:18] "GET /get HTTP/1.1" 200 302
127.0.0.1 - - [15/Dec/2017 07:58:18] "GET /get HTTP/1.1" 200 302
127.0.0.1 - - [15/Dec/2017 07:58:18] "GET /get HTTP/1.1" 200 302
127.0.0.1 - - [15/Dec/2017 07:58:18] "GET /get HTTP/1.1" 200 302
127.0.0.1 - - [15/Dec/2017 07:58:18] "GET /get HTTP/1.1" 200 302
127.0.0.1 - - [15/Dec/2017 07:58:18] "GET /get HTTP/1.1" 200 302


DS

-- System Information:
Debian Release: 9.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)



Bug#884430: test_nothing_logged.py:7: AssertionError

2017-12-15 Thread Daniel Stender
Source: pytest-catchlog
Version: 1.2.2+git20170915-2
Severity: serious
Justification: fails to build from source

pytest-catchlog currently FTBFS:

I: pybuild base:184: python2.7 -m pytest -v -x
= test session starts ==
platform linux2 -- Python 2.7.14+, pytest-3.2.1, py-1.4.34, pluggy-0.4.0 -- 
/usr/bin/python2.7
cachedir: .cache
rootdir: /<>, inifile:
plugins: catchlog-1.2.2
collecting ... collected 14 items

test_pytest_catchlog.py::test_nothing_logged FAILED

=== FAILURES ===
_ test_nothing_logged __

testdir = 

def test_nothing_logged(testdir):
testdir.makepyfile('''
import sys
import logging

def test_foo():
sys.stdout.write('text going to stdout')
sys.stderr.write('text going to stderr')
assert False
''')
result = testdir.runpytest()
assert result.ret == 1
result.stdout.fnmatch_lines(['*- Captured stdout call -*',
 'text going to stdout'])
result.stdout.fnmatch_lines(['*- Captured stderr call -*',
 'text going to stderr'])
py.test.raises(Exception, result.stdout.fnmatch_lines,
>  ['*- Captured *log call -*'])
E   Failed: nomatch: '*- Captured stdout call -*'
E   and: u'= test session starts 
=='
E   and: u'platform linux2 -- Python 2.7.14+, pytest-3.2.1, py-1.4.34, 
pluggy-0.4.0'
E   and: u'rootdir: 
/tmp/pytest-of-aham/pytest-0/testdir/test_nothing_logged0, inifile:'
E   and: u'plugins: catchlog-1.2.2'
E   and: u'collected 1 item'
E   and: u''
E   and: u'test_nothing_logged.py F'
E   and: u''
E   and: u'=== FAILURES 
==='
E   and: u'___ test_foo 
___'
E   and: u''
E   and: u'def test_foo():'
E   and: u"sys.stdout.write('text going to stdout')"
E   and: u"sys.stderr.write('text going to stderr')"
E   and: u'>   assert False'
E   and: u'E   assert False'
E   and: u''
E   and: u'test_nothing_logged.py:7: AssertionError'
E   fnmatch: '*- Captured stdout call -*'
E  with: u'- Captured stdout call 
-'
E   exact match: 'text going to stdout'
E   nomatch: '*- Captured stderr call -*'
E   and: u'= test session starts 
=='
E   and: u'platform linux2 -- Python 2.7.14+, pytest-3.2.1, py-1.4.34, 
pluggy-0.4.0'
E   and: u'rootdir: 
/tmp/pytest-of-aham/pytest-0/testdir/test_nothing_logged0, inifile:'
E   and: u'plugins: catchlog-1.2.2'
E   and: u'collected 1 item'
E   and: u''
E   and: u'test_nothing_logged.py F'
E   and: u''
E   and: u'=== FAILURES 
==='
E   and: u'___ test_foo 
___'
E   and: u''
E   and: u'def test_foo():'
E   and: u"sys.stdout.write('text going to stdout')"
E   and: u"sys.stderr.write('text going to stderr')"
E   and: u'>   assert False'
E   and: u'E   assert False'
E   and: u''
E   and: u'test_nothing_logged.py:7: AssertionError'
E   and: u'- Captured stdout call 
-'
E   and: u'text going to stdout'
E   fnmatch: '*- Captured stderr call -*'
E  with: u'- Captured stderr call 
-'
E   exact match: 'text going to stderr'
E   nomatch: '*- Captured *log call -*'
E   and: u'= test session starts 
=='
E   and: u'platform linux2 -- Python 2.7.14+, pytest-3.2.1, py-1.4.34, 
pluggy-0.4.0'
E   and: u'rootdir: 
/tmp/pytest-of-aham/pytest-0/testdir/test_nothing_logged0, inifile:'
E   and: u'plugins: catchlog-1.2.2'
E   and: u'collected 1 item'
E   and: u''
E   and: u'test_nothing_logged.py F'
E   and: u''
E   and: u'=== FAILURES 
==='
E   and: u'___ test_foo 
___'
E   and: u''
E   and: u'def test_foo():'
E   and: u"sys.stdout.write('text going to stdout')"
E   and: u"  

Bug#881652: marked as pending

2017-11-14 Thread Daniel Stender
tag 881652 pending
thanks

Hello,

Bug #881652 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:


https://anonscm.debian.org/cgit/python-modules/packages/m2crypto.git/commit/?id=5246156

---
commit 52461565087b886105df5a2fe5c182b879e9d5df
Author: Daniel Stender <sten...@debian.org>
Date:   Tue Nov 14 00:02:06 2017 +0100

deb/rules: temporarily disable test_HTTPSConnection_SNI_support on ppc-s

diff --git a/debian/changelog b/debian/changelog
index 3e925bc..a3f2c00 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,8 +1,10 @@
 m2crypto (0.27.0-4) UNRELEASED; urgency=medium
 
+  * deb/rules: temporarily disable test_HTTPSConnection_SNI_support on ppc-s
+(Closes: #881652), drop sni-test-race.patch (fix not working).
   * deb/source/options: complete modified files for extend-diff-ignore.
 
- -- Daniel Stender <sten...@debian.org>  Mon, 13 Nov 2017 23:16:29 +0100
+ -- Daniel Stender <sten...@debian.org>  Mon, 13 Nov 2017 23:57:50 +0100
 
 m2crypto (0.27.0-3) unstable; urgency=medium
 



Bug#881652: m2crypto FTBFS on ppc64el: HttpslibSSLClientTestCase.test_HTTPSConnection_SNI_support test failure

2017-11-13 Thread Daniel Stender
Thanks for writing the bug report.

This problem should have taken been care of by sni-test-race.patch,
which draws from https://gitlab.com/m2crypto/m2crypto/merge_requests/141

Unfortunately, not even bumping the timeout using $M2CRYPTO_TEST_SSL_SLEEP 
makes this
disappear. I'm in contact with upstream, we're working something out.

DS

On 11/13/2017 10:25 PM, Adrian Bunk wrote:
> Source: m2crypto
> Version: 0.27.0-3
> Severity: serious
> 
> https://buildd.debian.org/status/fetch.php?pkg=m2crypto=ppc64el=0.27.0-3=1510582782=0
> 
> ...
> === FAILURES 
> ===
> __ HttpslibSSLClientTestCase.test_HTTPSConnection_SNI_support 
> __
> 
> self =  testMethod=test_HTTPSConnection_SNI_support>
> 
> def test_HTTPSConnection_SNI_support(self):
> args = ['s_server', '-servername', srv_host, '-debug', '-www',
> '-cert', 'server.pem', '-key', 'server_key.pem',
> '-cert2', 'server.pem', '-key2', 'server_key.pem',
> '-accept', str(self.srv_port)]
> pid = self.start_server(args)
> try:
> ctx = SSL.Context()
> c = httpslib.HTTPSConnection(srv_host, self.srv_port,
>  ssl_context=ctx)
> c.request('GET', '/')
> c.close()
> finally:
> time.sleep(sleepTime)
> out, err = self.stop_server(pid)
>>   self.assertIn('Hostname in TLS extension: "%s"' % srv_host, out)
> E   AssertionError: 'Hostname in TLS extension: "localhost"' not found in 
> 'Setting secondary ctx parameters\nUsing default temp DH parameters\nACCEPT\n'
> 
> tests/test_ssl.py:256: AssertionError
> === warnings summary 
> ===
> tests/test_bn.py::BNTestCase::test_randfname
>   /<>/tests/test_bn.py:71: DeprecationWarning: Don't use 
> BN.randfname(), use tempfile methods instead.
> r = BN.randfname(8)
> 
> tests/test_pgp.py::PGPTestCase::test_simple
>   /<>/M2Crypto/PGP/PublicKeyRing.py:22: DeprecationWarning: 
> Deprecated. No maintainer for PGP. If you use this, please inform M2Crypto 
> maintainer.
> DeprecationWarning)
>   /<>/M2Crypto/PGP/packet.py:48: DeprecationWarning: Deprecated. 
> No maintainer for PGP. If you use this, please inform M2Crypto maintainer.
> DeprecationWarning)
>   /<>/M2Crypto/PGP/PublicKey.py:21: DeprecationWarning: 
> Deprecated. No maintainer for PGP. If you use this, please inform M2Crypto 
> maintainer.
> DeprecationWarning)
>   /<>/M2Crypto/PGP/RSA.py:23: DeprecationWarning: Deprecated. No 
> maintainer for PGP. If you use this, please inform M2Crypto maintainer.
> warnings.warn('Deprecated. No maintainer for PGP. If you use this, please 
> inform M2Crypto maintainer.', DeprecationWarning)
> 
> tests/test_rand.py::RandTestCase::test_pseudo_bytes
>   /<>/M2Crypto/Rand.py:145: DeprecationWarning: The underlying 
> OpenSSL method has been deprecated. Use Rand.rand_bytes instead.
> DeprecationWarning)
> 
> tests/test_ssl.py::MiscSSLClientTestCase::test_tls1_nok
>   /<>/M2Crypto/SSL/Context.py:64: DeprecationWarning: Function 
> TLSv1_method has been deprecated.
> self.ctx = m2.ssl_ctx_new(proto())
> 
> tests/test_ssl.py::MiscSSLClientTestCase::test_verify_cb_old
>   /<>/M2Crypto/SSL/Connection.py:288: DeprecationWarning: Old 
> style callback, use cb_func(ok, store) instead
> return m2.ssl_connect(self.ssl, self._timeout)
> 
> tests/test_ssl.py::TwistedSSLClientTestCase::test_twisted_wrapper
>   /<>/tests/test_ssl.py:1010: UserWarning: Skipping twisted 
> wrapper test because twisted not found
> 'Skipping twisted wrapper test because twisted not found')
> 
> -- Docs: http://doc.pytest.org/en/latest/warnings.html
> = 1 failed, 273 passed, 1 skipped, 9 warnings in 82.52 seconds 
> =
> E: pybuild pybuild:283: test: plugin custom failed with: exit code=1: 
> python2.7 -Wd -m pytest -v -rs
> dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned 
> exit code 13
> debian/rules:18: recipe for target 'override_dh_auto_test' failed
> make[1]: *** [override_dh_auto_test] Error 25
> 
> 


-- 
4096R/DF5182C8 (sten...@debian.org)
http://www.danielstender.com/



Bug#876787: afl: FTBFS /usr/bin/ld: unrecognized option '--no-keep-files-mapped'

2017-09-25 Thread Daniel Stender
Package: src:afl
Version: 2.50b-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Control: block 873404 by -1

AFL begun to FTBFS recently with a clang error:


[+] All set and ready to build.
clang-3.9  -Wall -D_FORTIFY_SOURCE=2 -g -Wno-pointer-sign 
-DAFL_PATH=\"/usr/lib/afl\" -DBIN_PATH=\"/usr/bin\" -DVERSION=\"2.50b\"  
afl-clang-fast.c -o ../afl-clang-fast -Wl,-z,relro -Wl,-z,now
ln -sf afl-clang-fast ../afl-clang-fast++
clang++-3.9 `llvm-config-3.9 --cxxflags` -fno-rtti -fpic  -Wall 
-D_FORTIFY_SOURCE=2 -g -Wno-pointer-sign -DVERSION=\"2.50b\" 
-Wno-variadic-macros -shared afl-llvm-pass.so.cc -o ../afl-llvm-pass.so 
`llvm-config-3.9 --ldflags` -Wl,-z,relro -Wl,-z,now
warning: unknown warning option '-Wno-maybe-uninitialized'; did you mean 
'-Wno-uninitialized'? [-Wunknown-warning-option]
1 warning generated.
/usr/bin/ld: unrecognized option '--no-keep-files-mapped'
/usr/bin/ld: use the --help option for usage information
clang: error: linker command failed with exit code 1 (use -v to see invocation)
Makefile:83: recipe for target '../afl-llvm-pass.so' failed


This seems to be a problem in the build toolchain (this is going to be
reassigned). The same error appears also with clang-4.0 and clang-5.0, thus
blocking the llvm-toolchain update of AFL.

DS

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.12.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), 
LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages afl depends on:
ii  build-essential  12.4
ii  libc62.24-17

Versions of packages afl recommends:
ii  afl-clang  2.50b-1
ii  afl-doc2.50b-1

Versions of packages afl suggests:
ii  gnuplot   5.0.7+dfsg1-1
ii  gnuplot-qt [gnuplot]  5.0.7+dfsg1-1

-- no debconf information



Bug#869195: python-blosc: building of sphinx-docs breaks

2017-08-25 Thread Daniel Stender
This appears to be a problem with the numpydoc extension. I can't tell what's 
happening now,
however removing numpydoc from the needed/supported extensions in the package 
temporarily
solves the FTBFS.

For the record, this happens both with python-sphinx/numpydoc and 
python3-sphinx/numpydoc.


# Sphinx version: 1.5.6
# Python version: 2.7.13 (CPython)
# Docutils version: 0.13.1 release
# Jinja2 version: 2.9.6
# Last messages:
#   loading intersphinx inventory from http://docs.python.org/objects.inv...
#   WARNING: intersphinx inventory 'http://docs.python.org/objects.inv' not 
fetchable due to : 
HTTPConnectionPool(host='127.0.0.1', port=9): Max retries exceeded with url: 
http://docs.python.org/objects.inv (Caused by ProxyError('Cannot connect to 
proxy.', NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection 
refused',)))
#   building [mo]: targets for 0 po files that are out of date
#   building [html]: targets for 5 source files that are out of date
#   updating environment:
#   5 added, 0 changed, 0 removed
#   reading sources... [ 20%] index
#   reading sources... [ 40%] install
#   reading sources... [ 60%] intro
#   reading sources... [ 80%] reference
# Loaded extensions:
#   sphinx.ext.coverage (1.5.6) from 
/usr/lib/python2.7/dist-packages/sphinx/ext/coverage.pyc
#   sphinx.ext.todo (1.5.6) from 
/usr/lib/python2.7/dist-packages/sphinx/ext/todo.pyc
#   sphinx.ext.autodoc (1.5.6) from 
/usr/lib/python2.7/dist-packages/sphinx/ext/autodoc.pyc
#   sphinx.ext.intersphinx (1.5.6) from 
/usr/lib/python2.7/dist-packages/sphinx/ext/intersphinx.pyc
#   sphinx.ext.doctest (1.5.6) from 
/usr/lib/python2.7/dist-packages/sphinx/ext/doctest.pyc
#   alabaster (0.7.8) from 
/usr/lib/python2.7/dist-packages/alabaster/__init__.pyc
#   numpydoc (unknown version) from 
/usr/lib/python2.7/dist-packages/numpydoc/__init__.pyc
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/sphinx/cmdline.py", line 296, in main
app.build(opts.force_all, filenames)
  File "/usr/lib/python2.7/dist-packages/sphinx/application.py", line 333, in 
build
self.builder.build_update()
  File "/usr/lib/python2.7/dist-packages/sphinx/builders/__init__.py", line 
251, in build_update
'out of date' % len(to_build))
  File "/usr/lib/python2.7/dist-packages/sphinx/builders/__init__.py", line 
265, in build
self.doctreedir, self.app))
  File "/usr/lib/python2.7/dist-packages/sphinx/environment/__init__.py", line 
556, in update
self._read_serial(docnames, app)
  File "/usr/lib/python2.7/dist-packages/sphinx/environment/__init__.py", line 
576, in _read_serial
self.read_doc(docname, app)
  File "/usr/lib/python2.7/dist-packages/sphinx/environment/__init__.py", line 
684, in read_doc
pub.publish()
  File "/usr/lib/python2.7/dist-packages/docutils/core.py", line 217, in publish
self.settings)
  File "/usr/lib/python2.7/dist-packages/sphinx/io.py", line 55, in read
self.parse()
  File "/usr/lib/python2.7/dist-packages/docutils/readers/__init__.py", line 
78, in parse
self.parser.parse(self.input, document)
  File "/usr/lib/python2.7/dist-packages/docutils/parsers/rst/__init__.py", 
line 185, in parse
self.statemachine.run(inputlines, document, inliner=self.inliner)
  File "/usr/lib/python2.7/dist-packages/docutils/parsers/rst/states.py", line 
171, in run
input_source=document['source'])
  File "/usr/lib/python2.7/dist-packages/docutils/statemachine.py", line 239, 
in run
context, state, transitions)
  File "/usr/lib/python2.7/dist-packages/docutils/statemachine.py", line 460, 
in check_line
return method(match, context, next_state)
  File "/usr/lib/python2.7/dist-packages/docutils/parsers/rst/states.py", line 
2983, in text
self.section(title.lstrip(), source, style, lineno + 1, messages)
  File "/usr/lib/python2.7/dist-packages/docutils/parsers/rst/states.py", line 
327, in section
self.new_subsection(title, lineno, messages)
  File "/usr/lib/python2.7/dist-packages/docutils/parsers/rst/states.py", line 
395, in new_subsection
node=section_node, match_titles=True)
  File "/usr/lib/python2.7/dist-packages/docutils/parsers/rst/states.py", line 
282, in nested_parse
node=node, match_titles=match_titles)
  File "/usr/lib/python2.7/dist-packages/docutils/parsers/rst/states.py", line 
196, in run
results = StateMachineWS.run(self, input_lines, input_offset)
  File "/usr/lib/python2.7/dist-packages/docutils/statemachine.py", line 239, 
in run
context, state, transitions)
  File "/usr/lib/python2.7/dist-packages/docutils/statemachine.py", line 460, 
in check_line
return method(match, context, next_state)
  File "/usr/lib/python2.7/dist-packages/docutils/parsers/rst/states.py", line 
2748, in underline
self.section(title, source, style, lineno - 1, messages)
  File "/usr/lib/python2.7/dist-packages/docutils/parsers/rst/states.py", line 
327, in section
self.new_subsection(title, lineno, messages)
  File 

Bug#872037: marked as pending

2017-08-14 Thread Daniel Stender
tag 872037 pending
thanks

Hello,

Bug #872037 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:


https://anonscm.debian.org/cgit/debian-science/packages/libvigraimpex.git/commit/?id=19741cd

---
commit 19741cd527073d1e4794ebc74bbf0742bc307aa9
Author: Daniel Stender <sten...@debian.org>
Date:   Mon Aug 14 22:40:50 2017 +0200

deb/rules: build test_multiarray with -O0

diff --git a/debian/changelog b/debian/changelog
index e609a08..4e52420 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+libvigraimpex (1.10.0+git20160211.167be93+dfsg-5) unstable; urgency=medium
+
+  * deb/rules: build test_multiarray with -O0 (Closes: #872037).
+
+ -- Daniel Stender <sten...@debian.org>  Mon, 14 Aug 2017 22:40:53 +0200
+
 libvigraimpex (1.10.0+git20160211.167be93+dfsg-4) unstable; urgency=medium
 
   * Upload to unstable.



Bug#872037: libvigrampex: Failure in MultiArrayPointoperatorsTest::testCombine2() [mips64el]

2017-08-13 Thread Daniel Stender
Source: libvigraimpex
Version: 1.10.0+git20160211.167be93+dfsg-4
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Current Vigra FTBFS on mips64el [1]:


[ 63%] Building CXX object 
test/multiarray/CMakeFiles/test_multiarray.dir/testsuccess.cxx.o
cd 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/obj/test/multiarray 
&& /usr/bin/c++  -DHasHDF5 -DHasJPEG -DHasPNG -DHasTIFF 
-I/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/include 
-I/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/test/include 
-I/usr/include/hdf5/serial  -std=c++11 -pthread -W -Wall -Wextra 
-Wno-unused-parameter -Wno-sign-compare -Wno-unused-variable -Wno-type-limits 
-g -O2 
-fdebug-prefix-map=/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg=.
 -fstack-protector-strong -Wformat -Werror=format-security -pipe -Wdate-time 
-D_FORTIFY_SOURCE=2   -o CMakeFiles/test_multiarray.dir/testsuccess.cxx.o -c 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/obj/test/multiarray/testsuccess.cxx
[ 65%] Linking CXX executable test_multiarray
cd 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/obj/test/multiarray 
&& /usr/bin/cmake -E cmake_link_script CMakeFiles/test_multiarray.dir/link.txt 
--verbose=1
/usr/bin/c++  -std=c++11 -pthread -W -Wall -Wextra -Wno-unused-parameter 
-Wno-sign-compare -Wno-unused-variable -Wno-type-limits -g -O2 
-fdebug-prefix-map=/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg=.
 -fstack-protector-strong -Wformat -Werror=format-security -pipe -Wdate-time 
-D_FORTIFY_SOURCE=2  -rdynamic CMakeFiles/test_multiarray.dir/test.cxx.o 
CMakeFiles/test_multiarray.dir/testsuccess.cxx.o  -o test_multiarray 
-Wl,-rpath,/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/obj/src/impex:/usr/lib/mips64el-linux-gnuabi64/hdf5/serial
 ../../src/impex/libvigraimpex.so.6.1.11.0 -ljpeg -lpng -lz -ltiff -lIlmImf 
-lImath -lHalf -lIex -lIlmThread 
/usr/lib/mips64el-linux-gnuabi64/hdf5/serial/libhdf5.so 
/usr/lib/mips64el-linux-gnuabi64/hdf5/serial/libhdf5_hl.so -lsz -lz -ltiff 
-lIlmImf -lImath -lHalf -lIex -lIlmThread 
/usr/lib/mips64el-linux-gnuabi64/hdf5/serial/libhdf5.so 
/usr/lib/mips64el-linux-gnuabi64/hdf5/serial/libhdf5_hl.so -lsz 
Running test_multiarray
cd 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/obj/test/multiarray 
&& ./run_test_multiarray.sh
Entering test suite MultiArrayTestSuite
All (24) tests passed in test suite MultiArrayTestSuite
Leaving test suite MultiArrayTestSuite

Entering test suite MultiArrayDataTestSuite
All (32) tests passed in test suite MultiArrayDataTestSuite
Leaving test suite MultiArrayDataTestSuite

Entering test suite ImageViewTestSuite
All (16) tests passed in test suite ImageViewTestSuite
Leaving test suite ImageViewTestSuite

Entering test suite MultiArrayPointOperatorsTestSuite

Failure in MultiArrayPointoperatorsTest::testCombine2()
Unexpected signal: memory access violation

Fatal error - aborting test suite MultiArrayPointOperatorsTestSuite.

test/multiarray/CMakeFiles/test_multiarray.dir/build.make:146: recipe for 
target 'test/multiarray/test_multiarray' failed
make[5]: *** [test/multiarray/test_multiarray] Error 1


DS

[1] 
https://buildd.debian.org/status/fetch.php?pkg=libvigraimpex=mips64el=1.10.0%2Bgit20160211.167be93%2Bdfsg-4=1502638529=0

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.11.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), 
LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)



Bug#871556: libvigraimpex: several tests failing in Gridgraph Test Dimension 3

2017-08-09 Thread Daniel Stender
Source: libvigraimpex
Version: 1.10.0+git20160211.167be93+dfsg-3
Severity: serious
Justification: fails to build from source (but built successfully in the past)

With the latest upload there are FTBFS problems on some archs.


Running test_gridgraph
cd 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/obj/test/gridgraph 
&& ./run_test_gridgraph.sh
Entering test suite Gridgraph Test
Entering test suite Gridgraph Test Dimension 2
All (38) tests passed in test suite Gridgraph Test Dimension 2
Leaving test suite Gridgraph Test Dimension 2
Entering test suite Gridgraph Test Dimension 3

Failure in NeighborhoodTests::testIndirectNeighborhood()
Assertion failed: neighborOffsets[k] == -neighborOffsets[neighborCount-1-k] 
[(-1, -1, -1) != (-1, 1, -1)] 
(/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/test/gridgraph/test.cxx:183)

Failure in (::template testNeighborIterator)()
Unexpected Contract exception:  
Precondition violation!
Index out of bounds
(/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/include/vigra/multi_array.hxx:999)

Last checkpoint: target(*e, g) == *n [(1, -1, 0) != (1, -1, 0)] 
(/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/test/gridgraph/test.cxx:744)

Failure in (::template testNeighborIterator)()
Assertion failed: source(*e, g) == *j [(0, -2, 0) != (0, 0, 0)] 
(/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/test/gridgraph/test.cxx:743)

Failure in (::template testBackNeighborIterator)()
Unexpected Contract exception:  
Precondition violation!
Index out of bounds
(/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/include/vigra/multi_array.hxx:999)

Last checkpoint: target(*e, g) == *n [(0, -1, 0) != (0, -1, 0)] 
(/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/test/gridgraph/test.cxx:940)

Failure in (::template 
testBackNeighborIterator)()
Unexpected Contract exception:  
Precondition violation!
Index out of bounds
(/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/include/vigra/multi_array.hxx:999)

Last checkpoint: target(*e, g) == *n [(0, -1, 0) != (0, -1, 0)] 
(/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/test/gridgraph/test.cxx:940)

Failure in (::template testEdgeIterator)()
Unexpected Contract exception:  
Precondition violation!
Index out of bounds
(/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/include/vigra/multi_array.hxx:999)

Last checkpoint: !(e == lemon::INVALID) 
(/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/test/gridgraph/test.cxx:1062)

Failure in (::template testEdgeIterator)()
Unexpected Contract exception:  
Precondition violation!
Index out of bounds
(/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/include/vigra/multi_array.hxx:999)

Last checkpoint: !(e == lemon::INVALID) 
(/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/test/gridgraph/test.cxx:1062)

Failure in (::template testArcIterator)()
Unexpected Contract exception:  
Precondition violation!
Index out of bounds
(/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/include/vigra/multi_array.hxx:999)

Last checkpoint: !(e == lemon::INVALID) 
(/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/test/gridgraph/test.cxx:1143)

Failure in (::template testArcIterator)()
Unexpected Contract exception:  
Precondition violation!
Index out of bounds
(/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/include/vigra/multi_array.hxx:999)

Last checkpoint: !(e == lemon::INVALID) 
(/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/test/gridgraph/test.cxx:1143)

9 of 38 tests failed in test suite Gridgraph Test Dimension 3
Leaving test suite Gridgraph Test Dimension 3

9 of 76 tests failed in test suite Gridgraph Test
Leaving test suite Gridgraph Test

test/gridgraph/CMakeFiles/test_gridgraph.dir/build.make:123: recipe for target 
'test/gridgraph/test_gridgraph' failed
make[5]: *** [test/gridgraph/test_gridgraph] Error 1
make[5]: *** Deleting file 'test/gridgraph/test_gridgraph'
make[5]: Leaving directory 
'/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/obj'
CMakeFiles/Makefile2:1895: recipe for target 
'test/gridgraph/CMakeFiles/test_gridgraph.dir/all' failed


DS

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.5.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), 
LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)



Bug#853513: libvigraimpex: ftbfs with GCC-7

2017-08-08 Thread Daniel Stender
The particular testblock has been disabled temporarily with 
1.10.0+git20160211.167be93+dfsg-3.

DS

-- 
4096R/DF5182C8 (sten...@debian.org)
http://www.danielstender.com/



Bug#871169: marked as pending

2017-08-08 Thread Daniel Stender
tag 871169 pending
thanks

Hello,

Bug #871169 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:


https://anonscm.debian.org/cgit/debian-science/packages/libvigraimpex.git/commit/?id=1db160a

---
commit 1db160a61feaa438b2731e3dc97d60ab750b2c93
Author: Daniel Stender <sten...@debian.org>
Date:   Wed Aug 9 00:46:43 2017 +0200

deb/changelog: finalized, upload to unstable

diff --git a/debian/changelog b/debian/changelog
index f34c475..fabb860 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,12 +1,11 @@
-libvigraimpex (1.10.0+git20160211.167be93+dfsg-3) UNRELEASED; urgency=medium
+libvigraimpex (1.10.0+git20160211.167be93+dfsg-3) unstable; urgency=medium
 
   * add temporarily-disable-blockwisealgorithms-tests.patch.
-  * add const-swap.patch [thanks to Matthias Klose].
-  * deb/copyright:
-+ add src/images/dissolved_color.gif to Files-Excluded (contains
-  "lenna" in composite).
+  * add const-swap.patch (Closes: #871169) [thanks to Matthias Klose].
+  * deb/copyright: add src/images/dissolved_color.gif to Files-Excluded
+(which contains "lenna" in composite).
 
- -- Daniel Stender <sten...@debian.org>  Tue, 08 Aug 2017 23:03:34 +0200
+ -- Daniel Stender <sten...@debian.org>  Wed, 09 Aug 2017 00:41:15 +0200
 
 libvigraimpex (1.10.0+git20160211.167be93+dfsg-2) unstable; urgency=medium
 



Bug#853513: libvigraimpex: ftbfs with GCC-7

2017-08-07 Thread Daniel Stender
On 07.08.2017 20:26, Matthias Klose wrote:
> Control: tags -1 + patch
> 
> patch at
> http://launchpadlibrarian.net/332312910/libvigraimpex_1.10.0+git20160211.167be93+dfsg-2build3_1.10.0+git20160211.167be93+dfsg-2ubuntu1.diff.gz

Great! I'll take care of it shortly.

DS

-- 
4096R/DF5182C8 (sten...@debian.org)
http://www.danielstender.com/



Bug#869094: marked as pending

2017-08-05 Thread Daniel Stender
tag 869094 pending
thanks

Hello,

Bug #869094 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:


https://anonscm.debian.org/cgit/python-modules/packages/pytest-xdist.git/commit/?id=868f5d6

---
commit 868f5d6e0c37f6a420e2189f21496f14ada607a3
Author: Daniel Stender <sten...@debian.org>
Date:   Sat Aug 5 19:29:04 2017 +0200

add temporarily-disable-test_looponfail_removed_test.patch

diff --git a/debian/changelog b/debian/changelog
index d1a63db..6506fe7 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -10,8 +10,9 @@ pytest-xdist (1.15.0-4) UNRELEASED; urgency=medium
 + change debian-branch to meet DEP-14.
 + add sign-tags field switched to True.
   * use debhelper level 10 (changes in deb/control and deb/compat).
+  * add temporarily-disable-test_looponfail_removed_test.patch (Closes: 
#869094).
 
- -- Daniel Stender <sten...@debian.org>  Sat, 05 Aug 2017 19:16:09 +0200
+ -- Daniel Stender <sten...@debian.org>  Sat, 05 Aug 2017 19:28:10 +0200
 
 pytest-xdist (1.15.0-3) unstable; urgency=medium
 



Bug#867516: marked as pending

2017-08-05 Thread Daniel Stender
tag 867516 pending
thanks

Hello,

Bug #867516 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:


https://anonscm.debian.org/cgit/python-modules/packages/pytest-xdist.git/commit/?id=cddf44e

---
commit cddf44ea0ffdf8f4a7fc005023073452a90da60f
Author: Daniel Stender <sten...@debian.org>
Date:   Sat Aug 5 19:47:43 2017 +0200

deb/changelog: add another bug to close

diff --git a/debian/changelog b/debian/changelog
index 39f1ffa..8c310ef 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,6 +1,6 @@
 pytest-xdist (1.18.2-1) UNRELEASED; urgency=medium
 
-  * New upstream release (Closes: #864360):
+  * New upstream release (Closes: #864360, #867516):
 + drop fix-acceptance_test-for-pytest3.patch (solved upstream).
   * deb/control:
 + add DPMT as Uploaders.
@@ -16,7 +16,7 @@ pytest-xdist (1.18.2-1) UNRELEASED; urgency=medium
   * use debhelper level 10 (changes in deb/control and deb/compat).
   * add temporarily-disable-test_looponfail_removed_test.patch (Closes: 
#869094).
 
- -- Daniel Stender <sten...@debian.org>  Sat, 05 Aug 2017 19:43:41 +0200
+ -- Daniel Stender <sten...@debian.org>  Sat, 05 Aug 2017 19:46:43 +0200
 
 pytest-xdist (1.15.0-3) unstable; urgency=medium
 



Bug#869718: packer currently doesn't build

2017-07-25 Thread Daniel Stender
Control: retitle -1 packer: currently doesn't build (updated build-deps)

... I've mend build-deps.

DS

-- 
4096R/DF5182C8 (sten...@debian.org)
http://www.danielstender.com/



Bug#869718: packer currently doesn't build

2017-07-25 Thread Daniel Stender
Package: packer
Version: 0.10.2+dfsg-6
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Packer currently doesn't build because we've begun to update the reverse-deps
for the upcoming packer update (#846549):


src/github.com/mitchellh/packer/communicator/winrm/communicator.go:10:2: cannot 
find package "github.com/masterzen/winrm/winrm" in any of:
/usr/lib/go-1.8/src/github.com/masterzen/winrm/winrm (from $GOROOT)

/<>/packer-0.10.2+dfsg/obj-x86_64-linux-gnu/src/github.com/masterzen/winrm/winrm
 (from $GOPATH)


Thanks,
DS

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.5.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), 
LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages packer depends on:
ii  libc6  2.24-12

Versions of packages packer recommends:
pn  docker.io  
ii  qemu   1:2.8+dfsg-6

Versions of packages packer suggests:
ii  ansible  2.2.1.0-2
pn  chef 

-- no debconf information



Bug#869195: python-blosc: building of sphinx-docs breaks

2017-07-21 Thread Daniel Stender
Package: python-blosc
Version: 1.4.4+ds1-3+b1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Control: forwarded -1 https://github.com/Blosc/python-blosc/issues/125

The building of python-blosc currenty breaks:


Running Sphinx v1.5.6
making output directory...
loading pickled environment... not yet created
loading intersphinx inventory from http://docs.python.org/objects.inv...
WARNING: intersphinx inventory 'http://docs.python.org/objects.inv' not 
fetchable due to : 
HTTPConnectionPool(host='127.0.0.1', port=9): Max retries exceeded with url: 
http://docs.python.org/objects.inv (Caused by ProxyError('Cannot connect to 
proxy.', 
NewConnectionError(': Failed to establish a new connection: [Errno 111] 
Connection refused',)))
building [mo]: targets for 0 po files that are out of date
building [html]: targets for 5 source files that are out of date
updating environment: 5 added, 0 changed, 0 removed
reading sources... [ 20%] index
reading sources... [ 40%] install
reading sources... [ 60%] intro
reading sources... [ 80%] reference

Exception occurred:
  File "/usr/lib/python2.7/re.py", line 155, in sub
return _compile(pattern, flags).sub(repl, string, count)
TypeError: expected string or buffer
The full traceback has been saved in /tmp/sphinx-err-A00fVX.log, if you want to 
report the issue to the developers.
Please also report this if it was a user error, so that a better error message 
can be provided next time.
A bug report can be filed in the tracker at 
. Thanks!
debian/rules:12: recipe for target 'override_dh_auto_install' failed


The package builds on python3-sphinx, but this happens with python-sphinx 
either.

Thanks,
DS

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.5.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), 
LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages python-blosc depends on:
ii  libblosc1  1.11.1+ds2-2
ii  libc6  2.24-12
ii  python 2.7.13-2

python-blosc recommends no packages.

Versions of packages python-blosc suggests:
ii  python-blosc-doc  1.4.4+ds1-3

-- no debconf information



Bug#869094: pytest-xdist: TestLooponFailing::test_looponfail_removed_test FAILED

2017-07-20 Thread Daniel Stender
Source: pytest-xdist
Version: 1.15.0-3
Severity: serious
Justification: fails to build from source
Control: forwarded -1 https://github.com/pytest-dev/pytest-xdist/issues/163

There is a new test failure with Pytest >= 3.1.0, during the build it appears
the first time with Python 2.7:


=== FAILURES ===
 TestLooponFailing.test_looponfail_removed_test 

self = 
testdir = 

def test_looponfail_removed_test(self, testdir):
modcol = testdir.getmodulecol("""
def test_one():
assert 0
def test_two():
assert 0
""")
remotecontrol = RemoteControl(modcol.config)
remotecontrol.loop_once()
assert len(remotecontrol.failures) == 2

modcol.fspath.write(py.code.Source("""
def test_xxx(): # renamed test
assert 0
def test_two():
assert 1 # pass now
"""))
removepyc(modcol.fspath)
remotecontrol.loop_once()
>   assert len(remotecontrol.failures) == 0
E   AssertionError: assert 1 == 0
E+  where 1 = len(['test_looponfail_removed_test.py::test_xxx'])
E+where ['test_looponfail_removed_test.py::test_xxx'] = 
.failures


The failure takes place also with the latest version 0.18.1, it isn't yet solved
upstream.

DS

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.5.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), 
LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)



Bug#868780: marked as pending

2017-07-19 Thread Daniel Stender
tag 868780 pending
thanks

Hello,

Bug #868780 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:


https://anonscm.debian.org/cgit/python-modules/packages/pytest-catchlog.git/commit/?id=7cd007a

---
commit 7cd007a50fe894534d61baefbac00a5d9c3e70ff
Author: Daniel Stender <sten...@debian.org>
Date:   Wed Jul 19 08:26:36 2017 +0200

add fix-test-failures.patch

diff --git a/debian/changelog b/debian/changelog
index 9194596..bd73860 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -5,8 +5,9 @@ pytest-catchlog (1.2.2-3) UNRELEASED; urgency=medium
 + change debian-branch to meet DEP-14.
 + add sign-tags.
   * deb/tests/control: dropped allow-stderr (not needed).
+  * add fix-test-failures.patch (Closes: #868780).
 
- -- Daniel Stender <sten...@debian.org>  Tue, 18 Jul 2017 16:28:36 +0200
+ -- Daniel Stender <sten...@debian.org>  Wed, 19 Jul 2017 08:24:12 +0200
 
 pytest-catchlog (1.2.2-1) unstable; urgency=medium
 



Bug#868780: pytest-catchlog: latest pytest breaks test_compat_camel_case_aliases

2017-07-18 Thread Daniel Stender
Source: pytest-catchlog
Version: 1.2.2-1
Severity: serious
Justification: fails to build from source
Control: forwarded -1 https://github.com/eisensheng/pytest-catchlog/issues/68

Latest Pytest in Debian (3.1.3) breaks the tests of this package:


test_pytest_catchlog.py::test_record_tuples PASSED
test_pytest_catchlog.py::test_compat_camel_case_aliases FAILED

=== FAILURES ===
 test_compat_camel_case_aliases 

testdir = 

def test_compat_camel_case_aliases(testdir):
testdir.makepyfile('''
import logging

def test_foo(caplog):
caplog.setLevel(logging.INFO)
logging.getLogger().debug('boo!')

with caplog.atLevel(logging.WARNING):
logging.getLogger().info('catch me if you can')
''')
result = testdir.runpytest()
assert result.ret == 0

py.test.raises(Exception, result.stdout.fnmatch_lines,
   ['*- Captured *log call -*'])

result = testdir.runpytest('-rw')
assert result.ret == 0
result.stdout.fnmatch_lines('''
=*warning summary*=
*WL1*test_compat_camel_case_aliases*caplog.setLevel()*deprecated*
*WL1*test_compat_camel_case_aliases*caplog.atLevel()*deprecated*
>   ''')
E   Failed: nomatch: '=*warning summary*='
E   and: u'= test session starts 
=='
E   and: u'platform linux2 -- Python 2.7.13, pytest-3.1.3, py-1.4.34, 
pluggy-0.4.0'
E   and: u'rootdir: 
/tmp/pytest-of-aham/pytest-0/testdir/test_compat_camel_case_aliases0, inifile:'
E   and: u'plugins: catchlog-1.2.2'
E   and: u'collected 1 item'
E   and: u''
E   and: u'test_compat_camel_case_aliases.py .'
E   and: u''
E   and: u'=== warnings summary 
==='
E   and: u'test_compat_camel_case_aliases.py::test_foo'
E   and: u"  'caplog.setLevel()' is deprecated, use 
'caplog.set_level()' instead"
E   and: u"  'caplog.atLevel()' is deprecated, use 'caplog.at_level()' 
instead"
E   and: u''
E   and: u'-- Docs: http://doc.pytest.org/en/latest/warnings.html'
E   and: u'= 1 passed, 2 warnings in 0.00 seconds 
='
E   and: u''
E   remains unmatched: '=*warning summary*='

/<>/test_pytest_catchlog.py:230: Failed
- Captured stdout call -
= test session starts ==
platform linux2 -- Python 2.7.13, pytest-3.1.3, py-1.4.34, pluggy-0.4.0
rootdir: /tmp/pytest-of-aham/pytest-0/testdir/test_compat_camel_case_aliases0, 
inifile:
plugins: catchlog-1.2.2
collected 1 item

test_compat_camel_case_aliases.py .

=== warnings summary ===
test_compat_camel_case_aliases.py::test_foo
  'caplog.setLevel()' is deprecated, use 'caplog.set_level()' instead
  'caplog.atLevel()' is deprecated, use 'caplog.at_level()' instead

-- Docs: http://doc.pytest.org/en/latest/warnings.html
= 1 passed, 2 warnings in 0.01 seconds =
= test session starts ==
platform linux2 -- Python 2.7.13, pytest-3.1.3, py-1.4.34, pluggy-0.4.0
rootdir: /tmp/pytest-of-aham/pytest-0/testdir/test_compat_camel_case_aliases0, 
inifile:
plugins: catchlog-1.2.2
collected 1 item

test_compat_camel_case_aliases.py .

=== warnings summary ===
test_compat_camel_case_aliases.py::test_foo
  'caplog.setLevel()' is deprecated, use 'caplog.set_level()' instead
  'caplog.atLevel()' is deprecated, use 'caplog.at_level()' instead

-- Docs: http://doc.pytest.org/en/latest/warnings.html
= 1 passed, 2 warnings in 0.00 seconds =
-- Captured log call ---
test_compat_camel_case_aliases.py5 DEBUGboo!
test_compat_camel_case_aliases.py8 INFO catch me if you can
test_compat_camel_case_aliases.py5 DEBUGboo!
test_compat_camel_case_aliases.py8 INFO catch me if you can
 Interrupted: stopping after 1 failures 
= 1 failed, 10 passed in 0.45 seconds ==
E: pybuild pybuild:283: test: plugin custom failed with: exit code=2: python2.7 
-m pytest -v -x


Thanks,
DS

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.5.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), 
LANGUAGE=de_DE.utf8 

Bug#863512: numba: segfault on test_shape [s390x]

2017-05-27 Thread Daniel Stender
Source: numba
Version: 0.33.0-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=numba=s390x=0.33.0-1=1495911986=0

This test breaks on s390x:


numba/tests/test_array_attr.py::TestNestedArrayAttr::test_shape Segmentation 
fault
E: pybuild pybuild:283: test: plugin custom failed with: exit code=139: cd 
/«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build && python2.7 -Wd -m pytest 
numba/tests -v -rs
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned 
exit code 13


-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
http://www.danielstender.com/



Bug#863509: numba: test_mean_magnitude breaks (plugin custom failed with: exit code=1) [mips, mipsel]

2017-05-27 Thread Daniel Stender
Source: numba
Version: 0.33.0-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=numba=mips=0.33.0-1=1495913987=0
https://buildd.debian.org/status/fetch.php?pkg=numba=mipsel=0.33.0-1=1495915594=0

This test breaks appears on the mips archs:


numba/tests/test_array_reductions.py::TestArrayReductions::test_mean_basic 
PASSED
numba/tests/test_array_reductions.py::TestArrayReductions::test_mean_magnitude 
E: pybuild pybuild:283: test: plugin custom failed with: exit code=1: cd 
/«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build && python2.7 -Wd -m pytest 
numba/tests -v -rs
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned 
exit code 13


-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
http://www.danielstender.com/



Bug#863511: numba: segfault on test_array_reshape [ppc64el]

2017-05-27 Thread Daniel Stender
Source: numba
Version: 0.33.0-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=numba=ppc64el=0.33.0-1=1495912133=0

Tests break with a segault on s390x:


numba/tests/test_array_manipulation.py::TestArrayManipulation::test_add_axis2_npm
 PASSED
numba/tests/test_array_manipulation.py::TestArrayManipulation::test_array_reshape
 Segmentation fault
E: pybuild pybuild:283: test: plugin custom failed with: exit code=139: cd 
/«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build && python2.7 -Wd -m pytest 
numba/tests -v -rs
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned 
exit code 13


-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
http://www.danielstender.com/



Bug#863508: numba: FTBFS: LLVM ERROR: Program used external function '__aeabi_unwind_cpp_pr0' [armel, armhf]

2017-05-27 Thread Daniel Stender
Source: numba
Version: 0.33.0-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=numba=armel=0.33.0-1=1495912245=0
https://buildd.debian.org/status/fetch.php?pkg=numba=armhf=0.33.0-1=1495912383=0

FTBFS on armel and armhf:


http_proxy='127.0.0.1:9' sphinx-build -N -bhtml 
.pybuild/pythonX.Y_2.7/build/docs/source/ 
debian/numba-doc/usr/share/doc/numba-doc/html/
Running Sphinx v1.4.9
making output directory...
LLVM ERROR: Program used external function '__aeabi_unwind_cpp_pr0' which could 
not be resolved!
debian/rules:22: recipe for target 'override_dh_installdocs' failed
make[1]: *** [override_dh_installdocs] Error 1


-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
http://www.danielstender.com/



Bug#863507: numba: tests are not running/immediately breaking (plugin custom failed with: exit code=1) [armel, armhf]

2017-05-27 Thread Daniel Stender
Source: numba
Version: 0.33.0-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=numba=armel=0.33.0-1=1495912245=0
https://buildd.debian.org/status/fetch.php?pkg=numba=armhf=0.33.0-1=1495912383=0

Tests are immediately breaking on armel and armhf:


PYBUILD_SYSTEM=custom PYBUILD_TEST_ARGS="cd {build_dir} && {interpreter} -Wd -m 
pytest numba/tests -v -rs" dh_auto_test || true
I: pybuild base:184: cd /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build && 
python2.7 -Wd -m pytest numba/tests -v -rs
= test session starts ==
platform linux2 -- Python 2.7.13, pytest-3.0.6, py-1.4.32, pluggy-0.4.0 -- 
/usr/bin/python2.7
cachedir: ../../../.cache
rootdir: /«PKGBUILDDIR», inifile: 
collecting ... E: pybuild pybuild:283: test: plugin custom failed with: exit 
code=1: cd /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build && python2.7 -Wd -m 
pytest numba/tests -v -rs
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned 
exit code 13


-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
http://www.danielstender.com/



Bug#863506: numba: KeyError in numba/tracing.py [amd64, i386, arm64]

2017-05-27 Thread Daniel Stender
Source: numba
Version: 0.33.0-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=numba=i386=0.33.0-1=1495914429=0
https://buildd.debian.org/status/fetch.php?pkg=numba=arm64=0.33.0-1=1495916190=0

This test failure appears:


_ test _

args = (), kwds = {}, fname = 'numba.tests.test_tracing.test', ftype = None

def wrapper(*args, **kwds):
if not logger.isEnabledFor(logging.INFO) or tls.tracing:
return func(*args, **kwds)

fname, ftype = find_function_info(func, spec, args)

try:
tls.tracing = True
>   enter, leave = create_events(fname, spec, args, kwds)

numba/tracing.py:103: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

fname = 'numba.tests.test_tracing.test'
spec = ArgSpec(args=['x', 'y', 'z'], varargs=None, keywords=None, 
defaults=(True,))
args = (), kwds = {}

def create_events(fname, spec, args, kwds):

values = dict()
if spec.defaults:
values = dict(zip(spec.args[-len(spec.defaults):],spec.defaults))
values.update(kwds)
values.update(list(zip(spec.args[:len(args)], args)))
>   positional = ['%s=%r'%(a, values.pop(a)) for a in spec.args]
E   KeyError: 'x'

numba/tracing.py:66: KeyError


-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
http://www.danielstender.com/



Bug#863505: numba: AssertionError in TestTimedeltaArithmeticNoPython.test_mul and others [arm64]

2017-05-27 Thread Daniel Stender
Source: numba
Version: 0.33.0-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=numba=arm64=0.33.0-1=1495916190=0

There are a couple of supposedly related test failures on arm64:


___ TestTimedeltaArithmeticNoPython.test_mul ___

self = 

def test_mul(self):
f = self.jit(mul_usecase)
def check(a, b, expected):
self.assertPreciseEqual(f(a, b), expected)
self.assertPreciseEqual(f(b, a), expected)

# non-int64 int * timedelta64
check(TD(3), np.uint32(2), TD(6))
# int * timedelta64
check(TD(3), 2, TD(6))
check(TD(3, 'ps'), 2, TD(6, 'ps'))
check(TD('NaT', 'ps'), 2, TD('NaT', 'ps'))
# float * timedelta64
check(TD(7), 1.5, TD(10))
check(TD(-7), 1.5, TD(-10))
check(TD(7, 'ps'), -1.5, TD(-10, 'ps'))
check(TD(-7), -1.5, TD(10))
check(TD('NaT', 'ps'), -1.5, TD('NaT', 'ps'))
>   check(TD(7, 'ps'), float('nan'), TD('NaT', 'ps'))

numba/tests/test_npdatetime.py:328: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
numba/tests/test_npdatetime.py:313: in check
self.assertPreciseEqual(f(a, b), expected)
numba/tests/support.py:257: in assertPreciseEqual
self.fail("when comparing %s and %s: %s" % (first, second, failure_msg))
E   AssertionError: when comparing 0 picoseconds and NaT: 
numpy.timedelta64(0,'ps') != numpy.timedelta64('NaT','ps')



___ TestLoopTypesDatetimeNoPython.test_multiply_dm_m ___

self = 

def test_template(self):
fn = _make_ufunc_usecase(ufunc)
>   self._check_loop(fn, ufunc, loop)

numba/tests/test_ufuncs.py:1514: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
numba/tests/test_ufuncs.py:1471: in _check_loop
self._check_ufunc_with_dtypes(fn, ufunc, letter_types)
numba/tests/test_ufuncs.py:1500: in _check_ufunc_with_dtypes
ulps=ulps)
numba/tests/support.py:257: in assertPreciseEqual
self.fail("when comparing %s and %s: %s" % (first, second, failure_msg))
E   AssertionError: when comparing [   -4 0 3 'NaT' 'NaT' 0-7 
'NaT'] and [   -4 0 3 'NaT' 'NaT' 0-7 0]: 
numpy.timedelta64('NaT','D') != numpy.timedelta64(0,'D') : ufunc 'multiply' 
arrays differ ([array([ 1.5,  0. ,  1.5,  nan, -3.5,  0. , -3.5,  nan]), 
array([   -3, 0, 2, 'NaT', 'NaT',-3, 2, 0], 
dtype='timedelta64[D]'), array([   -4, 0, 3, 'NaT', 'NaT', 0,
-7, 0], dtype='timedelta64[D]')]):
E   args: exact
E   expected [   -4 0 3 'NaT' 'NaT' 0-7 'NaT']
E   got [   -4 0 3 'NaT' 'NaT' 0-7 0]



___ TestLoopTypesDatetimeNoPython.test_multiply_md_m ___

self = 

def test_template(self):
fn = _make_ufunc_usecase(ufunc)
>   self._check_loop(fn, ufunc, loop)

numba/tests/test_ufuncs.py:1514: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
numba/tests/test_ufuncs.py:1471: in _check_loop
self._check_ufunc_with_dtypes(fn, ufunc, letter_types)
numba/tests/test_ufuncs.py:1500: in _check_ufunc_with_dtypes
ulps=ulps)
numba/tests/support.py:257: in assertPreciseEqual
self.fail("when comparing %s and %s: %s" % (first, second, failure_msg))
E   AssertionError: when comparing [   -7 'NaT' 3 0 0 'NaT'-4 
'NaT'] and [   -7 'NaT' 3 0 0 'NaT'-4 0]: 
numpy.timedelta64('NaT','D') != numpy.timedelta64(0,'D') : ufunc 'multiply' 
arrays differ ([array([2, 'NaT', 2, 0,-3, 'NaT',-3, 0], 
dtype='timedelta64[D]'), array([-3.5,  nan,  1.5,  0. ,  0. , -3.5,  1.5,  
nan]), array([   -7, 'NaT', 3, 0, 0, 'NaT',-4, 0], 
dtype='timedelta64[D]')]):
E   args: exact
E   expected [   -7 'NaT' 3 0 0 'NaT'-4 'NaT']
E   got [   -7 'NaT' 3 0 0 'NaT'-4 0]


-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
http://www.danielstender.com/



Bug#863504: numba: AssertionError in TestRaising.test_assert_statement_objmode [amd64, i386, arm64]

2017-05-27 Thread Daniel Stender
Source: numba
Version: 0.33.0-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=numba=arm64=0.33.0-1=1495916190=0
https://buildd.debian.org/status/fetch.php?pkg=numba=i386=0.33.0-1=1495914429=0

This test failure appears:


__ TestRaising.test_assert_statement_objmode ___

self = 

def test_assert_statement_objmode(self):
>   self.check_assert_statement(flags=force_pyobj_flags)

numba/tests/test_exceptions.py:196: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
numba/tests/test_exceptions.py:193: in check_assert_statement
self.assertEqual(str(cm.exception), "bar")
E   AssertionError: 'bar\nassert 2 == 1' != 'bar'


-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
http://www.danielstender.com/



Bug#863503: numba: numba/compiler.py:243: ConstantInferenceError [amd64, i386, arm64]

2017-05-27 Thread Daniel Stender
Source: numba
Version: 0.33.0-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=numba=i386=0.33.0-1=1495914429=0
https://buildd.debian.org/status/fetch.php?pkg=numba=arm64=0.33.0-1=1495916190=0

This failure appears among the tests several times:


__ TestRaising.test_assert_statement_nopython __

self = 

def test_assert_statement_nopython(self):
>   self.check_assert_statement(flags=no_pyobj_flags)

numba/tests/test_exceptions.py:199: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
numba/tests/test_exceptions.py:188: in check_assert_statement
cres = compile_isolated(pyfunc, (types.int32,), flags=flags)
numba/compiler.py:150: in compile_isolated
flags, locals)
numba/compiler.py:704: in compile_extra
return pipeline.compile_extra(func)
numba/compiler.py:357: in compile_extra
return self._compile_bytecode()
numba/compiler.py:665: in _compile_bytecode
return self._compile_core()
numba/compiler.py:652: in _compile_core
res = pm.run(self.status)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = 
status = fail_reason=None, can_fallback=False, can_giveup=False

def run(self, status):
assert self._finalized, "PM must be finalized before run()"
res = None
for pipeline_name in self.pipeline_order:
event(pipeline_name)
is_final_pipeline = pipeline_name == self.pipeline_order[-1]
for stage, stage_name in self.pipeline_stages[pipeline_name]:
try:
event(stage_name)
stage()
except _EarlyPipelineCompletion as e:
return e.result
except BaseException as e:
msg = "Failed at %s (%s)" % (pipeline_name, stage_name)
patched_exception = self._patch_error(msg, e)
# No more fallback pipelines?
if is_final_pipeline:
>   raise patched_exception
E   ConstantInferenceError: Caused By:
E   Traceback (most recent call last):
E File 
"/<>/.pybuild/pythonX.Y_2.7/build/numba/compiler.py", line 235, in 
run
E   stage()
E File 
"/<>/.pybuild/pythonX.Y_2.7/build/numba/compiler.py", line 466, in 
stage_generic_rewrites
E   self, self.func_ir)
E File 
"/<>/.pybuild/pythonX.Y_2.7/build/numba/rewrites/registry.py", 
line 71, in apply
E   pipeline.calltypes)
E File 
"/<>/.pybuild/pythonX.Y_2.7/build/numba/rewrites/static_raise.py", 
line 43, in match
E   const = interp.infer_constant(inst.exception)
E File 
"/<>/.pybuild/pythonX.Y_2.7/build/numba/ir.py", line 873, in 
infer_constant
E   return self._consts.infer_constant(name)
E File 
"/<>/.pybuild/pythonX.Y_2.7/build/numba/consts.py", line 44, in 
infer_constant
E   raise exc(*args)
E   ConstantInferenceError: constant inference not possible 
for call $108.23(@py_format6)
E   
E   Failed at nopython (nopython rewrites)
E   constant inference not possible for call 
$108.23(@py_format6)

numba/compiler.py:243: ConstantInferenceError


-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
http://www.danielstender.com/



Bug#863501: numba: RuntimeError: cannot cache function 'simple_usecase' [amd64, i386, arm64]

2017-05-27 Thread Daniel Stender
Source: numba
Version: 0.33.0-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=numba=i386=0.33.0-1=1495914429=0
https://buildd.debian.org/status/fetch.php?pkg=numba=arm64=0.33.0-1=1495916190=0

This failure appeared in the tests:


_ TestCache.test_non_creatable_pycache _

self = 

@unittest.skipIf(os.name == "nt",
 "cannot easily make a directory read-only on Windows")
def test_non_creatable_pycache(self):
# Make it impossible to create the __pycache__ directory
old_perms = os.stat(self.tempdir).st_mode
os.chmod(self.tempdir, 0o500)
self.addCleanup(os.chmod, self.tempdir, old_perms)

>   self._test_pycache_fallback()

numba/tests/test_dispatcher.py:954: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
numba/tests/test_dispatcher.py:926: in _test_pycache_fallback
mod = self.import_module()
numba/tests/test_dispatcher.py:623: in import_module
mod = import_dynamic(self.modname)
numba/tests/support.py:527: in import_dynamic
__import__(modname)
/tmp/numba-tests.1000/test_cache-jXZpdc/dispatcher_caching_test_fodder.py:19: 
in 
@jit(cache=True, nopython=True)
numba/decorators.py:175: in wrapper
disp.enable_caching()
numba/dispatcher.py:490: in enable_caching
self._cache = FunctionCache(self.py_func)
numba/caching.py:594: in __init__
self._impl = self._impl_class(py_func)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = 
py_func = 

def __init__(self, py_func):
self._is_closure = bool(py_func.__closure__)
self._lineno = py_func.__code__.co_firstlineno
# Get qualname
try:
qualname = py_func.__qualname__
except AttributeError:
qualname = py_func.__name__
# Find a locator
source_path = inspect.getfile(py_func)
for cls in self._locator_classes:
locator = cls.from_function(py_func, source_path)
if locator is not None:
break
else:
raise RuntimeError("cannot cache function %r: no locator available "
>  "for file %r" % (qualname, source_path))
E   RuntimeError: cannot cache function 'simple_usecase': no locator 
available for file 
'/tmp/numba-tests.1000/test_cache-jXZpdc/dispatcher_caching_test_fodder.py'

numba/caching.py:330: RuntimeError


-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
http://www.danielstender.com/



Bug#855577: numba: FTBFS: several tests fail

2017-05-27 Thread Daniel Stender
For the latest upload (0.33.0 in experimental), the tests have been failsafed
again so that there are even packages building to try out.

Bug reports on the individual test failures and other remaining things to fix
are coming up.

Failsafe is going to be removed again when the package hits unstable.

DS

-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
http://www.danielstender.com/



Bug#858189: marked as pending

2017-04-05 Thread Daniel Stender
tag 858189 pending
thanks

Hello,

Bug #858189 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:

https://anonscm.debian.org/cgit/collab-maint/execnet.git/commit/?id=667a3a9

---
commit 667a3a9cd54a9b9530cf43b31b89625a114bc3df
Author: Daniel Stender <sten...@debian.org>
Date:   Wed Apr 5 10:25:20 2017 +0200

add changes from NMU

diff --git a/debian/changelog b/debian/changelog
index d37e07e..44bc19f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+execnet (1.4.1-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Disable tests that are often failing (Closes: #854494, #858189).
+
+ -- Thomas Goirand <z...@debian.org>  Tue, 04 Apr 2017 20:30:05 +
+
 execnet (1.4.1-3) unstable; urgency=medium
 
   * add test_gateway-fix-race-condition.patch (Closes: #840823 [thanks



Bug#854494: marked as pending

2017-04-05 Thread Daniel Stender
tag 854494 pending
thanks

Hello,

Bug #854494 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:

https://anonscm.debian.org/cgit/collab-maint/execnet.git/commit/?id=667a3a9

---
commit 667a3a9cd54a9b9530cf43b31b89625a114bc3df
Author: Daniel Stender <sten...@debian.org>
Date:   Wed Apr 5 10:25:20 2017 +0200

add changes from NMU

diff --git a/debian/changelog b/debian/changelog
index d37e07e..44bc19f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+execnet (1.4.1-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Disable tests that are often failing (Closes: #854494, #858189).
+
+ -- Thomas Goirand <z...@debian.org>  Tue, 04 Apr 2017 20:30:05 +
+
 execnet (1.4.1-3) unstable; urgency=medium
 
   * add test_gateway-fix-race-condition.patch (Closes: #840823 [thanks



Bug#858018: packer: sometimes FTBFS: github.com/mitchellh/packer/version[no test files]

2017-04-02 Thread Daniel Stender
Control: retitle -1 packer: sometimes FTBFS: FAIL 
github.com/mitchellh/packer/packer/rpc

Actually, there's a test failure happening in these cases:


=== RUN   TestPostProcessorRPC
panic: Fail in goroutine after TestMuxBroker has completed

goroutine 308 [running]:
panic(0x87a720, 0xc4201436a0)
/usr/lib/go-1.7/src/runtime/panic.go:500 +0x1a1
testing.(*common).Fail(0xc42016c900)
/usr/lib/go-1.7/src/testing/testing.go:412 +0x11f
testing.(*common).FailNow(0xc42016c900)
/usr/lib/go-1.7/src/testing/testing.go:431 +0x2b
testing.(*common).Fatalf(0xc42016c900, 0x9442f3, 0x7, 0xc42019bf70, 0x1, 0x1)
/usr/lib/go-1.7/src/testing/testing.go:496 +0x83
github.com/mitchellh/packer/packer/rpc.TestMuxBroker.func1(0xc420344a40, 
0xc42016c900)

/<>/packer-0.10.2+dfsg/obj-x86_64-linux-gnu/src/github.com/mitchellh/packer/packer/rpc/
mux_broker_test.go:27 +0x140
created by github.com/mitchellh/packer/packer/rpc.TestMuxBroker

/<>/packer-0.10.2+dfsg/obj-x86_64-linux-gnu/src/github.com/mitchellh/packer/packer/rpc/
mux_broker_test.go:29 +0x281
exit status 2
FAILgithub.com/mitchellh/packer/packer/rpc  0.124s


DS

-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
http://www.danielstender.com/



Bug#858018: packer sometimes FTBFS on arm*: github.com/mitchellh/packer/version[no test files]

2017-04-02 Thread Daniel Stender
Control: retitle ! packer: sometimes FTBFS: 
github.com/mitchellh/packer/version[no test files]

Unfortunately this also happens on other archs:


?   github.com/mitchellh/packer/version [no test files]
dh_auto_test: go test -v -p 1 -timeout 30m github.com/mitchellh/packer {...} 
github.com/mitchellh/packer/version returned exit code 1
debian/rules:16: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>/packer-0.10.2+dfsg'
debian/rules:13: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

Build finished at 2017-04-02T08:06:33Z
{...}
+--+
| Summary  |
+--+

Build Architecture: amd64
Build Type: full
Build-Space: 103936
Build-Time: 110
Distribution: unstable
Fail-Stage: build
Host Architecture: amd64
Install-Time: 58
Job: 
/home/aham/Schreibtisch/projekte/00_debian/pakete/devops/packer/packaging/packer_0.10.2+dfsg-3.dsc
Machine Architecture: amd64
Package: packer
Package-Time: 180
Source-Version: 0.10.2+dfsg-3
Space: 103936
Status: attempted
Version: 0.10.2+dfsg-3


DS

-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
http://www.danielstender.com/



Bug#854494: execnet: testing/test_gateway.py::TestPopenGateway::test_waitclose_on_remote_killed FAILED/PASSEDSegmentation fault

2017-03-19 Thread Daniel Stender
In the test builds for reproducible builds, this repeatedly occurs as segfault:


testing/test_gateway.py::TestPopenGateway::test_waitclose_on_remote_killed 
PASSEDSegmentation fault
E: pybuild pybuild:283: test: plugin custom failed with: exit code=139: 
python3.5 -m pytest -v -x -rs testing/
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.5 returned 
exit code 13


https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/execnet_1.4.1-3.rbuild.log
https://tests.reproducible-builds.org/debian/rbuild/testing/armhf/execnet_1.4.1-3.rbuild.log

DS

-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
LPIC-1 (LPI000329859 64mz6f7kt4)
http://www.danielstender.com/



Bug#854494: execnet: FTBFS randomly (failing tests)

2017-03-08 Thread Daniel Stender
On 08.03.2017 01:01, Santiago Vila wrote:
> severity 854494 serious
> thanks
> 
> Dear maintainer:
> 
> I expected a general guideline from Release Managers regarding
> packages which FTBFS randomly like this one, but that will most surely
> not happen for stretch.
> 
> So, the only guideline I have left is the one expressed by Julien
> Cristau (one of the RMs) in Bug #844264:
> 
> "if the failure rate is low enough I think a lower severity can make
> sense"
> 
> I posted a list of bugs which FTBFS more than 10% of the time and
> several people agreed on -devel that they should be serious and
> maintainers should ask for stretch-ignore tag in case the bug should
> not be RC (most bugs are about failing tests so this should not be
> needed in general).
> 
> In the latest tests I made, this package fails for me more than 61% of
> the time, and it also fails (randomly) in the reproducible builds 
> autobuilders:
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/execnet.html
> 
> (I think this addresses the comment made here by Rebecca: Most probably
> the failures do not have anything to do with my machines being
> single-CPU, as the reproducible builds autobuilders are multi-core).
> 
> This may affect any user trying to build this package (for example, 
> after making a change), our downstreams, and the Security Team once
> that stretch is stable.
> 
> For this reason I'm raising this to serious.
> 
> Sorry for the long explanation.
> 
> Thanks.

... that's o.k. with me. Good work with those "randomly failing" test builds.

DS

-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
http://www.danielstender.com/



Bug#851578: python-numba: fails to install: SyntaxError: invalid syntax

2017-02-17 Thread Daniel Stender
... in.

I'm going to upload this already.

There are a couple of problems left, I'll file bug reports on them so that they 
could be
discussed, focused on if wanted.

DS

-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
http://www.danielstender.com/



Bug#851578: add nmu patch for this bug, however encountered FTBFS due to testsuite failure

2017-02-17 Thread Daniel Stender
On 17.02.2017 16:32, Daniel Stender wrote:
> On 17.02.2017 15:41, lumin wrote:
>> Control: tags -1 +patch
>>
>> Here is an NMU patch for this package. I intended to file an
>> RFS but the debomatic build failure stopped me to do so.
>>
>> The build failure was caused by testsuite failure:
>> http://debomatic-amd64.debian.net/distribution#experimental/numba/0.30.0-2.1/buildlog
> 
> Thanks for the changes. I'll upload anything on this package.

... it would be great if you could/would incorporate your changes, patches etc. 
into
the Git repo.

Thanks,
DS

-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
http://www.danielstender.com/



Bug#851578: add nmu patch for this bug, however encountered FTBFS due to testsuite failure

2017-02-17 Thread Daniel Stender
On 17.02.2017 15:41, lumin wrote:
> Control: tags -1 +patch
> 
> Here is an NMU patch for this package. I intended to file an
> RFS but the debomatic build failure stopped me to do so.
> 
> The build failure was caused by testsuite failure:
> http://debomatic-amd64.debian.net/distribution#experimental/numba/0.30.0-2.1/buildlog

Thanks for the changes. I'll upload anything on this package.

DS

-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
http://www.danielstender.com/



Bug#831541: theano: single GradientError and WrongValues in tests on s390x, ppc64 and sparc

2017-02-14 Thread Daniel Stender
On 14.02.2017 08:43, Rebecca N. Palmer wrote:
> Found the problem: the affected functions ( 
> https://sources.debian.net/src/theano/0.8.2-4/theano/sparse/opt.py/#L862 , 
> https://sources.debian.net/src/theano/0.8.2-4/theano/sparse/opt.py/#L1902 ) 
> cast a pointer-to-intptr_t (64 bit) to a pointer-to-int (32-bit).
> 
> Which isn't just broken on big-endian systems, it's a strict aliasing 
> violation *everywhere* (i.e. technically undefined behaviour with 
> optimization on, which it is by default, though it appears to work in 
> practice).
> 
> (I expect to post a patch tonight: the obvious has a potential overflow 
> issue, and it also needs a c_code_cache_version change to make the fix be 
> used in existing installs).

That would be sensational. #835531 doesn't keep up being RC, that would mean 
that we're through
to Stretch if this bug could be closed. Much thx in advance!

Daniel

-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
http://www.danielstender.com/



Bug#835531: fail of test_csr_correct_output_faster_than_scipy at times (FTBFS)

2017-02-14 Thread Daniel Stender
On 14.02.2017 08:59, Ole Streicher wrote:
> Hi Daniel,
> 
> I don't really see why you declare this failure as "serious". From the
> source (and the bug name), it basically means that theano took a bit
> longer to calculate than scipy for the same calculation. This may depend
> on the scipy version and optimization, and also on the timing (load)
> during the test -- it is calendar time what is taken here.
> 
> IMO, the failure is severity "normal", maybe you could consider
> resetting the severity to this value?
> 
> Best regards
> 
> Ole

Yes, in the meanwhile, I've thought into the same direction. The latest build 
(0.8.2-5~exp1)
succeeded again without this appeared anywhere. I'll do that.

Daniel

-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
http://www.danielstender.com/



Bug#848764: theano: test failures with Numpy 1.12

2017-02-10 Thread Daniel Stender
Thanks for the patch. It solves most of the problems towards Numpy 1.12, but 
from the complete
testsuite 4 errors remain:


ERROR: test_DownsampleFactorMax 
(theano.tensor.signal.tests.test_pool.TestDownsampleFactorMax)
--
Traceback (most recent call last):
  File "/<>/theano/tensor/signal/tests/test_pool.py", line 189, in 
test_DownsampleFactorMax
mode=mode)
  File "/<>/theano/tensor/signal/tests/test_pool.py", line 39, in 
numpy_max_pool_2d
output_val = numpy.zeros(out_shp)
TypeError: 'float' object cannot be interpreted as an integer

==
ERROR: test_max_pool_2d_2D 
(theano.tensor.signal.tests.test_pool.TestDownsampleFactorMax)
--
Traceback (most recent call last):
  File "/<>/theano/tensor/signal/tests/test_pool.py", line 664, in 
test_max_pool_2d_2D
mode=mode)
  File "/<>/theano/tensor/signal/tests/test_pool.py", line 39, in 
numpy_max_pool_2d
output_val = numpy.zeros(out_shp)
TypeError: 'float' object cannot be interpreted as an integer

==
ERROR: test_max_pool_2d_3D 
(theano.tensor.signal.tests.test_pool.TestDownsampleFactorMax)
--
Traceback (most recent call last):
  File "/<>/theano/tensor/signal/tests/test_pool.py", line 710, in 
test_max_pool_2d_3D
mode)
  File "/<>/theano/tensor/signal/tests/test_pool.py", line 39, in 
numpy_max_pool_2d
output_val = numpy.zeros(out_shp)
TypeError: 'float' object cannot be interpreted as an integer

==
ERROR: test_max_pool_2d_6D 
(theano.tensor.signal.tests.test_pool.TestDownsampleFactorMax)
--
Traceback (most recent call last):
  File "/<>/theano/tensor/signal/tests/test_pool.py", line 737, in 
test_max_pool_2d_6D
mode=mode)
  File "/<>/theano/tensor/signal/tests/test_pool.py", line 39, in 
numpy_max_pool_2d
output_val = numpy.zeros(out_shp)
TypeError: 'float' object cannot be interpreted as an integer

--
Ran 2995 tests in 6109.672s

FAILED (SKIP=113, errors=4)


DS

-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
http://www.danielstender.com/



Bug#834910: marked as pending

2017-02-08 Thread Daniel Stender
On 08.02.2017 16:15, Ole Streicher wrote:
> tag 834910 pending
> thanks
> 
> Hello,
> 
> Bug #834910 reported by you has been fixed in the Git repository. You can
> see the changelog below, and you can check the diff of the fix at:
> 
> http://git.debian.org/?p=collab-maint/lasagne.git;a=commitdiff;h=d663c1d
> 
> ---
> commit d663c1de9fd04ecfdf2c287a690e97e104902c6a
> Author: Ole Streicher 
> Date:   Wed Feb 8 16:14:41 2017 +0100
> 
> Use inspect.signature instead of inspect.getargspec if possible
> 
> Closes: #834910
> 
> diff --git a/debian/changelog b/debian/changelog
> index 4031946..e22634e 100644
> --- a/debian/changelog
> +++ b/debian/changelog
> @@ -1,3 +1,10 @@
> +lasagne (0.1+git20160728.8b66737-2) UNRELEASED; urgency=medium
> +
> +  * Use inspect.signature instead of inspect.getargspec if possible
> +(Closes: #834910)
> +
> + -- Ole Streicher   Wed, 08 Feb 2017 16:10:28 +0100
> +
>  lasagne (0.1+git20160728.8b66737-1) unstable; urgency=medium
>  
>* Initial release (Closes: #818641).

Thank you very much. I'll upload this ASAP.

DS

-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
http://www.danielstender.com/



Bug#834910: lasagne: two tests failing on Python 3.5

2017-02-08 Thread Daniel Stender
On 08.02.2017 13:54, Sandro Tosi wrote:
> control: reopen -1
> 
> not so fast..
> 
> On Wed, Feb 8, 2017 at 4:17 AM, Ole Streicher  wrote:
>> Hi Daniel, Sandro,
>>
>> I tried to reproduce the bug and could not get the failure with the
>> latest unstable (Python revision 3.5.3-1). So, I would recommend to
>> either close the bug as unreproducible, or at least to downgrade the
>> severity.
> 
> i was able to reproduce it just now in a clean pbuilder chroot, build
> log attached
> 
> this is still an RC bug affecting stretch

If that remains being a problem: there is somebody interested in taking over the
maintenance for Theano. Maybe she's interested in fixing this bug, too. I'll 
ask.

Let's wait a couple of days longer before removing this package. AUTORM is/was 
on
02-23, not longer than that, though ...

DS

-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
http://www.danielstender.com/



Bug#834910: lasagne: two tests failing on Python 3.5

2017-02-08 Thread Daniel Stender
On 08.02.2017 10:17, Ole Streicher wrote:
> Hi Daniel, Sandro,
> 
> I tried to reproduce the bug and could not get the failure with the
> latest unstable (Python revision 3.5.3-1). So, I would recommend to
> either close the bug as unreproducible, or at least to downgrade the
> severity.
> 
> IMO the package is worth to be kept in Stretch.
> 
> If you don't veto, I would just close the bug in a week.
> 
> Best regards
> 
> Ole

All right with me ...

Best,
Dan

-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
http://www.danielstender.com/



Bug#852048: pycodestyle >= 2.1.0 breaks prospector 0.12.4,,version graph

2017-02-06 Thread Daniel Stender
I've got deeper into it now. I think that was pinned by mistake, but pydocstyle 
was mend, the corresponding changelog
entry is on that. I've commented on the commit [1], waiting for a reaction ...

A simple patch for setup.py which removes the pinning would do it, because 
actually there are no API changes
in pycodestyle >= 2.1.0. I've tested that against pycodestyle 2.2.0-2 
(currently in the archive) and everything
works. I'll upload this shortly to catch the AUTORM.

DS

[1] 
https://github.com/landscapeio/prospector/commit/95e09816534853616d42877dcb8b9dc0f71a38e8

-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
http://www.danielstender.com/



Bug#827068: m2crypto: diff for NMU version 0.24.0-1.1

2017-02-05 Thread Daniel Stender
On 05.02.2017 15:08, Sebastian Andrzej Siewior wrote:
> Control: tags 827068 + patch
> Control: tags 827068 + pending
> 
> Dear maintainer,
> 
> I've prepared an NMU for m2crypto (versioned as 0.24.0-1.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer. I am also going to switch m2ext to
> libssl1.0-dev.
> 
> Regards.
> Sebastian

No, that's all right with me. Thx for solving the issue. I'll take care of the 
unblock
request ...

Best,
DS

-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
http://www.danielstender.com/



Bug#852048: pycodestyle >= 2.1.0 breaks prospector 0.12.4

2017-02-01 Thread Daniel Stender
... please hang on, I'm going to provide a patch.

DS

-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
http://www.danielstender.com/



Bug#827068: m2crypto: doesn't work together with OpenSSL 1.1 (API changes)

2017-02-01 Thread Daniel Stender
On 31.01.2017 21:52, Sebastian Andrzej Siewior wrote:
> On 2016-11-15 12:36:09 [+0100], Daniel Stender wrote:
>> On Mon, 14 Nov 2016 19:52:31 +0100 Daniel Stender <deb...@danielstender.com> 
>> wrote:
>>> The diff doesn't work like that on the upstream code in the archive
>>
>> ... the same is true for 0.25.1.
>>
>> I'm on it.
> 
> Should I take 0.25.1 and cherry-pick the patches or B-D on openssl 1.0
> for Stretch?
> 
>> DS
>>
> 
> Sebastian

Hi Sebastian,

... if you would like to write/provide a patch for the package (cherry pick 
from upstream)
that would be very welcome. On the other hand, if b-dep it down on openssl1.0 
it's also
all right with me.

Thank you!

Daniel

-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
http://www.danielstender.com/



Bug#853261: [pkg-go] Bug#853261: golang-github-masterzen-winrm: FTBFS when built with dpkg-buildpackage -A

2017-01-30 Thread Daniel Stender
All right. Thx for the bug report & patch.

Best,
DS

On 30.01.2017 22:11, Santiago Vila wrote:
> Package: src:golang-github-masterzen-winrm
> Version: 0.0~git20160323.0752679-2
> Severity: serious
> Tags: patch
> 
> Dear maintainer:
> 
> I tried to build this package in stretch with "dpkg-buildpackage -A"
> but it failed:
> 
> 
> [...]
>  debian/rules build-indep
> dh build-indep --buildsystem=golang --with=golang
>dh_testdir -i -O--buildsystem=golang
>dh_update_autotools_config -i -O--buildsystem=golang
>dh_auto_configure -i -O--buildsystem=golang
>dh_auto_build -i -O--buildsystem=golang
>   go install -v -p 1 github.com/masterzen/winrm 
> github.com/masterzen/winrm/soap github.com/masterzen/winrm/winrm
> github.com/masterzen/simplexml/dom
> github.com/masterzen/xmlpath
> github.com/masterzen/winrm/soap
> github.com/nu7hatch/gouuid
> github.com/masterzen/winrm/winrm
> github.com/masterzen/winrm
>dh_auto_test -i -O--buildsystem=golang
>   go test -v -p 1 github.com/masterzen/winrm 
> github.com/masterzen/winrm/soap github.com/masterzen/winrm/winrm
> ? github.com/masterzen/winrm  [no test files]
> === RUN   Test
> OK: 1 passed
> --- PASS: Test (0.00s)
> === RUN   TestAddUsualNamespaces
> --- PASS: TestAddUsualNamespaces (0.00s)
> === RUN   TestSetTo
> --- PASS: TestSetTo (0.00s)
> PASS
> okgithub.com/masterzen/winrm/soap 0.006s
> === RUN   Test
> OK: 27 passed
> --- PASS: Test (3.03s)
> PASS
> okgithub.com/masterzen/winrm/winrm3.039s
>  fakeroot debian/rules binary-indep
> dh binary-indep --buildsystem=golang --with=golang
>dh_testroot -i -O--buildsystem=golang
>dh_prep -i -O--buildsystem=golang
>dh_auto_install -i -O--buildsystem=golang
>   mkdir -p 
> /<>/golang-github-masterzen-winrm-0.0\~git20160323.0752679/debian/tmp/usr
>   cp -r bin 
> /<>/golang-github-masterzen-winrm-0.0\~git20160323.0752679/debian/tmp/usr
>   mkdir -p 
> /<>/golang-github-masterzen-winrm-0.0\~git20160323.0752679/debian/tmp/usr/share/gocode/src/github.com/masterzen/winrm
>   cp -r -T src/github.com/masterzen/winrm 
> /<>/golang-github-masterzen-winrm-0.0\~git20160323.0752679/debian/tmp/usr/share/gocode/src/github.com/masterzen/winrm
>debian/rules override_dh_install
> make[1]: Entering directory '/<>'
> dh_install
> mv -v debian/winrm/usr/bin/winrm debian/winrm/usr/bin/winrm-go
> mv: cannot stat 'debian/winrm/usr/bin/winrm': No such file or directory
> debian/rules:9: recipe for target 'override_dh_install' failed
> make[1]: *** [override_dh_install] Error 1
> make[1]: Leaving directory '/<>'
> debian/rules:6: recipe for target 'binary-indep' failed
> make: *** [binary-indep] Error 2
> dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit 
> status 2
> 
> 
> This happens because we are creating arch-independent packages only,
> so debian/winrm/[...] does not exist, as "winrm" is Arch:any.
> 
> Trivial (but untested) patch follows.
> 
> Thanks.
> 
> --- a/debian/rules
> +++ b/debian/rules
> @@ -5,7 +5,7 @@
>  %:
>   dh $@ --buildsystem=golang --with=golang
>  
> -override_dh_install:
> +override_dh_install-arch:
>   dh_install
>   mv -v debian/winrm/usr/bin/winrm debian/winrm/usr/bin/winrm-go
>  
> 
> ___
> Pkg-go-maintainers mailing list
> pkg-go-maintain...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
> 
> 


-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
http://www.danielstender.com/



Bug#853135: packer: FTBFS on arm archs: TestConfigInstantiatesCorrectAzureEnvironment fails

2017-01-29 Thread Daniel Stender
Package: packer
Version: 0.10.2+dfsg-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Since the tests are not fail safed anymore the package starts to FTBFS on arm64,
armel and armhf. There is a single test failure:


=== RUN   TestConfigInstantiatesCorrectAzureEnvironment
SIGQUIT: quit
PC=0x558bd125c4 m=0

goroutine 0 [idle]:
runtime.futex(0x558c4954f0, 0x0, 0x0, 0x0, 0x44, 0x558bcdfbe0, 
0x558c4947b0, 0x0, 0x0, 0x558bcdfc34, ...)
/usr/lib/go-1.7/src/runtime/sys_linux_arm64.s:312 +0x1c
runtime.futexsleep(0x558c4954f0, 0x0, 0x)
/usr/lib/go-1.7/src/runtime/os_linux.go:45 +0x58
runtime.notesleep(0x558c4954f0)
/usr/lib/go-1.7/src/runtime/lock_futex.go:145 +0xac
runtime.stopm()
/usr/lib/go-1.7/src/runtime/proc.go:1594 +0x10c
runtime.findrunnable(0x4420023500, 0x0)
/usr/lib/go-1.7/src/runtime/proc.go:2021 +0x818
runtime.schedule()
/usr/lib/go-1.7/src/runtime/proc.go:2120 +0x2c0
runtime.park_m(0x4420196340)
/usr/lib/go-1.7/src/runtime/proc.go:2183 +0x170
runtime.mcall(0x558c494b00)
/usr/lib/go-1.7/src/runtime/asm_arm64.s:177 +0x50

goroutine 1 [chan receive, 6 minutes]:
testing.(*T).Run(0x442009a300, 0x558c2328fb, 0x2d, 0x558c2776e8, 0x1)
/usr/lib/go-1.7/src/testing/testing.go:647 +0x348
testing.RunTests.func1(0x442009a3c0)
/usr/lib/go-1.7/src/testing/testing.go:793 +0xc0
testing.tRunner(0x442009a3c0, 0x442004bd90)
/usr/lib/go-1.7/src/testing/testing.go:610 +0xb8
testing.RunTests(0x558c277e48, 0x558c46c840, 0x50, 0x50, 0x558c465301)
/usr/lib/go-1.7/src/testing/testing.go:799 +0x3d0
testing.(*M).Run(0x442004bef0, 0x558c2098a0)
/usr/lib/go-1.7/src/testing/testing.go:743 +0xc4
main.main()
github.com/mitchellh/packer/builder/azure/arm/_test/_testmain.go:212 
+0x118

goroutine 17 [syscall, 9 minutes, locked to thread]:
runtime.goexit()
/usr/lib/go-1.7/src/runtime/asm_arm64.s:983 +0x4

goroutine 20 [syscall, 9 minutes]:
os/signal.signal_recv(0x0)
/usr/lib/go-1.7/src/runtime/sigqueue.go:116 +0x204
os/signal.loop()
/usr/lib/go-1.7/src/os/signal/signal_unix.go:22 +0x18
created by os/signal.init.1
/usr/lib/go-1.7/src/os/signal/signal_unix.go:28 +0x3c

goroutine 237 [runnable]:
math/big.mulAddWWW_g(0xcdfe88c70f0ad9f3, 0x38f2c68b683e2e89, 
0xebaa88fc6987ba83, 0xc0c1b06cc1ae881, 0xf2ae9b0780aa6147)
/usr/lib/go-1.7/src/math/big/arith.go:72
math/big.addMulVVW_g(0x4420456280, 0x10, 0x26, 0x44203ef2c0, 0x10, 0x14, 
0x38f2c68b683e2e89, 0xc0c1b06cc1ae882)
/usr/lib/go-1.7/src/math/big/arith.go:292 +0xa0
math/big.nat.montgomery(0x4420456280, 0x10, 0x26, 0x44204f2280, 0x10, 0x14, 
0x44204f2280, 0x10, 0x14, 0x44203ef2c0, ...)
/usr/lib/go-1.7/src/math/big/nat.go:226 +0x18c
math/big.nat.expNNMontgomery(0x4420456280, 0x10, 0x26, 0x44204f21e0, 0x10, 
0x14, 0x44204f20a0, 0x10, 0x14, 0x44203ef2c0, ...)
/usr/lib/go-1.7/src/math/big/nat.go:1141 +0x988
math/big.nat.expNN(0x44204f2280, 0x10, 0x14, 0x44204f21e0, 0x10, 0x14, 
0x44204f20a0, 0x10, 0x14, 0x44203ef2c0, ...)
/usr/lib/go-1.7/src/math/big/nat.go:955 +0x66c
math/big.nat.probablyPrime(0x44203ef2c0, 0x10, 0x14, 0x14, 0x44203ef2c0)
/usr/lib/go-1.7/src/math/big/nat.go:1242 +0x740
math/big.(*Int).ProbablyPrime(0x44203b9b80, 0x14, 0x442032d5f0)
/usr/lib/go-1.7/src/math/big/int.go:563 +0xe4
crypto/rand.Prime(0x558c46f480, 0x442007c270, 0x400, 0x44203b9b80, 0x0, 0x0)
/usr/lib/go-1.7/src/crypto/rand/util.go:99 +0x454
crypto/rsa.GenerateMultiPrimeKey(0x558c46f480, 0x442007c270, 0x2, 0x800, 
0x44201b1300, 0x0, 0x0)
/usr/lib/go-1.7/src/crypto/rsa/rsa.go:238 +0x1bc
crypto/rsa.GenerateKey(0x558c46f480, 0x442007c270, 0x800, 0xb, 0x0, 0x0)
/usr/lib/go-1.7/src/crypto/rsa/rsa.go:195 +0x44
github.com/mitchellh/packer/builder/azure/arm.NewOpenSshKeyPairWithSize(0x800, 
0xa, 0x0, 0x0)

/«BUILDDIR»/packer-0.10.2+dfsg/obj-aarch64-linux-gnu/src/github.com/mitchellh/packer/builder/azure/arm/openssh_key_pair.go:31
 +0x4c
github.com/mitchellh/packer/builder/azure/arm.NewOpenSshKeyPair(0x44201797a0, 
0x0, 0x0)

/«BUILDDIR»/packer-0.10.2+dfsg/obj-aarch64-linux-gnu/src/github.com/mitchellh/packer/builder/azure/arm/openssh_key_pair.go:27
 +0x2c
github.com/mitchellh/packer/builder/azure/arm.setSshValues(0x44203c4a80, 0x0, 
0x0)

/«BUILDDIR»/packer-0.10.2+dfsg/obj-aarch64-linux-gnu/src/github.com/mitchellh/packer/builder/azure/arm/config.go:270
 +0x414
github.com/mitchellh/packer/builder/azure/arm.newConfig(0x442032dd70, 0x2, 0x2, 
0x442032dd30, 0x0, 0x0, 0x0, 0x0, 0x0)

/«BUILDDIR»/packer-0.10.2+dfsg/obj-aarch64-linux-gnu/src/github.com/mitchellh/packer/builder/azure/arm/config.go:226
 +0x27c
github.com/mitchellh/packer/builder/azure/arm.TestConfigInstantiatesCorrectAzureEnvironment(0x442009a300)


Bug#852305: depends on non existing package libblosc1

2017-01-26 Thread Daniel Stender
Control: tags -1 + unreproducible

Tell me if I miss something ... otherwise I'm going to close this issue in the 
next days.

Anyway, Bcolz is in unstable now.

DS

-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
LPIC-1 (LPI000329859 64mz6f7kt4)
http://www.danielstender.com/



Bug#852307: bcolz: test_leftover_ptr_with_statement_create_open fails on s390x, powerpc

2017-01-23 Thread Daniel Stender
Package: bcolz
Version: 1.1.0+ds1-2
Severity: serious
Justification: fails to build from source
Control: forwarded -1 https://github.com/Blosc/bcolz/issues/329

There is a test failure on s390x and powerpc [1]:


==
FAIL: test_leftover_ptr_create_flush_open 
(bcolz.tests.test_carray.LeftoverDiskTest)
--
Traceback (most recent call last):
  File "bcolz/tests/test_carray.py", line 2516, in 
test_leftover_ptr_create_flush_open
self.assertEqual((n_chunks * chunklen) + i, out.value)
AssertionError: 100 != 0

==
FAIL: test_leftover_ptr_with_statement_create_open 
(bcolz.tests.test_carray.LeftoverDiskTest)
--
Traceback (most recent call last):
  File "bcolz/tests/test_carray.py", line 2533, in 
test_leftover_ptr_with_statement_create_open
self.assertEqual((n_chunks * chunklen) + i, out.value)
AssertionError: 100 != 0

--
Ran 1254 tests in 5.247s

FAILED (failures=2, skipped=156)


DS

[1] https://buildd.debian.org/status/package.php?p=bcolz=experimental


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)



Bug#852305: depends on non existing package libblosc1

2017-01-23 Thread Daniel Stender
On 23.01.2017 14:02, Martin Steigerwald wrote:
> Package: python-bcolz
> Version: 1.1.0+ds1-2
> Severity: serious
> 
> Dear Maintainer,
> 
> on searching what to install to make
> 
> […]/pkg-fio> tools/hist/fiologparser_hist.py
> Traceback (most recent call last):
>   File "tools/hist/fiologparser_hist.py", line 18, in 
> import pandas
> ImportError: No module named pandas
> 
> work, I came across python-bcolz.
> 
> Yet this is not installable:
> 
> […]~> LANG=C sudo apt install python-bcolz
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  python-bcolz : Depends: libblosc1 (>= 1.9.0) but it is not installable
> Recommends: python-numexpr but it is not installable
> E: Unable to correct problems, you have held broken packages.
> 
> 
> […]~> LANG=C apt-cache policy libblosc1
> libblosc1:
>   Installed: (none)
>   Candidate: (none)
>   Version table:
> 
> […]~> LANG=C apt-cache policy python-numexpr
> python-numexpr:
>   Installed: (none)
>   Candidate: (none)
>   Version table:
> 
> I see no bcolz related upload in 2017, so this issue may be there for quite
> some time already.
> 
> Thanks,
> Martin

Hi Martin,

yep, bcolz won't make it into Debian 9 (too late to fix #329 [1]), but 
libblosc1 should be available [2] ...

Daniel

[1] https://github.com/Blosc/bcolz/issues/329

[2] https://packages.qa.debian.org/c/c-blosc.html


-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
LPIC-1 (LPI000329859 64mz6f7kt4)
http://www.danielstender.com/



Bug#852048: prospector: dependencies can't be satisfied in testing/sid

2017-01-22 Thread Daniel Stender
Control: retitle -1 pycodestyle >= 2.1.0 breaks prospector 0.12.4

[CC-ing the pycodestyle maintainers]

OUCH!

In the upstream repo it's said that there are API changes in pycodestyle > 2.0.0
= 2.1.0 [1], and therefore 2.0.0 is pinned. I've missed that, and also the 
DEP-8 tests
of prospector kept on succeeding.

I'm studying the CHANGES of pycodestyle [2] right now ... I think it's "change 
all references
... to say pycodestyle; #530".

BTW, there are API changes in pydocstyle (formerly pep257) > 1.0.0, that's also 
pinned and
I didn't updated that yet for that reason [3].

Daniel

[1] 
https://github.com/landscapeio/prospector/commit/95e09816534853616d42877dcb8b9dc0f71a38e8

[2] https://github.com/PyCQA/pycodestyle/blob/master/CHANGES.txt

[3] https://bugs.debian.org/846591 (pydocstyle: newer version available)

-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
LPIC-1 (LPI000329859 64mz6f7kt4)
http://www.danielstender.com/



Bug#840823: marked as pending

2017-01-22 Thread Daniel Stender
tag 840823 pending
thanks

Hello,

Bug #840823 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:

http://git.debian.org/?p=collab-maint/execnet.git;a=commitdiff;h=cb7c537

---
commit cb7c53771f95c073bb945e54dd52af1f3983e9ba
Author: Daniel Stender <sten...@debian.org>
Date:   Sun Jan 22 16:00:41 2017 +0100

add test_gateway-fix-race-condition.patch

diff --git a/debian/changelog b/debian/changelog
index cfb08a8..461e30f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,9 +1,11 @@
 execnet (1.4.1-3) UNRELEASED; urgency=medium
 
+  * add test_gateway-fix-race-condition.patch (Closes: #840823 [thanks
+to Andreas Cadhalpun].
   * deb/clean: add .cache/.
   * run DEP-8 tests for Python3 without warnings (Closes: #849466).
 
- -- Daniel Stender <sten...@debian.org>  Fri, 13 Jan 2017 00:18:32 +0100
+ -- Daniel Stender <sten...@debian.org>  Sun, 22 Jan 2017 15:59:28 +0100
 
 execnet (1.4.1-2) unstable; urgency=medium
 



Bug#840823: execnet test failures

2017-01-22 Thread Daniel Stender
On 22.01.2017 13:54, Andreas Cadhalpun wrote:
> I think the answer is that you were lucky. ;)
> The problem can be reproduced by running:
> $ python -m pytest -v -x -rs testing/test_gateway.py
> 
> I did that 100 times and it failed 78 times, working only 22 times.
> 
> The failing test contains:
> for i in range(10):
> status = gw.remote_status()
> if status.numexecuting == 0:
> break
> else:
> pytest.fail("did not get correct remote status")
> 
> Apparently there is a race condition, so it is tried 10 times.
> However, it is tried in a tight loop, thus not much time passes
> between the first and the last try. Making it sleep inside the
> loop helps.
> 
> There is a similar construct in test_status_with_threads,
> which fails in a similar way, but after changing both to wait
> a bit (with attached patch), the test succeeded 100 times
> for 100 tries.

Hi Andreas,

... that looks very good, ♪thank you♪ very much!

Daniel

-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
LPIC-1 (LPI000329859 64mz6f7kt4)
http://www.danielstender.com/



Bug#852072: packer: build time tests are failing

2017-01-21 Thread Daniel Stender
Package: packer
Version: 0.10.2+dfsg-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

dh_auto_test is currently failsafed because the tests aren't passing through,
there are some failures on missing test-fixtures which appear to be missing
in the tarball. But for the release the tests shouldn't be failsafed.

DS

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages packer depends on:
ii  libc6  2.24-8

Versions of packages packer recommends:
pn  docker.io  
ii  qemu   1:2.7+dfsg-3+b1

Versions of packages packer suggests:
ii  ansible  2.2.0.0-1
pn  chef 

-- no debconf information



Bug#852048: prospector: dependencies can't be satisfied in testing/sid

2017-01-20 Thread Daniel Stender
On 21.01.2017 06:22, Rogério Brito wrote:
> Control: severity 852048 grave
> Control: retitle 852048 prospector: dependencies can't be satisfied in 
> testing/sid
> 
> Hi, Daniel.
> 
> On Jan 21 2017, Rogério Brito wrote:
>> I have used prospector successfully in the past, but I can't now, as it
>> seems that the dependencies declared are not tight enough.
> (...)
> 
> After reading the messages a bit more closely, I saw that both testing and
> sid have pycodestyle == 2.2.0, while prospector has a strictly equal (==)
> dependency on pycodestyle 2.0.0.
> 
> This means that this dependency can't be satisfied in testing nor in sid,
> and, therefore, I'm marking this as an RC bug.
> 
> 
> Thanks,

Ups, that's not right. The dep in control is unversioned, but the one in 
setup.py isn't.
I'll patch and forward that shortly.

BTW, the same for pydocstyle, but that one is in the archive (and an update 
would break
current Prospector).

Best,
Daniel

-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
LPIC-1 (LPI000329859 64mz6f7kt4)
http://www.danielstender.com/



Bug#848234: txwinrm,winrm: error when trying to install together

2017-01-19 Thread Daniel Stender
On Thu, 5 Jan 2017 21:40:12 + Christopher Hoskin 
 wrote:
> Dear Dan,
> 
> Thanks for getting in touch - sorry for not replying sooner. "winrm"
> is the name of a Microsoft Windows command, so users might expect a
> Linux command with the same name to perform a similar function. I'm
> not familiar with what the command in your package does, and it's a
> while since I did the original txwinrm packaging so I'm not sure off
> hand which of our commands is closer to the Windows winrm.
> 
> I'll try to find some time in the next week or so to refresh my memory
> of the details, and consider what an appropriate name for the command
> in my package would be.
> 
> Hope that's soon enough?
> 
> Thanks.
> 
> Christopher

... I've cleared that problem now by renaming the binary in my package.

Please add a Conflicts against winrm_0.0~git20160323.0752679-1.

DS

-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
LPIC-1 (LPI000329859 64mz6f7kt4)
http://www.danielstender.com/



Bug#848764: theano: FTBFS: Test failures

2017-01-17 Thread Daniel Stender
Control: retitle -1 test failures with Numpy 1.12

This is been working on upstream [1], marked as being a cornerstone for release 
9.0.
A partly fix has become available recently [2], but some failures remains.

DS

[1] https://github.com/Theano/Theano/issues/5396 (Make Theano support numpy 
1.12)

[2] https://github.com/Theano/Theano/pull/5406

-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
LPIC-1 (LPI000329859 64mz6f7kt4)
http://www.danielstender.com/



signature.asc
Description: OpenPGP digital signature


Bug#846951: execnet: testing/test_gateway.py::TestTracing::test_popen_stderr_tracing FAILEDexecnet: testing/test_gateway.py::TestTracing::test_popen_stderr_tracing FAILEDexecnet: testing/test_gateway.

2017-01-12 Thread Daniel Stender
Control: severity -1 important

This appeared once in reproducible builds CI, but currently not again. Hard to 
reproduce, any comments
welcome. However, I'm lowering the severity of this bug report.

DS

-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
LPIC-1 (LPI000329859 64mz6f7kt4)
http://www.danielstender.com/



signature.asc
Description: OpenPGP digital signature


Bug#846952: execnet: testing/test_channel.py::TestStringCoerce::test_2to3 FAILED

2017-01-12 Thread Daniel Stender
Control: severity -1 important

Like #840466 this is a test failure which appears only in DEP-8 testing. 
Furthermore, it's
hard to reproduce, local autopkgtesting succeeds [1] (gets skipped in a Python2 
environment).
This shouldn't be RC.

[1] http://www.danielstender.com/uploads/execnet-local-dep8.txt

-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
LPIC-1 (LPI000329859 64mz6f7kt4)
http://www.danielstender.com/



signature.asc
Description: OpenPGP digital signature


Bug#849675: pytest-httpbin: ImportError pytest_httpbin/certs': missing __init__.py

2016-12-29 Thread Daniel Stender
Source: pytest-httpbin
Version: 0.2.3-1
Severity: grave
Justification: renders package unusable

Pytest actually can't use the plugin:


/usr/lib/python2.7/dist-packages/pytest_httpbin/plugin.py:4: ImportWarning: Not 
importing directory '/usr/lib/python2.7/dist-packages/pytest_httpbin/certs': 
missing __init__.py
  from . import serve, certs


The same is true for the Python3 package:


/.
/usr
/usr/lib
/usr/lib/python3
/usr/lib/python3/dist-packages
/usr/lib/python3/dist-packages/pytest_httpbin
/usr/lib/python3/dist-packages/pytest_httpbin/__init__.py
/usr/lib/python3/dist-packages/pytest_httpbin/certs
/usr/lib/python3/dist-packages/pytest_httpbin/certs/cacert.pem
/usr/lib/python3/dist-packages/pytest_httpbin/certs/cert.pem
/usr/lib/python3/dist-packages/pytest_httpbin/certs/key.pem
/usr/lib/python3/dist-packages/pytest_httpbin/certs.py
/usr/lib/python3/dist-packages/pytest_httpbin/plugin.py
/usr/lib/python3/dist-packages/pytest_httpbin/serve.py
/usr/lib/python3/dist-packages/pytest_httpbin/version.py
/usr/lib/python3/dist-packages/pytest_httpbin-0.2.3.egg-info
/usr/lib/python3/dist-packages/pytest_httpbin-0.2.3.egg-info/PKG-INFO
/usr/lib/python3/dist-packages/pytest_httpbin-0.2.3.egg-info/dependency_links.txt
/usr/lib/python3/dist-packages/pytest_httpbin-0.2.3.egg-info/entry_points.txt
/usr/lib/python3/dist-packages/pytest_httpbin-0.2.3.egg-info/requires.txt
/usr/lib/python3/dist-packages/pytest_httpbin-0.2.3.egg-info/top_level.txt
/usr/share
/usr/share/doc
/usr/share/doc/python3-pytest-httpbin
/usr/share/doc/python3-pytest-httpbin/README.gz
/usr/share/doc/python3-pytest-httpbin/changelog.Debian.gz
/usr/share/doc/python3-pytest-httpbin/changelog.gz
/usr/share/doc/python3-pytest-httpbin/copyright


DS

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)



Bug#848764: theano: FTBFS: Test failures

2016-12-27 Thread Daniel Stender
Thanks for reporting this.

There are 3 errors and 2 failures in the tests in that build, the TypeError: 
"'numpy.float64' object cannot be interpreted
as an index" (3) points to being another problem with numpy 1.12.0.

1)

ERROR: test_infer_shape (theano.sparse.tests.test_sp2.BinomialTester)
--
Traceback (most recent call last):
  File "/<>/theano/sparse/tests/test_sp2.py", line 100, in 
test_infer_shape
self.op_class)
  File "/<>/theano/tests/unittest_tools.py", line 251, in 
_compile_and_check
numeric_outputs = outputs_function(*numeric_inputs)
  File "/<>/theano/compile/function_module.py", line 871, in 
__call__
storage_map=getattr(self.fn, 'storage_map', None))
  File "/<>/theano/gof/link.py", line 314, in raise_with_op
reraise(exc_type, exc_value, exc_trace)
  File "/<>/theano/compile/function_module.py", line 859, in 
__call__
outputs = self.fn()
  File "/<>/theano/gof/op.py", line 912, in rval
r = p(n, [x[0] for x in i], o)
  File "/<>/theano/sparse/sandbox/sp2.py", line 125, in perform
binomial = numpy.random.binomial(n, p, size=shape)
  File "mtrand.pyx", line 3764, in mtrand.RandomState.binomial 
(numpy/random/mtrand/mtrand.c:31661)
TypeError: Cannot cast array data from dtype('float64') to dtype('int64') 
according to the rule 'safe'
Apply node that caused the error: Binomial{format='csc', 
dtype='float64'}(, , 
)
Toposort index: 0
Inputs types: [TensorType(float64, scalar), TensorType(float64, scalar), 
TensorType(int64, vector)]
Inputs shapes: [(), (), (2,)]
Inputs strides: [(), (), (8,)]
Inputs values: [array(5.0), array(0.25), array([3, 5])]
Outputs clients: [['output']]

Backtrace when the node is created(use Theano flag traceback.limit=N to make it 
longer):
  File "/usr/lib/python2.7/dist-packages/nose/suite.py", line 177, in __call__
return self.run(*arg, **kw)
  File "/usr/lib/python2.7/dist-packages/nose/suite.py", line 224, in run
test(orig)
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 45, in __call__
return self.run(*arg, **kwarg)
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 133, in run
self.runTest(result)
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 151, in runTest
test(result)
  File "/usr/lib/python2.7/unittest/case.py", line 393, in __call__
return self.run(*args, **kwds)
  File "/usr/lib/python2.7/unittest/case.py", line 329, in run
testMethod()
  File "/<>/theano/sparse/tests/test_sp2.py", line 98, in 
test_infer_shape
[Binomial(sp_format, o_type)(*self.inputs)],

HINT: Use the Theano flag 'exception_verbosity=high' for a debugprint and 
storage map footprint of this apply node.


2)

RROR: test_op (theano.sparse.tests.test_sp2.BinomialTester)
--
Traceback (most recent call last):
  File "/<>/theano/sparse/tests/test_sp2.py", line 85, in test_op
tested = f(*self._inputs)
  File "/<>/theano/compile/function_module.py", line 871, in 
__call__
storage_map=getattr(self.fn, 'storage_map', None))
  File "/<>/theano/gof/link.py", line 314, in raise_with_op
reraise(exc_type, exc_value, exc_trace)
  File "/<>/theano/compile/function_module.py", line 859, in 
__call__
outputs = self.fn()
  File "/<>/theano/gof/op.py", line 912, in rval
r = p(n, [x[0] for x in i], o)
  File "/<>/theano/sparse/sandbox/sp2.py", line 125, in perform
binomial = numpy.random.binomial(n, p, size=shape)
  File "mtrand.pyx", line 3764, in mtrand.RandomState.binomial 
(numpy/random/mtrand/mtrand.c:31661)
TypeError: Cannot cast array data from dtype('float64') to dtype('int64') 
according to the rule 'safe'
Apply node that caused the error: Binomial{format='csc', 
dtype='float64'}(, , 
)
Toposort index: 0
Inputs types: [TensorType(float64, scalar), TensorType(float64, scalar), 
TensorType(int64, vector)]
Inputs shapes: [(), (), (2,)]
Inputs strides: [(), (), (8,)]
Inputs values: [array(5.0), array(0.25), array([3, 5])]
Outputs clients: [['output']]

Backtrace when the node is created(use Theano flag traceback.limit=N to make it 
longer):
  File "/usr/lib/python2.7/dist-packages/nose/suite.py", line 177, in __call__
return self.run(*arg, **kw)
  File "/usr/lib/python2.7/dist-packages/nose/suite.py", line 224, in run
test(orig)
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 45, in __call__
return self.run(*arg, **kwarg)
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 133, in run
self.runTest(result)
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 151, in runTest
test(result)
  File "/usr/lib/python2.7/unittest/case.py", line 393, in __call__
return self.run(*args, **kwds)
  File "/usr/lib/python2.7/unittest/case.py", 

Bug#849499: llvmlite: ERROR: test_get_host_cpu_features (llvmlite.tests.test_binding.TestMisc)

2016-12-27 Thread Daniel Stender
Source: llvmlite
Version: 0.14.0-2
Severity: serious
File: llvmlite
Justification: fails to build from source

llvmlite [1] (currently in experimental) has a test failure on some archs 
(mips, ppc64el, s390x etc.) [2]:


==
ERROR: test_get_host_cpu_features (llvmlite.tests.test_binding.TestMisc)
--
Traceback (most recent call last):
  File "/«PKGBUILDDIR»/llvmlite/tests/test_binding.py", line 237, in 
test_get_host_cpu_features
features = llvm.get_host_cpu_features()
  File "/«PKGBUILDDIR»/llvmlite/binding/targets.py", line 61, in 
get_host_cpu_features
outdict[feat[1:]] = flag_map[feat[0]]
IndexError: string index out of range


get_host_cpu_features() is defined in llvmlite/binding/targets.py:


def get_host_cpu_features():
"""
Returns a dictionary-like object indicating the CPU features for current
architecture and whether they are enabled for this CPU.  The key-value pairs
are the feature name as string and a boolean indicating whether the feature
is available.  The returned value is an instance of ``FeatureMap`` class,
which adds a new method ``.flatten()`` for returning a string suitable for
use as the "features" argument to ``Target.create_target_machine()``.
"""
with ffi.OutputString() as out:
ffi.lib.LLVMPY_GetHostCPUFeatures(out)
outdict = FeatureMap()
flag_map = {'+': True, '-': False}
for feat in str(out).split(','):
outdict[feat[1:]] = flag_map[feat[0]]
return outdict


It appears ffi.lib.LLVMPY_GetHostCPUFeatures() doesn't return anything (e.g. on 
s390x):


Python 2.7.13 (default, Dec 18 2016, 20:19:42) 
[GCC 6.2.1 20161215] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from llvmlite.binding import ffi
>>> with ffi.OutputString() as out:
... ffi.lib.LLVMPY_GetHostCPUFeatures(out)
... print(out)
... 
0


Could this be a regression from LLVM?

DS

[1] https://packages.qa.debian.org/l/llvmlite.html

[2] https://buildd.debian.org/status/package.php?p=llvmlite=experimental

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages python-llvmlite depends on:
ii  libc6  2.24-8
ii  libgcc11:6.2.1-5
ii  libtinfo5  6.0+20161126-1
ii  llvm-3.8   1:3.8.1-16
ii  python 2.7.11-2
ii  python-enum34  1.1.6-1
ii  python-six 1.10.0-3
pn  python:any 
ii  zlib1g 1:1.2.8.dfsg-4

Versions of packages python-llvmlite recommends:
ii  llvmlite-doc  0.14.0-2

python-llvmlite suggests no packages.

-- no debconf information



Bug#848234: txwinrm,winrm: error when trying to install together

2016-12-22 Thread Daniel Stender
Hi Christopher,

we have a binaries-have-conflict between our packages and we have to negotiate 
how to handle
this.

I standpoint is, masterzen-winrm was in first (2016-04-14), so I would like to 
ask if
you could change your package to solve this. I would change mine if this would 
be the
other way around. Is that alright with you?

Dan

-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
LPIC-1 (LPI000329859 64mz6f7kt4)
http://www.danielstender.com/



Bug#835531: theano: FTBFS on amd64 (fail of test_csr_correct_output_faster_than_scipy)

2016-12-17 Thread Daniel Stender
Control: severity -1 normal

Reopened because this appeared again in reproducible builds CI. However, this 
failure is only
hardly reproducible. Currently it builds fine throughout. Therefore, I'm 
lowering the severity
of this bug report.

DS

-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
LPIC-1 (LPI000329859 64mz6f7kt4)
http://www.danielstender.com/



signature.asc
Description: OpenPGP digital signature


Bug#844358: pytest-httpbin: FTBFS (test_chunked_encoding[https] FAILED)

2016-12-09 Thread Daniel Stender
Control: severity -1 normal

I've filed this about a FTBFS in reproducible builds CI on i386 in unstable. 
But this
couldn't hardly be reproduced. The new package (0.2.3) doesn't contain a 
particular
fix for this, but appears to build fine throughout. DEP-8 test doesn't brought 
up
something, whatsoever.

For that, I'm now lowering the severity of this bug but leave it open for now, 
seeking
out of this appears again anywhere.

Thanks,
DS

-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
LPIC-1 (LPI000329859 64mz6f7kt4)
http://www.danielstender.com/



Bug#844515: packer: FTBFS on s390x (go install -v -p 1 died with signal 4)

2016-12-04 Thread Daniel Stender
Control: severity -1 important

This is a toolchain problem. s390x support is currently removed for golang-go 
[1].
And rdependend packages are going to be removed [2].

I'll leave this bug open until this happened.

DS

[1] https://bugs.debian.org/844258 (golang-go: go SIGILL on s390x)

[2] https://bugs.debian.org/845003

-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
LPIC-1 (LPI000329859 64mz6f7kt4)
http://www.danielstender.com/



signature.asc
Description: OpenPGP digital signature


Bug#844343: golang-github-pierrec-lz4: FTBFS on armhf (TestCopy crashes)

2016-12-04 Thread Daniel Stender
Control: forwarded -1 https://github.com/pierrec/lz4/issues/9

This is reproducible on harris (Linux harris 3.16.0-4-armmp #1 SMP Debian 
3.16.36-1+deb8u2
(2016-10-19) armv7l GNU/Linux).

DS

-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
LPIC-1 (LPI000329859 64mz6f7kt4)
http://www.danielstender.com/



Bug#846952: execnet: testing/test_channel.py::TestStringCoerce::test_2to3 FAILED

2016-12-04 Thread Daniel Stender
Source: execnet
Version: 1.4.1-2
Severity: serious
Justification: fails to build from source

Execnet currently fails in DEP-8 tests [1]:


testing/test_channel.py::TestStringCoerce::test_2to3 FAILED
{...}
=== FAILURES ===
__ TestStringCoerce.test_2to3 __

self = 
makegateway = >

@pytest.mark.skipif('sys.version>="3.0"')
def test_2to3(self, makegateway):
python = _find_version('3')
gw = makegateway('popen//python=%s' % python)
ch = gw.remote_exec('channel.send(channel.receive());'*2)
ch.send('a')
>   res = ch.receive()

testing/test_channel.py:351: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = , timeout = None

def receive(self, timeout=None):
"""receive a data item that was sent from the other side.
timeout: None [default] blocked waiting.  A positive number
indicates the number of seconds after which a channel.TimeoutError
exception will be raised if no item was received.
Note that exceptions from the remotely executing code will be
reraised as channel.RemoteError exceptions containing
a textual representation of the remote traceback.
"""
itemqueue = self._items
if itemqueue is None:
raise IOError("cannot receive(), channel has receiver callback")
try:
x = itemqueue.get(timeout=timeout)
except self.gateway.execmodel.queue.Empty:
raise self.TimeoutError("no item after %r seconds" % (timeout))
if x is ENDMARKER:
itemqueue.put(x)  # for other receivers
>   raise self._getremoteerror() or EOFError()
E   EOFError: couldnt load message header, expected 9 bytes, got 0

execnet/gateway_base.py:737: EOFError
- Captured stderr call -
Exception ignored in: 
Traceback (most recent call last):
  File "", line 602, in __del__
AttributeError: 'Channel' object has no attribute '_closed'


By the way, the package is RFA [2].

Thanks,
DS

[1] 
https://ci.debian.net/data/packages/unstable/amd64/e/execnet/20161203_200139.autopkgtest.log.gz

[2] https://bugs.debian.org/840032

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)



Bug#846951: execnet: testing/test_gateway.py::TestTracing::test_popen_stderr_tracing FAILED

2016-12-04 Thread Daniel Stender
Source: execnet
Version: 1.4.1-2
Severity: serious
Justification: fails to build from source

There is a test failure in this package from the reproducible builds CI in the 
2nd build
on amd64 [1]:


testing/test_gateway.py::TestTracing::test_popen_stderr_tracing FAILED
{...}
=== FAILURES ===
 TestTracing.test_popen_stderr_tracing _

self = 
capfd = <_pytest.capture.CaptureFixture instance at 0x7f439eae9710>
monkeypatch = <_pytest.monkeypatch.MonkeyPatch instance at 0x7f439eae97e8>
makegateway = >

def test_popen_stderr_tracing(self, capfd, monkeypatch, makegateway):
monkeypatch.setenv('EXECNET_DEBUG', "2")
gw = makegateway("popen")
pid = gw.remote_exec("import os ; channel.send(os.getpid())").receive()
out, err = capfd.readouterr()
slave_line = "[%s] creating slavegateway" % pid
>   assert slave_line in err
E   assert '[13247] creating slavegateway' in '8>\n[13247] gw0-slave 
[serve] spawning receiver thread\n[13247] gw0-slave [serve] integrating as 
primary thread\n[13247]...hed\n[13247] gw0-slave sent \n[13247] gw0-slave 1 sent channel close message\n'

testing/test_gateway.py:391: AssertionError
 pytest-warning summary 
WI1 /build/execnet-1.4.1/testing/conftest.py:21 'pytest_runtest_setup' hook 
uses deprecated __multicall__ argument
WC1 None pytest_funcarg__specsocket: declaring fixtures using 
"pytest_funcarg__" prefix is deprecated and scheduled to be removed in pytest 
4.0.  Please remove the prefix and use the @pytest.fixture decorator instead.
WC1 None pytest_funcarg__specssh: declaring fixtures using "pytest_funcarg__" 
prefix is deprecated and scheduled to be removed in pytest 4.0.  Please remove 
the prefix and use the @pytest.fixture decorator instead.
 Interrupted: stopping after 1 failures 
 1 failed, 229 passed, 607 skipped, 5 xfailed, 3 pytest-warnings in 15.21 
seconds
 

By the way, the package is RFA [2].

DS

[1] 
https://tests.reproducible-builds.org/debian/rb-pkg/testing/amd64/execnet.html

[2] https://bugs.debian.org/840032

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)



Bug#840823: execnet: FTBFS (failing tests)

2016-12-04 Thread Daniel Stender
Control: retitle -1 execnet: 
testing/test_gateway.py::TestBasicGateway::test_gateway_status_busy[thread-popen]
 FAILED

There are two more RC test failures recorded, one from reproducible builds CI, 
the other from DEP-8
tests. I'll file more bugs on these, now.

I can't reproduce this right now and not yet firm into this package. I'll get 
into it but if somebody could
come up with some hints on that (maybe the new maintainer [1]), this would be 
great.

DS

[1] https://bugs.debian.org/840032 (RFA)

-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
LPIC-1 (LPI000329859 64mz6f7kt4)
http://www.danielstender.com/



Bug#841474: marked as pending

2016-11-19 Thread Daniel Stender
tag 841474 pending
thanks

Hello,

Bug #841474 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:

http://git.debian.org/?p=collab-maint/afl.git;a=commitdiff;h=f99f42a

---
commit f99f42ab9ebb10c8f813ac9e5efe1fe79d295225
Author: Daniel Stender <sten...@debian.org>
Date:   Sat Nov 19 22:43:47 2016 +0100

pass custom mfpu also to $CXXFLAGS

diff --git a/debian/changelog b/debian/changelog
index 8e6b0cf..d941e25 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+afl (2.34b-5) experimental; urgency=medium
+
+  * deb/rules:
++ pass custom mfpu also to $CXXFLAGS (Closes: #841474) [thanks to Michal
+  Zaleswki].
++ corrected an error in the info text.
+
+ -- Daniel Stender <sten...@debian.org>  Sat, 19 Nov 2016 22:39:34 +0100
+
 afl (2.34b-4) experimental; urgency=medium
 
   * use "vfpv3" to set mfpu.



Bug#841474: afl: FTBFS on armhf (illegal instruction in afl-clang-fast)

2016-11-19 Thread Daniel Stender
Control: found -1 afl/2.34b-4

I've tried to build while passing "-mfpu=vfpv3" to $CFLAGS for llvm_mode/, but 
although
it appears NEON has been disabled by that ("-target-feature -neon"), it doesn't 
work out
like that (test build on abel which is non-NEON):


[*] Testing the CC wrapper and instrumentation output...
unset AFL_USE_ASAN AFL_USE_MSAN AFL_INST_RATIO; AFL_QUIET=1 AFL_PATH=. 
AFL_CC=clang-3.9 ../afl-clang-fast -g -O2 -fdebug-prefix-
map=/home/stender/sandbox/afl-2.34b=. -fstack-protector-strong -Wformat 
-Werror=format-security -mfpu=vfpv3 -Wall -D_FORTIFY_SOURCE=2 
-g -Wno-pointer-sign -DAFL_PATH=\"/usr/lib/afl\" -DBIN_PATH=\"/usr/bin\" 
-DVERSION=\"2.34b\"  ../test-instr.c -o test-instr 
-Wl,-z,relro -Wl,-z,now
Stack dump:
0.  Program arguments: /usr/lib/llvm-3.9/bin/clang -cc1 -triple 
armv7-unknown-linux-gnueabihf -emit-obj -disable-free -disable-
llvm-verifier -discard-value-names -main-file-name test-instr.c 
-mrelocation-model static -mthread-model posix -mdisable-fp-elim 
-fmath-errno -masm-verbose -mconstructor-aliases -fuse-init-array -target-cpu 
cortex-a8 -target-feature -fp-only-sp -target-feature 
-d16 -target-feature +vfp3 -target-feature -fp16 -target-feature -vfp4 
-target-feature -fp-armv8 -target-feature -neon -target-
feature -crypto -target-abi aapcs-linux -mfloat-abi hard -dwarf-column-info 
-debug-info-kind=limited -dwarf-version=4 -debugger-
tuning=gdb -resource-dir /usr/lib/llvm-3.9/bin/../lib/clang/3.9.0 -D 
_FORTIFY_SOURCE=2 -D AFL_PATH="/usr/lib/afl" -D 
BIN_PATH="/usr/bin" -D VERSION="2.34b" -D __AFL_HAVE_MANUAL_CONTROL=1 -D 
__AFL_COMPILER=1 -D 
FUZZING_BUILD_MODE_UNSAFE_FOR_PRODUCTION=1 -D __AFL_LOOP(_A)=({ static volatile 
char *_B __attribute__((used));  _B = 
(char*)"##SIG_AFL_PERSISTENT##"; __attribute__((visibility("default"))) int 
_L(unsigned int) __asm__("__afl_persistent_loop"); 
_L(_A); }) -D __AFL_INIT()=do { static volatile char *_A __attribute__((used)); 
 _A = (char*)"##SIG_AFL_DEFER_FORKSRV##"; 
__attribute__((visibility("default"))) void _I(void) 
__asm__("__afl_manual_init"); _I(); } while (0) -internal-isystem /usr/local
/include -internal-isystem /usr/lib/llvm-3.9/bin/../lib/clang/3.9.0/include 
-internal-externc-isystem /usr/include/arm-linux-
gnueabihf -internal-externc-isystem /include -internal-externc-isystem 
/usr/include -O3 -Wformat -Werror=format-security -Wall 
-Wno-pointer-sign -fdebug-compilation-dir 
/home/stender/sandbox/afl-2.34b/llvm_mode 
-fdebug-prefix-map=/home/stender/sandbox
/afl-2.34b=. -ferror-limit 19 -fmessage-length 105 -funroll-loops 
-stack-protector 2 -fallow-half-arguments-and-returns 
-fno-signed-char -fobjc-runtime=gcc -fdiagnostics-show-option 
-fcolor-diagnostics -vectorize-loops -vectorize-slp -load ../afl-
llvm-pass.so -o /tmp/test-instr-64d4c5.o -x c ../test-instr.c 
1.   parser at end of file
2.  Per-module optimization passes
3.  Running pass 'American Fuzzy Lop Instrumentation' on module 
'../test-instr.c'.
clang: error: unable to execute command: Illegal instruction


If somebody finds time and interest, hints are welcome (the latest package is 
in experimental).

DS

-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
LPIC-1 (LPI000329859 64mz6f7kt4)
http://www.danielstender.com/



Bug#844515: [pkg-go] Bug#844515: packer: FTBFS on s390x (go install -v -p 1 died with signal 4)

2016-11-16 Thread Daniel Stender
... found it, #844258 (golang-go: go SIGILL on s390x)

True, zemlinsky (builder) is z10, zelenka (porterbox) z13.

Thanks for the hint,
DS

On 16.11.2016 20:05, Michael Hudson-Doyle wrote:
> This is the "golang for s390x only works on z196+, not z10" thing. The
> right fix is probably to not build golang on Debian, sadly.
> 
> On 17 November 2016 at 01:40, Daniel Stender <deb...@danielstender.com>
> wrote:
> 
>> Package: packer
>> Version: 0.10.1+dfsg-1
>> Severity: serious
>> Justification: fails to build from source (but built successfully in the
>> past)
>>
>> Packer currently (recently 0.10.2+dfsg-1) fails to build on s390x:
>>
>> 
>>dh_auto_build -O--buildsystem=golang
>> cd obj-s390x-linux-gnu
>> go install -v -p 1
>> dh_auto_build: go install -v -p 1 died with signal 4
>> cd /<>/packer-0.10.2+dfsg
>> debian/rules:6: recipe for target 'build' failed
>> make: *** [build] Error 255
>> dpkg-buildpackage: error: debian/rules build gave error exit status 2
>> 
>>
>> This is a regression from 0.10.1+dfsg-1 [1] (the build on 2016-10-16 [2]
>> failed
>> for a dependency reason which is solved in the meanwhile, see #841605 [3]).
>>
>> [1] https://buildd.debian.org/status/logs.php?pkg=packer=s390x
>>
>> [2] https://buildd.debian.org/status/fetch.php?pkg=packer;
>> arch=s390x=0.10.1%2Bdfsg-1=1476596269
>>
>> [3] https://bugs.debian.org/841605 (packer: FTBFS: src/
>> github.com/Azure/go-autorest/autorest/azure/token.go:140: undefined:
>> jwt.MapClaims)
>>
>> I can reproduce this locally in a qemu-chroot for Sbuild, however a test
>> build on
>> the zelenka porterbox succeeded:
>>
>> 
>> {...}
>> dpkg-deb: building package 'golang-github-mitchellh-packer-dev' in
>> '../golang-github-mitchellh-packer-dev_0.10.2+dfsg-1_all.deb'.
>> dpkg-deb: building package 'packer' in '../packer_0.10.2+dfsg-1_
>> s390x.deb'.
>>  dpkg-genbuildinfo
>> dpkg-genbuildinfo: warning: File::FcntlLock not available; using flock
>> which is not NFS-safe
>>  dpkg-genchanges  >../packer_0.10.2+dfsg-1_s390x.changes
>> dpkg-genchanges: info: including full source code in upload
>>  dpkg-source --after-build packer-0.10.2+dfsg
>> dpkg-buildpackage: info: full upload (original source is included)
>> (sid_s390x-dchroot)stender@zelenka:~/sandbox/packer-0.10.2+dfsg$
>> 
>>
>> Thanks for hints,
>> DS
>>
>> -- System Information:
>> Debian Release: stretch/sid
>>   APT prefers testing
>>   APT policy: (500, 'testing'), (1, 'experimental')
>> Architecture: amd64 (x86_64)
>>
>> Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
>> Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
>> Shell: /bin/sh linked to /bin/dash
>> Init: systemd (via /run/systemd/system)
>>
>> Versions of packages packer depends on:
>> ii  libc6  2.24-5
>>
>> Versions of packages packer recommends:
>> pn  docker.io  
>> ii  qemu   1:2.7+dfsg-3+b1
>>
>> Versions of packages packer suggests:
>> ii  ansible  2.1.1.0-1
>> pn  chef 
>>
>> -- no debconf information
>>
>> ___
>> Pkg-go-maintainers mailing list
>> pkg-go-maintain...@lists.alioth.debian.org
>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
>>
> 


-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
LPIC-1 (LPI000329859 64mz6f7kt4)
http://www.danielstender.com/



Bug#844515: packer: FTBFS on s390x (go install -v -p 1 died with signal 4)

2016-11-16 Thread Daniel Stender
Package: packer
Version: 0.10.1+dfsg-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Packer currently (recently 0.10.2+dfsg-1) fails to build on s390x:


   dh_auto_build -O--buildsystem=golang
cd obj-s390x-linux-gnu
go install -v -p 1
dh_auto_build: go install -v -p 1 died with signal 4
cd /<>/packer-0.10.2+dfsg
debian/rules:6: recipe for target 'build' failed
make: *** [build] Error 255
dpkg-buildpackage: error: debian/rules build gave error exit status 2


This is a regression from 0.10.1+dfsg-1 [1] (the build on 2016-10-16 [2] failed
for a dependency reason which is solved in the meanwhile, see #841605 [3]).

[1] https://buildd.debian.org/status/logs.php?pkg=packer=s390x

[2] 
https://buildd.debian.org/status/fetch.php?pkg=packer=s390x=0.10.1%2Bdfsg-1=1476596269

[3] https://bugs.debian.org/841605 (packer: FTBFS: 
src/github.com/Azure/go-autorest/autorest/azure/token.go:140: undefined: 
jwt.MapClaims)

I can reproduce this locally in a qemu-chroot for Sbuild, however a test build 
on
the zelenka porterbox succeeded:


{...}
dpkg-deb: building package 'golang-github-mitchellh-packer-dev' in 
'../golang-github-mitchellh-packer-dev_0.10.2+dfsg-1_all.deb'.
dpkg-deb: building package 'packer' in '../packer_0.10.2+dfsg-1_s390x.deb'.
 dpkg-genbuildinfo
dpkg-genbuildinfo: warning: File::FcntlLock not available; using flock which is 
not NFS-safe
 dpkg-genchanges  >../packer_0.10.2+dfsg-1_s390x.changes
dpkg-genchanges: info: including full source code in upload
 dpkg-source --after-build packer-0.10.2+dfsg
dpkg-buildpackage: info: full upload (original source is included)
(sid_s390x-dchroot)stender@zelenka:~/sandbox/packer-0.10.2+dfsg$


Thanks for hints,
DS

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages packer depends on:
ii  libc6  2.24-5

Versions of packages packer recommends:
pn  docker.io  
ii  qemu   1:2.7+dfsg-3+b1

Versions of packages packer suggests:
ii  ansible  2.1.1.0-1
pn  chef 

-- no debconf information



Bug#844435: [pkg-go] Bug#844435: Bug#844435: golang-golang-x-oauth2: splitted package misses Breaks

2016-11-15 Thread Daniel Stender
On 15.11.2016 19:11, Martín Ferrari wrote:
> Daniel,
> 
> 
> On 15/11/16 18:46, Daniel Stender wrote:
> 
>> the new package golang-golang-x-oauth2-google-dev missed Breaks against the 
>> previous
>> package revision:
> 
> Oh, I completely forgot that, thanks for spotting! Will fix asap.

... all right. I have an eye for that since it happened to me a couple of times.

Cheers,
Dan

-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
LPIC-1 (LPI000329859 64mz6f7kt4)
http://www.danielstender.com/



Bug#844435: golang-golang-x-oauth2: splitted package misses Breaks

2016-11-15 Thread Daniel Stender
Source: golang-golang-x-oauth2
Version: 0.0~git20161103.0.36bc617-2
Severity: serious
Justification: Policy 7.6

Hi,

the new package golang-golang-x-oauth2-google-dev missed Breaks against the 
previous
package revision:


$ sudo dpkg -i 
golang-golang-x-oauth2-google-dev_0.0~git20161103.0.36bc617-3_all.deb 
Selecting previously unselected package golang-golang-x-oauth2-google-dev.
(Reading database ... 673099 files and directories currently installed.)
Preparing to unpack 
golang-golang-x-oauth2-google-dev_0.0~git20161103.0.36bc617-3_all.deb ...
Unpacking golang-golang-x-oauth2-google-dev (0.0~git20161103.0.36bc617-3) ...
dpkg: error processing archive 
golang-golang-x-oauth2-google-dev_0.0~git20161103.0.36bc617-3_all.deb 
(--install):
 trying to overwrite 
'/usr/share/gocode/src/golang.org/x/oauth2/google/appengine.go', which is also 
in package golang-golang-x-oauth2-dev 0.0~git20161103.0.36bc617-1
Errors were encountered while processing:
 golang-golang-x-oauth2-google-dev_0.0~git20161103.0.36bc617-3_all.deb


Best,
DS
 
-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)



Bug#827068: m2crypto: doesn't work together with OpenSSL 1.1 (API changes)

2016-11-15 Thread Daniel Stender
On Mon, 14 Nov 2016 19:52:31 +0100 Daniel Stender <deb...@danielstender.com> 
wrote:
> The diff doesn't work like that on the upstream code in the archive

... the same is true for 0.25.1.

I'm on it.

DS

-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
LPIC-1 (LPI000329859 64mz6f7kt4)
http://www.danielstender.com/



Bug#844358: pytest-httpbin: FTBFS (test_chunked_encoding[https] FAILED)

2016-11-14 Thread Daniel Stender
Source: pytest-httpbin
Version: 0.2.0-1
Severity: serious
Justification: fails to build from source

The package currently doesn't build:


tests/test_httpbin.py::test_chunked_encoding[https] FAILED

=== FAILURES ===
_ test_chunked_encoding[https] _

httpbin_both = 

def test_chunked_encoding(httpbin_both):
>   assert requests.get(httpbin_both.url + '/stream/20').status_code == 200

tests/test_httpbin.py:44: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib/python2.7/dist-packages/requests/api.py:70: in get
return request('get', url, params=params, **kwargs)
/usr/lib/python2.7/dist-packages/requests/api.py:56: in request
return session.request(method=method, url=url, **kwargs)
/usr/lib/python2.7/dist-packages/requests/sessions.py:475: in request
resp = self.send(prep, **send_kwargs)
/usr/lib/python2.7/dist-packages/requests/sessions.py:628: in send
r.content
/usr/lib/python2.7/dist-packages/requests/models.py:755: in content
self._content = bytes().join(self.iter_content(CONTENT_CHUNK_SIZE)) or 
bytes()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

def generate():
# Special case for urllib3.
if hasattr(self.raw, 'stream'):
try:
for chunk in self.raw.stream(chunk_size, decode_content=True):
yield chunk
except ProtocolError as e:
>   raise ChunkedEncodingError(e)
E   ChunkedEncodingError: ("Connection broken: error(0, 'Error')", 
error(0, 'Error'))

/usr/lib/python2.7/dist-packages/requests/models.py:679: ChunkedEncodingError
- Captured stderr call -
127.0.0.1 - - [14/Nov/2016 19:54:16] "GET /stream/20 HTTP/1.1" 200 5430
 Interrupted: stopping after 1 failures 
== 1 failed, 8 passed in 1.36 seconds ==


I'll get into that, soon.

DS

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)



Bug#827068: m2crypto: doesn't work together with OpenSSL 1.1 (API changes)

2016-11-14 Thread Daniel Stender
On Sun, 16 Oct 2016 14:05:28 +0200 Kurt Roeckx  wrote:
> tags 827068 + patch
> thanks
> 
> Hi,
> 
> A patch is available at:
> https://gitlab.com/m2crypto/m2crypto/merge_requests/98
> 
> Kurt

The diff doesn't work like that on the upstream code in the archive, I'll 
package
a repo snapshot as soon as that merge has completed.

DS

-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
LPIC-1 (LPI000329859 64mz6f7kt4)
http://www.danielstender.com/



Bug#844343: golang-github-pierrec-lz4: FTBFS on armhf (TestCopy crashes)

2016-11-14 Thread Daniel Stender
Source: golang-github-pierrec-lz4
Version: 0.0~git20151216.222ab1f-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

The build of this package break in the reproducible build environment during the
2nd build on armhf [1]:


=== RUN   TestCopy
SIGQUIT: quit
PC=0x709f8 m=0

goroutine 0 [idle]:
runtime.futex(0x1c48fc, 0x0, 0x0, 0x0, 0x0, 0x0, 0x1dba0, 0x0, 0x0, 0x0, ...)
/usr/lib/go-1.7/src/runtime/sys_linux_arm.s:247 +0x20
runtime.futexsleep(0x1c48fc, 0x0, 0x, 0x)
/usr/lib/go-1.7/src/runtime/os_linux.go:45 +0x68
runtime.notesleep(0x1c48fc)
/usr/lib/go-1.7/src/runtime/lock_futex.go:145 +0xa4
runtime.stopm()
/usr/lib/go-1.7/src/runtime/proc.go:1594 +0x100
runtime.findrunnable(0x1051f400, 0x0)
/usr/lib/go-1.7/src/runtime/proc.go:2021 +0x758
runtime.schedule()
/usr/lib/go-1.7/src/runtime/proc.go:2120 +0x26c
runtime.goexit0(0x117eb770)
/usr/lib/go-1.7/src/runtime/proc.go:2257 +0x1d0
runtime.mcall(0x1c4600)
/usr/lib/go-1.7/src/runtime/asm_arm.s:183 +0x5c

goroutine 1 [chan receive, 3 minutes]:
testing.(*T).Run(0x10588000, 0x14906a, 0x8, 0x15c6f4, 0xa1901)
/usr/lib/go-1.7/src/testing/testing.go:647 +0x324
testing.RunTests.func1(0x10590100)
/usr/lib/go-1.7/src/testing/testing.go:793 +0xb8
testing.tRunner(0x10590100, 0x1053ced4)
/usr/lib/go-1.7/src/testing/testing.go:610 +0xa4
testing.RunTests(0x15c714, 0x1c3120, 0x8, 0x8, 0xa1)
/usr/lib/go-1.7/src/testing/testing.go:799 +0x388
testing.(*M).Run(0x1053cf7c, 0x40)
/usr/lib/go-1.7/src/testing/testing.go:743 +0x8c
main.main()
github.com/pierrec/lz4/_test/_testmain.go:76 +0x118

goroutine 17422 [semacquire]:
sync.runtime_Semacquire(0x10516080)
/usr/lib/go-1.7/src/runtime/sema.go:47 +0x24
sync.(*WaitGroup).Wait(0x10516074)
/usr/lib/go-1.7/src/sync/waitgroup.go:131 +0xc0
github.com/pierrec/lz4.(*Writer).Write(0x10516050, 0x128c, 0x10, 
0x10, 0x0, 0x0, 0x0)

/build/golang-github-pierrec-lz4-0.0~git20151216.222ab1f/obj-arm-linux-gnueabihf/src/github.com/pierrec/lz4/writer.go:183
 +0x9b0
github.com/pierrec/lz4.(*Writer).ReadFrom(0x10516050, 0x1b2770, 0x10570128, 
0x20, 0x0, 0x0, 0x0)

/build/golang-github-pierrec-lz4-0.0~git20151216.222ab1f/obj-arm-linux-gnueabihf/src/github.com/pierrec/lz4/writer.go:357
 +0x1a0
io.copyBuffer(0x1b2758, 0x10516050, 0x1b2770, 0x10570128, 0x0, 0x0, 0x0, 0x0, 
0x0, 0x0, ...)
/usr/lib/go-1.7/src/io/io.go:384 +0x124
io.Copy(0x1b2758, 0x10516050, 0x1b2770, 0x10570128, 0x10, 0x148670, 0x0, 0x0)
/usr/lib/go-1.7/src/io/io.go:360 +0x64
github.com/pierrec/lz4_test.TestCopy(0x10588000)

/build/golang-github-pierrec-lz4-0.0~git20151216.222ab1f/obj-arm-linux-gnueabihf/src/github.com/pierrec/lz4/lz4_test.go:493
 +0x370
testing.tRunner(0x10588000, 0x15c6f4)
/usr/lib/go-1.7/src/testing/testing.go:610 +0xa4
created by testing.(*T).Run
/usr/lib/go-1.7/src/testing/testing.go:646 +0x304

goroutine 25094 [runnable]:
github.com/pierrec/lz4.(*Writer).Write.func1(0x10516050, 0x128c, 0x10, 
0x10)

/build/golang-github-pierrec-lz4-0.0~git20151216.222ab1f/obj-arm-linux-gnueabihf/src/github.com/pierrec/lz4/writer.go:120
created by github.com/pierrec/lz4.(*Writer).Write

/build/golang-github-pierrec-lz4-0.0~git20151216.222ab1f/obj-arm-linux-gnueabihf/src/github.com/pierrec/lz4/writer.go:123
 +0xf8

goroutine 25098 [runnable]:
github.com/pierrec/lz4.CompressBlock(0x1298, 0x4, 0x4, 0x112a8000, 
0x4, 0x4, 0x0, 0x4, 0x6fe08, 0x10516074)

/build/golang-github-pierrec-lz4-0.0~git20151216.222ab1f/obj-arm-linux-gnueabihf/src/github.com/pierrec/lz4/block.go:116
github.com/pierrec/lz4.(*Writer).compressBlock(0x10516050, 0x116ea084)

/build/golang-github-pierrec-lz4-0.0~git20151216.222ab1f/obj-arm-linux-gnueabihf/src/github.com/pierrec/lz4/writer.go:238
 +0x310
created by github.com/pierrec/lz4.(*Writer).Write

/build/golang-github-pierrec-lz4-0.0~git20151216.222ab1f/obj-arm-linux-gnueabihf/src/github.com/pierrec/lz4/writer.go:165
 +0x530

goroutine 25097 [runnable]:
github.com/pierrec/lz4.(*Writer).compressBlock(0x10516050, 0x116ea058)

/build/golang-github-pierrec-lz4-0.0~git20151216.222ab1f/obj-arm-linux-gnueabihf/src/github.com/pierrec/lz4/writer.go:228
created by github.com/pierrec/lz4.(*Writer).Write

/build/golang-github-pierrec-lz4-0.0~git20151216.222ab1f/obj-arm-linux-gnueabihf/src/github.com/pierrec/lz4/writer.go:165
 +0x530

goroutine 25096 [runnable]:
github.com/pierrec/lz4.(*Writer).compressBlock(0x10516050, 0x116ea02c)

/build/golang-github-pierrec-lz4-0.0~git20151216.222ab1f/obj-arm-linux-gnueabihf/src/github.com/pierrec/lz4/writer.go:228
created by github.com/pierrec/lz4.(*Writer).Write


Bug#841474: marked as pending

2016-11-14 Thread Daniel Stender
tag 841474 pending
thanks

Hello,

Bug #841474 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:

http://git.debian.org/?p=collab-maint/afl.git;a=commitdiff;h=a4abda1

---
commit a4abda1a4f8cdff5b4bd59df968e861f9d27bcb5
Author: Daniel Stender <sten...@debian.org>
Date:   Mon Nov 14 13:50:31 2016 +0100

deb/rules: add -mfpu=vfp3 to $CFLAGS on armhf

diff --git a/debian/changelog b/debian/changelog
index 547b2ff..e78f22f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+afl (2.34b-3) UNRELEASED; urgency=medium
+
+  * deb/rules:
++ add -mfpu=vfp3 to $CFLAGS on armhf (Closes: #841474).
++ pass $clang_cflags to make -C llvm_mode.
+
+ -- Daniel Stender <sten...@debian.org>  Mon, 14 Nov 2016 13:50:06 +0100
+
 afl (2.34b-2) unstable; urgency=medium
 
   * Upload to unstable.



Bug#843040: c-blosc: diff for NMU version 1.11.1+ds1-2.1

2016-11-06 Thread Daniel Stender
Hi Gilles,

that's o.k. with me. Thx for taking care of this.

Best,
DS

On 06.11.2016 12:10, Gilles Filippini wrote:
> Control: tags 8430040 + patch
> Control: tags 8430040 + pending
> 
> Dear maintainer,
> 
> I've prepared an NMU for c-blosc (versioned as 1.11.1+ds1-2.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.
> 
> Regards,
> 
> _g.

-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
LPIC-1 (LPI000329859 64mz6f7kt4)
http://www.danielstender.com/



Bug#841474: afl: FTBFS on armhf (illegal instruction on test-instr.c)

2016-10-20 Thread Daniel Stender
Package: afl
Version: 2.34b-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

>From 2.30b-1 onwards (the first package which was tried to build against 
>llvm-toolchain
> 3.7 on this arch), AFL build breaks with "illegal instruction" trying to 
> compile
test-instr.c with afl-clang-fast, now trying to build with clang 3.9 [1]:


[*] Testing the CC wrapper and instrumentation output...
unset AFL_USE_ASAN AFL_USE_MSAN AFL_INST_RATIO; AFL_QUIET=1 AFL_PATH=. 
AFL_CC=clang-3.9
../afl-clang-fast -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. -fPIE 
-fstack-protector-strong
-Wformat -Werror=format-security -Wall -D_FORTIFY_SOURCE=2 -g -Wno-pointer-sign
-DAFL_PATH=\"/usr/lib/afl\" -DBIN_PATH=\"/usr/bin\" -DVERSION=\"2.34b\"  
../test-instr.c -o
test-instr -fPIE -pie -Wl,-z,relro -Wl,-z,now
Illegal instruction


Julien Puydt has reported something similar for the flint package:
https://bugs.debian.org/798111 (Illegal instruction after compiling some code)

Strangely, the package builds fine in the porterbox and with a 
qemu-bootstrapped local
sbuild [2].

Thanks for any input (if this could be worked around in the AFL package),
I'll try to seek what's causing this in the build toolchain.
DS

[1] 
https://buildd.debian.org/status/fetch.php?pkg=afl=armhf=2.34b-2=1474836143

[2] 
http://www.danielstender.com/buildlogs/afl_2.34b-2_armhf-2016-10-20T23:40:16Z.build

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages afl depends on:
ii  build-essential  12.2
ii  libc62.24-3

Versions of packages afl recommends:
pn  afl-clang  
ii  afl-doc2.34b-2

Versions of packages afl suggests:
ii  gnuplot  5.0.4+dfsg1-3

-- no debconf information



  1   2   3   >