o-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
- 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.
an.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-tea
s 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
--
Aar
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
6 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:
.
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
-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))
-------- &
=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/rule
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
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
s.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 (am
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)
ht
ecent 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 a
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
ncountered 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...@mo
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
___
Pyt
.
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
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) ...
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
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:
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
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
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
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
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
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
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
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
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
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
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:
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
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
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
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
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
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
38 matches
Mail list logo
