[Python-modules-team] Bug#893745: python-cffi: FTBFS on ia64: several test failures
_s baz(int, int);
struct foo_s bok(void); }
""")
lib = verify(ffi, 'test_extern_python_struct',
"struct foo_s { int a, b, c; };")
#
@ffi.def_extern()
def bar(x, s, z):
return x + s.a + s.b + s.c + z
res = lib.bar(1000, [1001, 1002, 1004], 1008)
assert res == 5015
#
@ffi.def_extern()
def baz(x, y):
return [x + y, x - y, x * y]
res = lib.baz(1000, 42)
> assert res.a == 1042
E AssertionError: assert 1109917696 == 1042
E+ where 1109917696 = .a
testing/cffi1/test_recompiler.py:1675: AssertionError
- Captured stdout call -
generating /tmp/ffi-0/_CFFI_test_extern_python_struct.cpp
setting the current directory to '/tmp/ffi-0'
running build_ext
building '_CFFI_test_extern_python_struct' extension
ia64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes
-fno-strict-aliasing -g -O2 -fdebug-prefix-map=/<>=. -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -UNDEBUG
-I/usr/include/python2.7 -c _CFFI_test_extern_python_struct.cpp -o
./_CFFI_test_extern_python_struct.o
ia64-linux-gnu-g++ -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions
-fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes
-Wdate-time -D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-diLoLc/python2.7-2.7.14=. -Wformat
-Werror=format-security -g -O2 -fdebug-prefix-map=/<>=. -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2
./_CFFI_test_extern_python_struct.o -o ./_CFFI_test_extern_python_struct.so
- Captured stderr call -
cc1plus: warning: command line option '-Wstrict-prototypes' is valid for C/ObjC
but not for C++
--
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#893743: python-cffi: FTBFS on hurd-i386: test_thread AssertionError
Source: python-cffi
Version: 1.11.5-1
Severity: important
Tags: upstream
Justification: fails to build from source (but built successfully in the past)
User: debian-h...@lists.debian.org
Usertags: hurd
The latest build of python-cffi for hurd-i386 (admittedly not a
release architecture) failed, per the below excerpts from [1]:
I: pybuild base:184: python2.7-dbg -m pytest c/ testing/
= test session starts
==
[...]
=== FAILURES
===
_ TestThread.test_init_different_modules_in_different_threads
__
self =
def test_init_different_modules_in_different_threads(self):
add1_cffi = self.prepare_module('add1')
add2_cffi = self.prepare_module('add2')
self.compile('thread2-test', [add1_cffi, add2_cffi], threads=True)
output = self.execute('thread2-test')
output = self._take_out(output, "preparing")
output = self._take_out(output, ".")
output = self._take_out(output, ".")
# at least the 3rd dot should be after everything from ADD2
> assert output == ("starting\n"
"prepADD2\n"
"adding 1000 and 200 and 30\n"
".\n"
"adding 40 and 2\n"
"done\n")
E AssertionError: assert 'starting\n.\...nd 30\ndone\n' ==
'starting\npre...and 2\ndone\n'
E starting
E + prepADD2
E + adding 1000 and 200 and 30
E .
E adding 40 and 2
E - prepADD2
E - adding 1000 and 200 and 30...
E
E ...Full output truncated (2 lines hidden), use '-vv' to show
testing/embedding/test_thread.py:29: AssertionError
Could you please take a look?
Thanks!
[1]
https://buildd.debian.org/status/fetch.php?pkg=python-cffi=hurd-i386=1.11.5-1=1519773174=0
--
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#892221: python-jpype: FTBFS on hurd-i386: jni_md_platform is not defined
Source: python-jpype Version: 0.6.2+dfsg-2 Severity: normal Tags: upstream User: debian-h...@lists.debian.org Usertags: hurd Builds of python-jpype for hurd-i386 (admittedly not a release architecture) have been failing, as most recently seen in [1]: setup.py:91: UserWarning: Your platform is not being handled explicitly. It may work or not! " It may work or not!", UserWarning) Traceback (most recent call last): File "setup.py", line 95, in [os.path.join(java_home, 'include', jni_md_platform)] NameError: name 'jni_md_platform' is not defined Per [2], the appropriate directory name here appears to be linux(!). Also, sys.platform starts with "gnu" on the Hurd. Could you please take a look? Thanks! [1] https://buildd.debian.org/status/fetch.php?pkg=python-jpype=hurd-i386=0.6.2%2Bdfsg-2=1518954986=0 [2] https://packages.debian.org/sid/hurd-i386/gcj-6-jdk/filelist -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#887681: python-tornado: FTBFS on hurd-i386: multiple test suite failures
cio module not present, curl client accepts invalid headers, localhost does not resolve to ipv6, needs fix, non-windows platform, pycares module not present, timing tests unreliable on travis, tornado.speedups module not present, unix sockets with SO_REUSEADDR not supported on this platform [E 180115 14:23:02 testing:737] FAIL [E 180115 14:23:02 runtests:186] logged 0 warnings and 1 errors -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#885246: peewee: FTBFS on hurd-i386: sqlite3.OperationalError: database is locked
Source: peewee Version: 2.10.2+dfsg-2 Severity: important Tags: upstream Justification: fails to build from source User: debian-h...@lists.debian.org Usertags: hurd-i386 The build of peewee for hurd-i386 (admittedly not a release architecture) failed with test suite errors boiling down to sqlite3.OperationalError: database is locked as detailed at https://buildd.debian.org/status/fetch.php?pkg=peewee=hurd-i386=2.10.2%2Bdfsg-2=1513960535=0. Could you please take a look? Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#883040: thumbor: FTBFS on hurd-i386: ZeroDivisionError calculating bytes/s
se_exc_info(failure)
File "/usr/lib/python2.7/dist-packages/tornado/stack_context.py", line 314,
in wrapped
ret = fn(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/tornado/concurrent.py", line 483, in
run_callback
result = future.result()
File "/usr/lib/python2.7/dist-packages/tornado/concurrent.py", line 232, in
result
raise_exc_info(self._exc_info)
File "/usr/lib/python2.7/dist-packages/tornado/stack_context.py", line 314,
in wrapped
ret = fn(*args, **kwargs)
File "thumbor/loaders/http_loader.py", line 93, in return_contents
context.metrics.timing('original_image.time_info.bytes_per_second',
len(response.body) / response.time_info['total'])
ZeroDivisionError: float division by zero
>> begin captured logging <<
tornado.curl_httpclient: DEBUG: GET http://localhost:40135/
tornado.curl_httpclient: DEBUG: Trying 127.0.0.1...
tornado.curl_httpclient: DEBUG: TCP_NODELAY set
tornado.curl_httpclient: DEBUG: Connected to localhost (127.0.0.1) port 40135
(#0)
tornado.curl_httpclient: DEBUG: > GET / HTTP/1.1
tornado.curl_httpclient: DEBUG: > Host: localhost:40135
tornado.curl_httpclient: DEBUG: > User-Agent: Thumbor/6.3.2
tornado.curl_httpclient: DEBUG: > Accept: */*
tornado.curl_httpclient: DEBUG: > Accept-Encoding: gzip,deflate
tornado.curl_httpclient: DEBUG: >
tornado.access: INFO: 200 GET / (127.0.0.1) 0.00ms
tornado.curl_httpclient: DEBUG: < HTTP/1.1 200 OK
tornado.curl_httpclient: DEBUG: < Date: Sun, 26 Nov 2017 00:55:58 GMT
tornado.curl_httpclient: DEBUG: < Content-Length: 5
tornado.curl_httpclient: DEBUG: < Etag:
"f7ff9e8b7bb2e09b70935a5d785e0cc5d9d0abf0"
tornado.curl_httpclient: DEBUG: < Content-Type: text/html; charset=UTF-8
tornado.curl_httpclient: DEBUG: < Server: TornadoServer/4.3
tornado.curl_httpclient: DEBUG: <
tornado.curl_httpclient: DEBUG: Connection #0 to host localhost left intact
thumbor: DEBUG: METRICS: timing: original_image.fetch.200.localhost:40135:10
thumbor: DEBUG: METRICS: inc: original_image.status.200:1
thumbor: DEBUG: METRICS: timing: original_image.time_info.redirect:0
thumbor: DEBUG: METRICS: timing: original_image.time_info.queue:0
thumbor: DEBUG: METRICS: timing: original_image.time_info.pretransfer:0
thumbor: DEBUG: METRICS: timing: original_image.time_info.starttransfer:0
thumbor: DEBUG: METRICS: timing: original_image.time_info.connect:0
thumbor: DEBUG: METRICS: timing: original_image.time_info.total:0
thumbor: DEBUG: METRICS: timing: original_image.time_info.namelookup:0
- >> end captured logging << -
--
Ran 424 tests in 25.180s
FAILED (SKIP=3, errors=6)
--
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#883039: thumbor: FTBFS (64-bit big-endian): test segmentation fault
Source: thumbor Version: 6.3.2-3 Severity: important Tags: upstream Justification: fails to build from source User: debian-s...@lists.debian.org Usertags: s390x Builds of thumbor have been failing for 64-bit big-endian architectures because the test suite encounters a segmentation fault. Specifically, these errors occurred on s390x and the non-release architecture ppc64; sparc64 is missing some build dependencies. I don't have additional details, but perhaps you can reproduce the problem on a porter box. Could you please take a look? Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#883038: thumbor: FTBFS (32-bit big-endian): orientation-related tests fail
ne 285, in _assert_topic return _registered_assertions[method_name](self.topic, *args, **kw) File "/usr/lib/python2.7/dist-packages/preggy/core.py", line 58, in wrapper func(*args, **kw) File "/usr/lib/python2.7/dist-packages/preggy/assertions/types/boolean.py", line 21, in to_be_true raise AssertionError(msg) AssertionError: Expected topic(False) to be truthy >> begin captured logging << preggy.utils: DEBUG: fetching assertion: 'to_be_false' preggy.utils: DEBUG: fetching assertion: 'to_be_true' - >> end captured logging << - == FAIL: test_reorientate4 (tests.engines.test_base_engine.BaseEngineTestCase) -- Traceback (most recent call last): File "/«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/tests/engines/test_base_engine.py", line 271, in test_reorientate4 expect(self.engine.flip_vertically.called).to_be_true() File "/usr/lib/python2.7/dist-packages/preggy/core.py", line 285, in _assert_topic return _registered_assertions[method_name](self.topic, *args, **kw) File "/usr/lib/python2.7/dist-packages/preggy/core.py", line 58, in wrapper func(*args, **kw) File "/usr/lib/python2.7/dist-packages/preggy/assertions/types/boolean.py", line 21, in to_be_true raise AssertionError(msg) AssertionError: Expected topic(False) to be truthy >> begin captured logging << preggy.utils: DEBUG: fetching assertion: 'to_be_false' preggy.utils: DEBUG: fetching assertion: 'to_be_false' preggy.utils: DEBUG: fetching assertion: 'to_be_true' - >> end captured logging << - == FAIL: test_reorientate5 (tests.engines.test_base_engine.BaseEngineTestCase) -- Traceback (most recent call last): File "/«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/tests/engines/test_base_engine.py", line 285, in test_reorientate5 expect(self.image).to_equal(((1, 2), (3, 4))) File "/usr/lib/python2.7/dist-packages/preggy/core.py", line 285, in _assert_topic return _registered_assertions[method_name](self.topic, *args, **kw) File "/usr/lib/python2.7/dist-packages/preggy/core.py", line 58, in wrapper func(*args, **kw) File "/usr/lib/python2.7/dist-packages/preggy/core.py", line 126, in test_assertion raise AssertionError(err_msg) AssertionError: Expected topic(((1, 3), (2, 4))) to equal ((1, 2), (3, 4)) >> begin captured logging << preggy.utils: DEBUG: fetching assertion: 'to_equal' - >> end captured logging << - == FAIL: test_reorientate7 (tests.engines.test_base_engine.BaseEngineTestCase) -- Traceback (most recent call last): File "/«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/tests/engines/test_base_engine.py", line 312, in test_reorientate7 expect(self.image).to_equal(((1, 2), (3, 4))) File "/usr/lib/python2.7/dist-packages/preggy/core.py", line 285, in _assert_topic return _registered_assertions[method_name](self.topic, *args, **kw) File "/usr/lib/python2.7/dist-packages/preggy/core.py", line 58, in wrapper func(*args, **kw) File "/usr/lib/python2.7/dist-packages/preggy/core.py", line 126, in test_assertion raise AssertionError(err_msg) AssertionError: Expected topic(((4, 2), (3, 1))) to equal ((1, 2), (3, 4)) -------- >> begin captured logging << preggy.utils: DEBUG: fetching assertion: 'to_equal' - >> end captured logging << - -- Ran 424 tests in 29.200s FAILED (SKIP=3, errors=3, failures=5) -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#883028: thumbor: FTBFS: Async operation timed out after 5 seconds
etch
return self.wait()
File "/usr/lib/python2.7/dist-packages/tornado/testing.py", line 336, in wait
self.__rethrow()
File "/usr/lib/python2.7/dist-packages/tornado/testing.py", line 272, in
__rethrow
raise_exc_info(failure)
File "/usr/lib/python2.7/dist-packages/tornado/testing.py", line 320, in
timeout_func
timeout)
AssertionError: Async operation timed out after 5 seconds
>> begin captured logging <<
thumbor: DEBUG: METRICS: inc: response.count:1
thumbor: DEBUG: METRICS: inc: storage.miss:1
PIL.PngImagePlugin: DEBUG: STREAM 'IHDR' 16 13
PIL.PngImagePlugin: DEBUG: STREAM 'bKGD' 41 6
PIL.PngImagePlugin: DEBUG: 'bKGD' 41 6 (unknown)
PIL.PngImagePlugin: DEBUG: STREAM 'IDAT' 59 8192
thumbor: DEBUG: creating tempfile for Commons-logo-inches.svg in
/tmp/tmp6BGTzs/5e/18b757cde8521bbe891f7ca5e459a1dfc54b99.b5fdf46c1c594b5ebd144feab7682692...
thumbor: DEBUG: moving tempfile
/tmp/tmp6BGTzs/5e/18b757cde8521bbe891f7ca5e459a1dfc54b99.b5fdf46c1c594b5ebd144feab7682692
to /tmp/tmp6BGTzs/5e/18b757cde8521bbe891f7ca5e459a1dfc54b99...
thumbor: DEBUG: No image format specified. Retrieving from the image extension:
.svg.
thumbor: DEBUG: Content Type of image/svg+xml detected.
tornado.access: INFO: 200 GET /unsafe/Commons-logo-inches.svg (127.0.0.1)
10207.16ms
thumbor: DEBUG: METRICS: timing: response.time:10201
thumbor: DEBUG: METRICS: timing: response.time.200:10201
thumbor: DEBUG: METRICS: inc: response.status.200:1
thumbor: DEBUG: METRICS: inc: response.format.png:1
thumbor: DEBUG: METRICS: timing: response.time.png:10201
thumbor: DEBUG: METRICS: inc: response.bytes.png:142841
- >> end captured logging << -
--
Ran 424 tests in 167.687s
FAILED (SKIP=3, failures=2)
(192,227),(224,240),(244,247),(255,252)],[(0,48),(16,50),(62,77),(92,110),(128,144),(140,153),(167,180),(192,192),(224,217),(244,225),(255,225)])/gradient.gif)
SUCCESS
(unsafe/filters:curve([(0,0),(255,255)],[(0,50),(16,51),(32,69),(58,85),(92,120),(128,170),(140,186),(167,225),(192,245),(225,255),(244,255),(255,254)],[(0,0),(16,2),(32,18),(64,59),(92,116),(128,182),(167,211),(192,227),(224,240),(244,247),(255,252)],[(0,48),(16,50),(62,77),(92,110),(128,144),(140,153),(167,180),(192,192),(224,217),(244,225),(255,225)])/animated.gif)
Joining threads
E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: cd
/<>/.pybuild/pythonX.Y_2.7/build; python2.7 -m nose -s
integration_tests/ tests/ --ignore-files=test_statsd_metrics.py
--ignore-files=test_sentry.py --ignore-files=test_queued_detector.py
--ignore-files=test_distributed_collage.py
--exclude=test_convert_svg_already_converted_to_png
--exclude=test_convert_not_well_formed_svg_to_png
dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
debian/rules:11: recipe for target 'build-arch' failed
make: *** [build-arch] Error 25
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit
status 2
E: Build killed with signal TERM after 150 minutes of inactivity
--
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#881685: pythonqt: FTBFS on ppc64: cannot find -lPythonQt-Qt5-Python3.6
Source: pythonqt Version: 3.2-4 Severity: important Tags: upstream Justification: fails to build from source (but built successfully in the past) User: debian-powe...@lists.debian.org Usertags: ppc64 Builds of pythonqt for ppc64 (admittedly not a release architecture) have been failing lately: /usr/bin/ld: cannot find -lPythonQt-Qt5-Python3.6 collect2: error: ld returned 1 exit status Makefile:403: recipe for target '../../lib/libPythonQt_QtAll-Qt5-Python3.6.so.3.2.0' failed Make then finishes building libPythonQt-Qt5-Python3.6 in a parallel job, so the issue presumably stems from not fully accounting for parallel make; I'm not sure offhand why it specifically impacts ppc64, but it does. (I see that PythonQt.pro already declares CONFIG += ordered so perhaps the real bug is in qmake, but I suppose you could work around it by building fully sequentially here.) Could you please take a look? Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#879259: python-lupa FTBFS on ppc64el: test_coroutine_sets_callback_debug_hook_nowrap (lupa.tests.test.TestLuaCoroutinesWithDebugHooks) ... Segmentation fault
Source: python-lupa Followup-For: Bug #879259 User: debian-powe...@lists.debian.org FTR, this same error also occurs on the big-endian non-release variant ppc64. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#861256: pygame: FTBFS on sh4: surface_test.AllTestCases times out
Source: pygame Version: 1.9.1release+dfsg-10+b2 Severity: important Justification: fails to build from source (but built successfully in the past) The sh4 build of pygame failed, per the log excerpt below, from https://buildd.debian.org/status/fetch.php?pkg=pygame=sh4=1.9.3%2Bdfsg-2=1493197569=0 Could you please take a look? Thanks! ERROR: all_tests_for (pygame.tests.surface_test.AllTestCases) -- Traceback (most recent call last): File "test/pygame.tests.surface_test.py", line 1, in all_tests_for subprocess completely failed with return code of "Process timed out (time_out = 120 secs) and was successfully terminated" cmd: ['/usr/bin/python3.5', '-m', 'pygame.tests.test_utils.test_runner', 'pygame.tests.surface_test', '--exclude', 'opengl,interactive,subprocess_ignore,python3_ignore'] test_env: [...] working_dir: /tmp/tmpqaf65cf7 return (first 10 and last 10 lines): WARNING: You are using the SDL disk writer audio driver! Writing to file [sdlaudio.raw]. WARNING: You are using the SDL disk writer audio driver! Writing to file [sdlaudio.raw]. WARNING: You are using the SDL disk writer audio driver! Writing to file [sdlaudio.raw]. WARNING: You are using the SDL disk writer audio driver! Writing to file [sdlaudio.raw]. WARNING: You are using the SDL disk writer audio driver! Writing to file [sdlaudio.raw]. ... WARNING: You are using the SDL disk writer audio driver! Writing to file [sdlaudio.raw]. WARNING: You are using the SDL disk writer audio driver! Writing to file [sdlaudio.raw]. WARNING: You are using the SDL disk writer audio driver! Writing to file [sdlaudio.raw]. /usr/lib/python3.5/runpy.py:125: RuntimeWarning: 'pygame.tests.test_utils.test_runner' found in sys.modules after import of package 'pygame.tests.test_utils', but prior to execution of 'pygame.tests.test_utils.test_runner'; this may result in unpredictable behaviour warn(RuntimeWarning(msg)) loading pygame.tests.surface_test <--!! TES -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#861253: pygame: FTBFS (64-bit BE): BufferProxyLegacyTest.test_write fails
Source: pygame Version: 1.9.1release+dfsg-10+b2 Severity: serious Justification: fails to build from source (but built successfully in the past) Builds of pygame for 64-bit big-endian architectures (s390x and the non-release architectures ppc64 and sparc64) failed: ERROR: test_write (pygame.tests.bufferproxy_test.BufferProxyLegacyTest) -- Traceback (most recent call last): File "/<>/pygame-1.9.3+dfsg/.pybuild/pythonX.Y_2.7/build/pygame/tests/bufferproxy_test.py", line 469, in test_write bp.write(data[:3], 2) IndexError: 'offset' is out of range All of these architectures encountered additional test-suite errors, which I've already reported separately (#861249, #861250). Could you please take a look? Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#861254: pygame: FTBFS on kFreeBSD: /dev/uhid3: No such file or directory
Source: pygame Version: 1.9.1release+dfsg-10+b2 Severity: important Justification: fails to build from source (but built successfully in the past) Builds of pygame for kfreebsd-amd64 and kfreebsd-i386 failed: == FAIL: test_get_error (pygame.tests.base_test.BaseModuleTest) -- Traceback (most recent call last): File "/«BUILDDIR»/pygame-1.9.3+dfsg/.pybuild/pythonX.Y_2.7/build/pygame/tests/base_test.py", line 572, in test_get_error e) AssertionError: /dev/uhid3: No such file or directory == FAIL: test_set_error (pygame.tests.base_test.BaseModuleTest) -- Traceback (most recent call last): File "/«BUILDDIR»/pygame-1.9.3+dfsg/.pybuild/pythonX.Y_2.7/build/pygame/tests/base_test.py", line 589, in test_set_error e) AssertionError: /dev/uhid3: No such file or directory Could you please take a look? Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#861252: pygame: FTBFS on ppc64el: some color-handling tests fail
Source: pygame Version: 1.9.1release+dfsg-10+b2 Severity: serious Justification: fails to build from source (but built successfully in the past) The ppc64el build of pygame failed: == FAIL: test_save_colorkey (pygame.tests.image_test.ImageModuleTest) make sure the color key is not changed when saving. -- Traceback (most recent call last): File "/<>/pygame-1.9.3+dfsg/.pybuild/pythonX.Y_2.7/build/pygame/tests/image_test.py", line 283, in test_save_colorkey self.assertEqual(p1, s2.get_at((0,0))) AssertionError: (23, 23, 23, 255) != (23, 23, 255, 23) == FAIL: test_cross (pygame.tests.math_test.Vector2TypeTest) [as per #861249] == FAIL: test_blanket_alpha (pygame.tests.surface_test.SurfaceSelfBlitTest) -- Traceback (most recent call last): File "/<>/pygame-1.9.3+dfsg/.pybuild/pythonX.Y_2.7/build/pygame/tests/surface_test.py", line 2331, in test_blanket_alpha self._assert_same(surf, comp) File "/<>/pygame-1.9.3+dfsg/.pybuild/pythonX.Y_2.7/build/pygame/tests/surface_test.py", line 2252, in _assert_same a.get_bitsize( AssertionError: (255, 0, 0, 255) != (0, 255, 170, 255), bpp: 8 == FAIL: test_colorkey (pygame.tests.surface_test.SurfaceSelfBlitTest) -- Traceback (most recent call last): File "/<>/pygame-1.9.3+dfsg/.pybuild/pythonX.Y_2.7/build/pygame/tests/surface_test.py", line 2311, in test_colorkey self._assert_same(surf, comp) File "/<>/pygame-1.9.3+dfsg/.pybuild/pythonX.Y_2.7/build/pygame/tests/surface_test.py", line 2252, in _assert_same a.get_bitsize( AssertionError: (255, 0, 0, 255) != (0, 255, 0, 255), bpp: 8 Could you please take a look? Thanks! -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (300, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386, x32 Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#861250: pygame: FTBFS (big-endian): test_get_bounding_rect fails
Source: pygame Version: 1.9.1release+dfsg-10+b2 Severity: serious Justification: fails to build from source (but built successfully in the past) Builds of pygame for big-endian architectures (mips, s390x, and the non-release architectures hppa, powerpc, ppc64, and sparc64) all failed: FAIL: test_get_bounding_rect (pygame.tests.surface_test.SurfaceTypeTest) -- Traceback (most recent call last): File "/«BUILDDIR»/pygame-1.9.3+dfsg/.pybuild/pythonX.Y_2.7/build/pygame/tests/surface_test.py", line 154, in test_get_bounding_rect self.assertEqual(bound_rect.width, 0) AssertionError: 1 != 0 On most of these architectures (all but mips and hppa), there were additional test suite failures, which I'm reporting separately. I presume the non-release architectures m68k and powerpcspe would have encountered the same error if those builds hadn't silently skipped the test suite altogether for some reason. Could you please take a look? Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#861249: FTBFS: math_test.Vector2TypeTest.test_cross fails
Source: pygame Version: 1.9.1release+dfsg-10+b2 Severity: serious Justification: fails to build from source (but built successfully in the past) pygame FTBFS on several architectures (arm64, ppc64el, s390x, and the non-release architectures powerpc and ppc64): FAIL: test_cross (pygame.tests.math_test.Vector2TypeTest) -- Traceback (most recent call last): File "/<>/pygame-1.9.3+dfsg/.pybuild/pythonX.Y_2.7/build/pygame/tests/math_test.py", line 360, in test_cross self.assertEqual(self.v1.cross(self.v1), 0) AssertionError: -3.2862601528904633e-16 != 0 On most of these architectures (all but arm64), there were additional test suite failures, which I'll report separately. I presume the non-release architecture powerpcspe would have encountered the same error if that build hadn't silently skipped the test suite altogether for some reason. Could you please take a look? Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#841374: cf-python: FTBFS: dh: unable to load addon sphinxdoc
Source: cf-python Version: 1.3.2+dfsg1-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Builds of cf-python in minimal environments geared towards building only its architecture-dependent python-cf binary package (as on the autobuilders) have been failing: fakeroot debian/rules clean dh clean --with python2,sphinxdoc --buildsystem=pybuild dh: unable to load addon sphinxdoc: Can't locate Debian/Debhelper/Sequence/sphinxdoc.pm in @INC (you may need to install the Debian::Debhelper::Sequence::sphinxdoc module) (@INC contains: [...]) at (eval 12) line 2. BEGIN failed--compilation aborted at (eval 12) line 2. debian/rules:11: recipe for target 'clean' failed make: *** [clean] Error 2 Please either conditionalize the usage of --with-sphinxdoc appropriately or move python-sphinx from Build-Depends-Indep to Build-Depends. Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#825095: python-backports-shutil-get-terminal-size: clashes over backports/__init__.py with python-backports.ssl-match-hostname
Package: python-backports-shutil-get-terminal-size Version: 1.0.0-1 Severity: serious Justification: Policy 6.6(4) python-backports-shutil-get-terminal-size is impossible to install alongside python-backports.ssl-match-hostname: Unpacking python-backports-shutil-get-terminal-size (1.0.0-1) ... dpkg: error processing archive /var/cache/apt/archives/python-backports-shutil-get-terminal-size_1.0.0-1_all.deb (--unpack): trying to overwrite '/usr/lib/python2.7/dist-packages/backports/__init__.py', which is also in package python-backports.ssl-match-hostname 3.4.0.2-1 Could you please take a look? Thanks! -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (300, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.5.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#819997: python-feather-format: FTBFS on i386: low is out of bounds for int32
Source: python-feather-format Version: 0.1.0-1 Severity: important Justification: fails to build from source The i386 build of python-feather-format failed: == ERROR: test_integer_no_nulls (feather.tests.test_reader.TestFeatherReader) -- Traceback (most recent call last): File "/«PKGBUILDDIR»/feather/tests/test_reader.py", line 126, in test_integer_no_nulls size=num_values) File "mtrand.pyx", line 1260, in mtrand.RandomState.randint (numpy/random/mtrand/mtrand.c:14127) ValueError: low is out of bounds for int32 -- Ran 14 tests in 0.099s FAILED (errors=1) Could you please take a look? Thanks! ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#806383: python-igraph: FTBFS on *i386: testMultilevel AssertionError
Source: python-igraph Version: 0.7.1.post6-2 Severity: important Justification: fails to build from source Thanks for promptly fixing python-igraph's build dependencies! Automatic builds now succeed for most architectures, but still fail on i386, hurd-i386, and kfreebsd-i386: == FAIL: testMultilevel (igraph.test.decomposition.CommunityTests) -- Traceback (most recent call last): File "/«PKGBUILDDIR»/igraph/test/decomposition.py", line 243, in testMultilevel self.assertTrue(cls[0].membership == [0,0,0,1,0,0,1,1,2,2,2,3,2,3,2,2]) AssertionError: False is not true -- Ran 307 tests in 7.597s FAILED (failures=1, skipped=3) This error may well reflect a bug in the underlying igraph library; if so, please feel free to reassign it accordingly, though you might want to mark it as affecting this package so nobody tries to report it again. At any rate, please do take a look. Thanks! ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#806230: python-igraph: FTBFS: Cannot find C igraph using pkg-config.
Source: python-igraph
Version: 0.7.1.post6-1
Severity: serious
Justification: fails to build from source
Builds of python-igraph in minimal environments have been failing:
running build_ext
Cannot find the C core of igraph on this system using pkg-config.
We will now try to download and compile the C core from scratch.
Version number of the C core: 0.7.1.post6
We will also try: 0.7.1
Version 0.7.1.post6 of the C core of igraph is not found among the nightly
builds.
Use the --c-core-version switch to try a different version.
Could not download and compile the C core of igraph.
E: pybuild pybuild:274: build: plugin distutils failed with: exit code=1:
/usr/bin/python setup.py build
dh_auto_build: pybuild --build -i python{version} -p 2.7 --dir . returned
exit code 13
debian/rules:6: recipe for target 'build-arch' failed
make: *** [build-arch] Error 25
Please declare a build dependency on pkg-config.
Thanks!
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#796902: python-scipy: FTBFS: dh: unable to load addon sphinxdoc
Source: python-scipy Version: 0.16.0-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Builds of python-scipy in minimal environments geared for building only its architecture-dependent binary packages have been failing with errors along the lines of dpkg-buildpackage: host architecture arm64 fakeroot debian/rules clean dh clean --with python2,python3,sphinxdoc dh: unable to load addon sphinxdoc: Can't locate Debian/Debhelper/Sequence/sphinxdoc.pm in @INC (you may need to install the Debian::Debhelper::Sequence::sphinxdoc module) (@INC contains: /etc/perl /usr/local/lib/aarch64-linux-gnu/perl/5.20.2 /usr/local/share/perl/5.20.2 /usr/lib/aarch64-linux-gnu/perl5/5.20 /usr/share/perl5 /usr/lib/aarch64-linux-gnu/perl/5.20 /usr/share/perl/5.20 /usr/local/lib/site_perl .) at (eval 5) line 2. BEGIN failed--compilation aborted at (eval 5) line 2. make: *** [clean] Error 2 debian/rules:16: recipe for target 'clean' failed Please either conditionalize the use of --with sphinxdoc appropriately or move python-sphinx from Build-Depends-Indep to Build-Depends. Thanks! ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#767394: python-django-assets: dist-packages/tests/__init__.py conflict
Package: python-django-assets Version: 0.10-1 Severity: serious Justification: Policy 6.6 (4) python-django-assets and python3-django-assets respectively ship the overly generic paths /usr/lib/python2.7/dist-packages/tests/__init__.py and /usr/lib/python3/dist-packages/tests/__init__.py, leading to de facto conflicts with similarly broken packages. Please either install these tests somewhere less likely to cause trouble or omit them altogether. Thanks! ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#767400: python3-websocket: dist-packages/tests/__init__.py conflict
Package: python3-websocket Version: 0.18.0-1 Severity: serious Justification: Policy 6.6 (4) python3-websocket ships the overly generic path /usr/lib/python3/dist-packages/tests/__init__.py, leading to de facto conflicts with similarly broken packages. Please either install these tests somewhere less likely to cause trouble or omit them altogether. (It looks like python-websocket already does the latter.) Thanks! ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#763716: python-pythonmagick: ships unstripped static archive
Package: python-pythonmagick Version: 0.9.11-1 Severity: minor python-pythonmagick's disk usage on amd64 has jumped from under 3 MB to nearly 90, and https://packages.debian.org/sid/python-pythonmagick shows similar numbers for other architectures. The culprit appears to be /usr/lib/python2.7/dist-packages/PythonMagick/_PythonMagick.a, for which I see no need. If that file really is necessary for some reason (which I'd be curious to know), please at least strip its debug information by default. (dh_strip evidently skips it because its filename doesn't contain lib.) Thanks! -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (300, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages python-pythonmagick depends on: ii libboost-python1.55.0 1.55.0+dfsg-3 ii libc6 2.19-11 ii libgcc11:4.9.1-15 ii libgomp1 4.9.1-15 ii libmagick++-6.q16-58:6.8.9.6-4 ii libmagickcore-6.q16-2 8:6.8.9.6-4 ii libmagickwand-6.q16-2 8:6.8.9.6-4 ii libstdc++6 4.9.1-15 ii python 2.7.8-1 python-pythonmagick recommends no packages. python-pythonmagick suggests no packages. -- no debconf information ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#758175: blist: FTBFS: Python.h: No such file or directory
Source: blist Version: 1.3.6-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Builds of blist in minimal environments (as on the autobuilders) have been failing: blist/_blist.c:38:20: fatal error: Python.h: No such file or directory Please substitute python(3)-all-dev for python(3)-all in Build-Depends to account for the fact that blist builds a binary extension, not just a module. Thanks! ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#745691: django-classy-tags: FTBFS: Sphinx documentation not found
notfound 745691 0.3.4.1-1 found 745691 0.5.1-1 thanks Evgeni Golov evg...@debian.org writes: Did you mean 0.5.1-1? Yes; reportbug evidently thought I was reporting on the version I have installed, from testing. There is a -2 in SVN, which makes the package arch:all and thus should fix this issue? That's an even better fix, assuming the contents are in fact architecture-independent. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#745690: sphinx-common: dh_sphinxdoc always insists on documentation
Package: sphinx-common Version: 1.2.2+dfsg-1 Severity: normal In the course of tracking build failures affecting new packages, I've found one common problem to be placing documentation in a separate architecture-independent package (as Policy encourages) but unconditionally invoking dh --with sphinxdoc, which fails the build when it finds no Sphinx documentation to process: dh_sphinxdoc -a dh_sphinxdoc: Sphinx documentation not found make: *** [binary-arch] Error 2 This failure mode has come up a lot; I've already reported #663985, #670955, #718231, #719176, #721779, #721780, and #738735, and now see that django-classy-tags has run into the same issue (to be reported shortly). I do see the value in having a sanity check, but note that other dh_ commands are typically safe to run if they have nothing to do. Could you please consider either downgrading this error to a warning or disabling it altogether, at least when invoked with -a? Thanks! -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (300, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages sphinx-common depends on: ii libjs-sphinxdoc 1.2.2+dfsg-1 Versions of packages sphinx-common recommends: ii python-sphinx 1.2.2+dfsg-1 ii python3-sphinx 1.2.2+dfsg-1 sphinx-common suggests no packages. -- no debconf information ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#745691: django-classy-tags: FTBFS: Sphinx documentation not found
Source: django-classy-tags Version: 0.3.4.1-1 Severity: serious Justification: fails to build from source Builds of django-classy-tags covering only its main architecture-dependent binary package (as on the autobuilders) have been failing: fakeroot debian/rules binary-arch dh binary-arch --with python2,sphinxdoc ... dh_sphinxdoc -a dh_sphinxdoc: Sphinx documentation not found make: *** [binary-arch] Error 2 This is arguably a case of dh_sphinxdoc being too strict (reported as #745690); until and unless that changes, though, please arrange to supply --with sphinxdoc only when actually building the -doc package. Thanks! ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#734521: pyzmq: FTBFS for s390x: test_timeout AssertionError
Source: pyzmq Version: 14.0.1-1 Severity: serious Justification: fails to build from source (but built successfully in the past) The s390x build of pyzmq failed with an AssertionError when trying to run the unit test under Python 2.7: Traceback (most recent call last): File zmq/tests/test_poll.py, line 176, in test_timeout self.assertTrue(toc-tic 0.1) AssertionError: False is not true Could you please take a look? You can find the full log at https://buildd.debian.org/status/fetch.php?pkg=pyzmqarch=s390xver=14.0.1-1stamp=1389093313 Thanks! ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#734518: pyzmq: FTBFS on i386: pypy build reports ImportError
Source: pyzmq
Version: 14.0.1-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
The i386 build of pyzmq for pypy failed with an ImportError, as detailed at
https://buildd.debian.org/status/fetch.php?pkg=pyzmqarch=i386ver=14.0.1-1stamp=1389093279:
pypy -c 'import zmq'
Traceback (most recent call last):
File app_main.py, line 72, in run_toplevel
File app_main.py, line 566, in run_it
File string, line 1, in module
File zmq/__init__.py, line 62, in module
from zmq.backend import *
File zmq/backend/__init__.py, line 22, in module
_ns = select_backend('zmq.backend.cffi')
File zmq/backend/select.py, line 31, in select_backend
mod = __import__(name, fromlist=public_api)
File zmq/backend/cffi/__init__.py, line 46, in module
from zmq.backend.cffi import (constants, error, message, context, socket,
File zmq/backend/cffi/constants.py, line 4, in module
from ._cffi import C, c_constant_names
File zmq/backend/cffi/_cffi.py, line 180, in module
Please check that you have zeromq headers and libraries. % e)
ImportError: PyZMQ CFFI backend couldn't find zeromq: unsupported operand
type(s) for +: 'str' and 'list'
Please check that you have zeromq headers and libraries.
Could you please take a look?
Thanks!
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#734518: pyzmq: FTBFS on i386: pypy build reports ImportError
Julian Taylor jtaylor.deb...@googlemail.com writes: its because pypy 2.2 has not built on i386 yet, a cffi function has a different return value in 2.1. I see; thanks for the prompt explanation! In that case, I'd recommend versioning pyzmq's build dependency on pypy accordingly. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#721779: billiard: FTBFS: dh: unable to load addon sphinxdoc
found 721779 2.7.3.32-2 thanks Thanks for looking into this bug! Alas, moving sphinx to the main Build-Depends field (from -Indep) merely shifted the error: dh_sphinxdoc -a -O--buildsystem=python_distutils dh_sphinxdoc: Sphinx documentation not found Please arrange to use --with sphinxdoc only when actually building the -doc package, as I'd originally suggested. ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#721779: billiard: FTBFS: dh: unable to load addon sphinxdoc
Source: billiard Version: 2.7.3.32-1 Severity: serious Justification: fails to build from source Builds of billiard in minimal environments geared towards building only its architecture-dependent binary package (python-billiard) have been failing due to its unconditional use of dh --with sphinxdoc: dh clean --with python2,sphinxdoc --buildsystem=python_distutils dh: unable to load addon sphinxdoc: Can't locate Debian/Debhelper/Sequence/sphinxdoc.pm in @INC (you may need to install the Debian::Debhelper::Sequence::sphinxdoc module) (@INC contains: /etc/perl /usr/local/lib/perl/5.18.1 /usr/local/share/perl/5.18.1 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.18 /usr/share/perl/5.18 /usr/local/lib/site_perl .) at (eval 11) line 2. BEGIN failed--compilation aborted at (eval 11) line 2. make: *** [clean] Error 2 As I recall, using --with sphinxdoc can also lead to errors when not building the documentation, so I'd strongly recommend simply conditionalizing its usage appropriately. Could you please look into it? Thanks! ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#718900: python3-numpy: .so files missing on kFreeBSD
Package: python3-numpy Version: 1:1.7.1-2+b1 Severity: important The kFreeBSD python3-numpy packages somehow lack .so files, making them unusable and causing matplotlib to FTBFS: $ dpkg -L python3-numpy | fgrep .so $ python3 Python 3.3.2+ (default, Aug 4 2013, 21:56:44) [GCC 4.8.1] on gnukfreebsd9 Type help, copyright, credits or license for more information. import numpy Traceback (most recent call last): File stdin, line 1, in module File /usr/lib/python3/dist-packages/numpy/__init__.py, line 137, in module from . import add_newdocs File /usr/lib/python3/dist-packages/numpy/add_newdocs.py, line 9, in module from numpy.lib import add_newdoc File /usr/lib/python3/dist-packages/numpy/lib/__init__.py, line 4, in module from .type_check import * File /usr/lib/python3/dist-packages/numpy/lib/type_check.py, line 8, in module import numpy.core.numeric as _nx File /usr/lib/python3/dist-packages/numpy/core/__init__.py, line 5, in module from . import multiarray ImportError: cannot import name multiarray BUILDING MATPLOTLIB matplotlib: yes [1.3.0] python: yes [3.3.2+ (default, Aug 4 2013, 21:56:44) [GCC 4.8.1]] platform: yes [gnukfreebsd9] REQUIRED DEPENDENCIES AND EXTENSIONS Requires numpy 1.5 or later to build. (Numpy not found) make: *** [build-3.3-stamp] Error 1 dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 Curiously, python3-numpy-dbg and python-numpy are both fine, as is python3-numpy on other platforms. Could you please take a look? Thanks! ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#511042: /usr/share/pyshared-data/python-chaco lists *LICENSE* again
found 511042 3.2.0-1 thanks This bug appears to be back: | Setting up python-chaco (3.2.0-1) ... | file does not exist: /usr/lib/python2.4/site-packages/enthought/chaco/LICENSE | file does not exist: /usr/lib/python2.4/site-packages/enthought/chaco/tools/toolbars/images/image_LICENSE.txt | file does not exist: /usr/lib/python2.4/site-packages/enthought/chaco2/LICENSE | pycentral: pycentral pkginstall: error byte-compiling files (372) | pycentral pkginstall: error byte-compiling files (372) | dpkg: error processing python-chaco (--configure): | subprocess installed post-installation script returned error exit status 1 Could you please fix it? Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) Finger a...@monk.mit.edu (NOT a valid e-mail address) for more info. ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#511042: /u/s/pyshared-data/python-chaco lists nonexistent LICENSE files
Package: python-chaco Version: 3.0.1-1 Severity: grave Justification: renders package unusable (uninstallable) At least on amd64, python-chaco.postinst's call to pycentral pkginstall python-chaco fails because /usr/share/pyshared-data/python-chaco lists three files not actually present under /usr/share/pyshared: /usr/share/pyshared/enthought/chaco2/LICENSE=f /usr/share/pyshared/enthought/chaco/LICENSE=f /usr/share/pyshared/enthought/chaco/tools/toolbars/images/image_LICENSE.txt=f Could you please ensure that the listing actually agrees with the filesystem? Thanks! -- System Information: Debian Release: 5.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/python-modules-team
