[Python-modules-team] Bug#880338: python-thriftpy: FTBFS: dpkg-buildpackage: error: dpkg-source -b python-thriftpy-0.3.9 subprocess returned exit status 2

[Lucas Nussbaum]

Source: python-thriftpy
Version: 0.3.9-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20171030 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_clean --exclude=.c
> make[1]: Leaving directory '/<>'
>  dpkg-source -b python-thriftpy-0.3.9
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building python-thriftpy using existing 
> ./python-thriftpy_0.3.9.orig.tar.gz
> dpkg-source: info: local changes detected, the modified files are:
>  python-thriftpy-0.3.9/thriftpy/protocol/cybin/cybin.c
>  python-thriftpy-0.3.9/thriftpy/transport/cybase.c
>  python-thriftpy-0.3.9/thriftpy/transport/framed/cyframed.c
>  python-thriftpy-0.3.9/thriftpy/transport/memory/cymemory.c
> dpkg-source: error: aborting due to unexpected upstream changes, see 
> /tmp/python-thriftpy_0.3.9-1.diff.cyb9Jm
> dpkg-source: info: you can integrate the local changes with dpkg-source 
> --commit
> dpkg-buildpackage: error: dpkg-source -b python-thriftpy-0.3.9 subprocess 
> returned exit status 2
> 
> Build finished at 2017-10-30T12:42:55Z

The full build log is available from:
   http://aws-logs.debian.net/2017/10/30/python-thriftpy_0.3.9-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#880315: pythonqt: FTBFS: build-dependency not installable: libpythonqt-dev

[Lucas Nussbaum]

Source: pythonqt
Version: 3.2-3
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20171030 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: cmake, debhelper (>= 10), libgtk2.0-dev, libpulse-dev, 
> libpythonqt-dev, libqt5designer5, libqt5multimediawidgets5, 
> libqt5opengl5-dev, libqt5svg5-dev, libqt5xmlpatterns5-dev, libqtwebkit-dev, 
> pyqt5-dev, pyqt5-dev-tools, python-dev, python3-pyside.qtuitools, qt5-qmake, 
> qtbase5-private-dev, qtdeclarative5-dev, qtmultimedia5-dev, qttools5-dev
> Filtered Build-Depends: cmake, debhelper (>= 10), libgtk2.0-dev, 
> libpulse-dev, libpythonqt-dev, libqt5designer5, libqt5multimediawidgets5, 
> libqt5opengl5-dev, libqt5svg5-dev, libqt5xmlpatterns5-dev, libqtwebkit-dev, 
> pyqt5-dev, pyqt5-dev-tools, python-dev, python3-pyside.qtuitools, qt5-qmake, 
> qtbase5-private-dev, qtdeclarative5-dev, qtmultimedia5-dev, qttools5-dev
> dpkg-deb: building package 'sbuild-build-depends-pythonqt-dummy' in 
> '/<>/resolver-uMroFt/apt_archive/sbuild-build-depends-pythonqt-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-pythonqt-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-uMroFt/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-uMroFt/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-uMroFt/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-uMroFt/apt_archive ./ Sources [629 B]
> Get:5 copy:/<>/resolver-uMroFt/apt_archive ./ Packages [713 B]
> Fetched 2305 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install pythonqt build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> 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:
>  sbuild-build-depends-pythonqt-dummy : Depends: libpythonqt-dev but it is not 
> going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2017/10/30/pythonqt_3.2-3_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#880232: nose: FTBFS: Test failures

[Lucas Nussbaum]

Source: nose
Version: 1.3.7-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20171030 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> --
> Traceback (most recent call last):
> ...
> ModuleNotFoundError: No module named 'apackagethatdoesntexist'
> 
> --
> Ran 1 test in ...s
> 
> FAILED (errors=1)
> 
> 
> --
> Ran 387 tests in 13.605s
> 
> FAILED (SKIP=18, failures=2)
> debian/rules:25: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2017/10/30/nose_1.3.7-2_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#870935: requesting removal of packages that missed both jessie and stretch

[Lucas Nussbaum]

reassign 870941 ftp.debian.org
retitle 870941 RM: flickrfs -- RoQA; missed both jessie and stretch
reassign 870991 ftp.debian.org
retitle 870991 RM: mnemonicode -- RoQA; missed both jessie and stretch
reassign 870977 ftp.debian.org
retitle 870977 RM: xburst-tools -- RoQA; missed both jessie and stretch
reassign 870947 ftp.debian.org
retitle 870947 RM: libsearch-estraier-perl -- RoQA; missed both jessie and 
stretch
reassign 870963 ftp.debian.org
retitle 870963 RM: jarisplayer -- RoQA; missed both jessie and stretch
reassign 871002 ftp.debian.org
retitle 871002 RM: cipux-cat-web -- RoQA; missed both jessie and stretch
reassign 870989 ftp.debian.org
retitle 870989 RM: interchange -- RoQA; missed both jessie and stretch
reassign 870932 ftp.debian.org
retitle 870932 RM: ocamlduce -- RoQA; missed both jessie and stretch
reassign 870995 ftp.debian.org
retitle 870995 RM: couchdb -- RoQA; missed both jessie and stretch
reassign 870971 ftp.debian.org
retitle 870971 RM: qpid-tools -- RoQA; missed both jessie and stretch
reassign 870919 ftp.debian.org
retitle 870919 RM: node-zlib -- RoQA; missed both jessie and stretch
reassign 870928 ftp.debian.org
retitle 870928 RM: openclipart2 -- RoQA; missed both jessie and stretch
reassign 870952 ftp.debian.org
retitle 870952 RM: qpid-cpp -- RoQA; missed both jessie and stretch
reassign 870988 ftp.debian.org
retitle 870988 RM: moodle-debian-edu-theme -- RoQA; missed both jessie and 
stretch
reassign 870994 ftp.debian.org
retitle 870994 RM: gregorio -- RoQA; missed both jessie and stretch
reassign 870937 ftp.debian.org
retitle 870937 RM: cutter-testing-framework -- RoQA; missed both jessie and 
stretch
reassign 870942 ftp.debian.org
retitle 870942 RM: diet -- RoQA; missed both jessie and stretch
reassign 870923 ftp.debian.org
retitle 870923 RM: babel -- RoQA; missed both jessie and stretch
reassign 870982 ftp.debian.org
retitle 870982 RM: djbdns -- RoQA; missed both jessie and stretch
reassign 871005 ftp.debian.org
retitle 871005 RM: rinputd -- RoQA; missed both jessie and stretch
reassign 871006 ftp.debian.org
retitle 871006 RM: z88dk -- RoQA; missed both jessie and stretch
reassign 870955 ftp.debian.org
retitle 870955 RM: openbve -- RoQA; missed both jessie and stretch
reassign 870998 ftp.debian.org
retitle 870998 RM: android-permissions -- RoQA; missed both jessie and stretch
reassign 870918 ftp.debian.org
retitle 870918 RM: openmeeg -- RoQA; missed both jessie and stretch
reassign 870933 ftp.debian.org
retitle 870933 RM: twitter-recess -- RoQA; missed both jessie and stretch
reassign 870976 ftp.debian.org
retitle 870976 RM: varnish-agent -- RoQA; missed both jessie and stretch
reassign 870962 ftp.debian.org
retitle 870962 RM: uif2iso -- RoQA; missed both jessie and stretch
reassign 870970 ftp.debian.org
retitle 870970 RM: gnu-fdisk -- RoQA; missed both jessie and stretch
reassign 871004 ftp.debian.org
retitle 871004 RM: hyde -- RoQA; missed both jessie and stretch
reassign 870940 ftp.debian.org
retitle 870940 RM: controlaula -- RoQA; missed both jessie and stretch
reassign 870992 ftp.debian.org
retitle 870992 RM: bashdb -- RoQA; missed both jessie and stretch
reassign 870980 ftp.debian.org
retitle 870980 RM: django-ldapdb -- RoQA; missed both jessie and stretch
reassign 870986 ftp.debian.org
retitle 870986 RM: python-lua -- RoQA; missed both jessie and stretch
reassign 870960 ftp.debian.org
retitle 870960 RM: django-conneg -- RoQA; missed both jessie and stretch
reassign 870958 ftp.debian.org
retitle 870958 RM: python-django-feincms -- RoQA; missed both jessie and stretch
reassign 871001 ftp.debian.org
retitle 871001 RM: node-jquery -- RoQA; missed both jessie and stretch
reassign 870920 ftp.debian.org
retitle 870920 RM: drgeo -- RoQA; missed both jessie and stretch
reassign 870935 ftp.debian.org
retitle 870935 RM: pyfltk -- RoQA; missed both jessie and stretch
reassign 870938 ftp.debian.org
retitle 870938 RM: tmview -- RoQA; missed both jessie and stretch
reassign 870999 ftp.debian.org
retitle 870999 RM: planner-el -- RoQA; missed both jessie and stretch
reassign 870939 ftp.debian.org
retitle 870939 RM: tile -- RoQA; missed both jessie and stretch
reassign 870931 ftp.debian.org
retitle 870931 RM: udev-discover -- RoQA; missed both jessie and stretch
reassign 870966 ftp.debian.org
retitle 870966 RM: janest-core -- RoQA; missed both jessie and stretch
reassign 870969 ftp.debian.org
retitle 870969 RM: sbackup -- RoQA; missed both jessie and stretch
reassign 871000 ftp.debian.org
retitle 871000 RM: node-bones -- RoQA; missed both jessie and stretch
reassign 870973 ftp.debian.org
retitle 870973 RM: xgraph -- RoQA; missed both jessie and stretch
reassign 870984 ftp.debian.org
retitle 870984 RM: imview-doc -- RoQA; missed both jessie and stretch
reassign 870997 ftp.debian.org
retitle 870997 RM: libtext-vimcolor-perl -- RoQA; missed both jessie and stretch
reassign 870922 ftp.debian.org
retitle 870922 RM: elmerfem -- RoQA; missed both jessie and stretch
reassign 870924 ftp.debian.o

[Python-modules-team] Bug#871385: python-scrapy-djangoitem: FTBFS: build-dependency not installable: python3-scrapy

[Lucas Nussbaum]

Source: python-scrapy-djangoitem
Version: 1.1.1-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), dh-python, python-all, python-django, 
> python-scrapy, python-setuptools, python-six, python3-all, python3-django, 
> python3-scrapy, python3-setuptools, python3-six
> Filtered Build-Depends: debhelper (>= 9), dh-python, python-all, 
> python-django, python-scrapy, python-setuptools, python-six, python3-all, 
> python3-django, python3-scrapy, python3-setuptools, python3-six
> dpkg-deb: building package 
> 'sbuild-build-depends-python-scrapy-djangoitem-dummy' in 
> '/<>/resolver-NzGLi2/apt_archive/sbuild-build-depends-python-scrapy-djangoitem-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-python-scrapy-djangoitem-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-NzGLi2/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-NzGLi2/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-NzGLi2/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-NzGLi2/apt_archive ./ Sources [548 B]
> Get:5 copy:/<>/resolver-NzGLi2/apt_archive ./ Packages [630 B]
> Fetched 2141 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install python-scrapy-djangoitem build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> 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:
>  sbuild-build-depends-python-scrapy-djangoitem-dummy : Depends: 
> python3-scrapy but it is not installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   
http://aws-logs.debian.net/2017/08/07/python-scrapy-djangoitem_1.1.1-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#871339: ipywidgets: FTBFS: dh_sphinxdoc: debian/python-ipywidgets-doc/usr/share/doc/python-ipywidgets-doc/html/_static/bootstrap-3/js/bootstrap.min.js is missing

[Lucas Nussbaum]

Source: ipywidgets
Version: 5.2.2-3
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_sphinxdoc -X_static/mathjax
> dh_sphinxdoc: 
> debian/python-ipywidgets-doc/usr/share/doc/python-ipywidgets-doc/html/_static/bootstrap-3/js/bootstrap.min.js
>  is missing
> debian/rules:73: recipe for target 'override_dh_sphinxdoc' failed
> make[1]: *** [override_dh_sphinxdoc] Error 2

The full build log is available from:
   http://aws-logs.debian.net/2017/08/07/ipywidgets_5.2.2-3_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#871204: sqlobject: FTBFS: dh_auto_test: pybuild --test -i python{version} -p "3.6 3.5" returned exit code 13

[Lucas Nussbaum]

Source: sqlobject
Version: 3.1.0+dfsg-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>  debian/rules build
> dh build --with python2,python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:184: python2.7 setup.py config 
> running config
> I: pybuild base:184: python3.6 setup.py config 
> running config
> I: pybuild base:184: python3.5 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:184: /usr/bin/python setup.py build 
> running build
> running build_py
> creating 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject
> copying sqlobject/events.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject
> copying sqlobject/joins.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject
> copying sqlobject/styles.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject
> copying sqlobject/cache.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject
> copying sqlobject/conftest.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject
> copying sqlobject/converters.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject
> copying sqlobject/wsgi_middleware.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject
> copying sqlobject/classregistry.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject
> copying sqlobject/compat.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject
> copying sqlobject/views.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject
> copying sqlobject/__init__.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject
> copying sqlobject/main.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject
> copying sqlobject/sqlbuilder.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject
> copying sqlobject/col.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject
> copying sqlobject/boundattributes.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject
> copying sqlobject/dbconnection.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject
> copying sqlobject/__version__.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject
> copying sqlobject/declarative.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject
> copying sqlobject/dberrors.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject
> copying sqlobject/sresults.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject
> copying sqlobject/constraints.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject
> copying sqlobject/index.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject
> creating 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject/firebird
> copying sqlobject/firebird/firebirdconnection.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject/firebird
> copying sqlobject/firebird/__init__.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject/firebird
> creating 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject/include
> copying sqlobject/include/hashcol.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject/include
> copying sqlobject/include/__init__.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject/include
> creating 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject/include/tests
> copying sqlobject/include/tests/__init__.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject/include/tests
> copying sqlobject/include/tests/test_hashcol.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject/include/tests
> creating 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject/inheritance
> copying sqlobject/inheritance/__init__.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject/inheritance
> copying sqlobject/inheritance/iteration.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject/inheritance
> creating 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject/inheritance/tests
> copying sqlobject/inheritance/tests/test_aggregates.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject/inheritance/tests
> copying sqlobject/inheritance/tests/test_indexes.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject/inheritance/tests
> copying sqlobject/inheritance/tests/test_foreignKey.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobje

[Python-modules-team] Bug#871199: pysodium: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13

[Lucas Nussbaum]

Source: pysodium
Version: 0.6.11-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>  debian/rules build
> dh build --with python2,python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:184: python2.7 setup.py config 
> running config
> I: pybuild base:184: python3.6 setup.py config 
> running config
> I: pybuild base:184: python3.5 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:184: /usr/bin/python setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_2.7/build/test
> copying test/__init__.py -> /<>/.pybuild/pythonX.Y_2.7/build/test
> copying test/test_pysodium.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/test
> creating /<>/.pybuild/pythonX.Y_2.7/build/pysodium
> copying pysodium/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pysodium
> I: pybuild base:184: /usr/bin/python3.6 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_3.6/build/test
> copying test/__init__.py -> /<>/.pybuild/pythonX.Y_3.6/build/test
> copying test/test_pysodium.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/test
> creating /<>/.pybuild/pythonX.Y_3.6/build/pysodium
> copying pysodium/__init__.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/pysodium
> I: pybuild base:184: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_3.5/build/test
> copying test/__init__.py -> /<>/.pybuild/pythonX.Y_3.5/build/test
> copying test/test_pysodium.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/test
> creating /<>/.pybuild/pythonX.Y_3.5/build/pysodium
> copying pysodium/__init__.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/pysodium
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:184: cd /<>/.pybuild/pythonX.Y_2.7/build; 
> python2.7 -m unittest discover -v 
> test_AsymCrypto_With_Seeded_Keypair (test.test_pysodium.TestPySodium) ... ok
> test_aead_chacha20poly1305 (test.test_pysodium.TestPySodium) ... ok
> test_aead_chacha20poly1305_detached (test.test_pysodium.TestPySodium) ... ok
> test_aead_chacha20poly1305_ietf (test.test_pysodium.TestPySodium) ... ok
> test_crypto_auth (test.test_pysodium.TestPySodium) ... ok
> test_crypto_blake2b (test.test_pysodium.TestPySodium) ... ok
> test_crypto_box_open (test.test_pysodium.TestPySodium) ... ok
> test_crypto_box_open_afternm (test.test_pysodium.TestPySodium) ... ok
> test_crypto_box_open_detached (test.test_pysodium.TestPySodium) ... ok
> test_crypto_box_pk_from_sk (test.test_pysodium.TestPySodium) ... ok
> test_crypto_box_seal (test.test_pysodium.TestPySodium) ... ok
> test_crypto_generichash (test.test_pysodium.TestPySodium) ... *** Error in 
> `python2.7': double free or corruption (!prev): 0x561176470750 ***
> === Backtrace: =
> /lib/x86_64-linux-gnu/libc.so.6(+0x70bfb)[0x7f688c0c1bfb]
> /lib/x86_64-linux-gnu/libc.so.6(+0x76fc6)[0x7f688c0c7fc6]
> /lib/x86_64-linux-gnu/libc.so.6(+0x7780e)[0x7f688c0c880e]
> /usr/lib/python2.7/lib-dynload/_ctypes.x86_64-linux-gnu.so(+0x11a03)[0x7f688bb7ea03]
> python2.7(+0x138243)[0x5611757bc243]
> python2.7(PyEval_EvalFrameEx+0x60c1)[0x561175789671]
> python2.7(PyEval_EvalFrameEx+0x5e5f)[0x56117578940f]
> python2.7(PyEval_EvalCodeEx+0x255)[0x561175781da5]
> python2.7(+0x11a5c8)[0x56117579e5c8]
> python2.7(PyObject_Call+0x43)[0x561175770163]
> python2.7(PyEval_EvalFrameEx+0x2eeb)[0x56117578649b]
> python2.7(PyEval_EvalCodeEx+0x255)[0x561175781da5]
> python2.7(+0x11a40e)[0x56117579e40e]
> python2.7(PyObject_Call+0x43)[0x561175770163]
> python2.7(+0x12fd7e)[0x5611757b3d7e]
> python2.7(PyObject_Call+0x43)[0x561175770163]
> python2.7(+0x19071b)[0x56117581471b]
> python2.7(PyObject_Call+0x43)[0x561175770163]
> python2.7(PyEval_EvalFrameEx+0x6072)[0x561175789622]
> python2.7(PyEval_EvalCodeEx+0x255)[0x561175781da5]
> python2.7(+0x11a5c8)[0x56117579e5c8]
> python2.7(PyObject_Call+0x43)[0x561175770163]
> python2.7(PyEval_EvalFrameEx+0x2eeb)[0x56117578649b]
> python2.7(PyEval_EvalCodeEx+0x255)[0x561175781da5]
> python2.7(+0x11a40e)[0x56117579e40e]
> python2.7(PyObject_Call+0x43)[0x561175770163]
> python2.7(+0x12fd7e)[0x5611757b3d7e]
> python2.7(PyObject_Call+0x43)[0x561175770163]
> python2.7(+0x19071b)[0x56117581471b]
> python2.7(PyObject_Call+0x43)[0x561175770163]
> python2.7(PyEval_EvalFrameEx+0x6072)[0x561175789622]
> python2.7(PyEval_EvalCodeEx+0x255)[0x561175781da5]
> python2.7(+0x11a5c8)[0x56117579e5c8]
> python2.7(PyObject_Call+0x43)[0x561175770163]
> python2.7(PyEval_EvalFrameEx+0x2eeb)[0x56117578649b]
> python2.7(PyEval_EvalCodeEx+0x255)[0x561175781da5]
> python2.7(+0x11a40e)[0x56117579e40e]
> python2.7(PyObject_Call+0x43)[0x561175770163]
> python2.7(+0x12fd7e)[0x5611757b3d7e]
> python2.7(PyObject_Call+0x43)[

[Python-modules-team] Bug#871156: pyfits: FTBFS: cc1: error: -Wformat-security ignored without -Wformat [-Werror=format-security]

[Lucas Nussbaum]

Source: pyfits
Version: 1:3.4-4
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall 
> -Wstrict-prototypes -fno-strict-aliasing -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
> -I/usr/lib/python2.7/dist-packages/numpy/core/include 
> -I/usr/include/python2.7 -c src/compressionmodule.c -o 
> build/temp.linux-amd64-2.7/src/compressionmodule.o 
> -Wno-declaration-after-statement -Wno-unused-variable -Wno-parentheses 
> -Wno-uninitialized -Wno-format -Wno-strict-prototypes -Wno-unused 
> -Wno-comments -Wno-switch
> cc1: error: -Wformat-security ignored without -Wformat 
> [-Werror=format-security]
> In file included from 
> /usr/lib/python2.7/dist-packages/numpy/core/include/numpy/ndarraytypes.h:1788:0,
>  from 
> /usr/lib/python2.7/dist-packages/numpy/core/include/numpy/ndarrayobject.h:18,
>  from 
> /usr/lib/python2.7/dist-packages/numpy/core/include/numpy/arrayobject.h:4,
>  from src/compressionmodule.c:97:
> /usr/lib/python2.7/dist-packages/numpy/core/include/numpy/npy_1_7_deprecated_api.h:15:2:
>  warning: #warning "Using deprecated NumPy API, disable it by " "#defining 
> NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION" [-Wcpp]
>  #warning "Using deprecated NumPy API, disable it by " \
>   ^~~
> src/compressionmodule.c: In function 'get_header_string':
> src/compressionmodule.c:255:14: warning: assignment makes integer from 
> pointer without a cast [-Wint-conversion]
>  *val = def;
>   ^
> cc1: some warnings being treated as errors
> building optional extension "pyfits.compression" failed: command 
> 'x86_64-linux-gnu-gcc' failed with exit status 1
> 
> 
> Failed to build PyFITS tile compression support.  PyFITS will still
> function, but without the ability to read or write compressed images.
> Please seek support from h...@stsci.edu if you need this capability.
> !
> running build_scripts
> creating build/scripts-2.7
> copying and adjusting scripts/fitscheck -> build/scripts-2.7
> copying and adjusting scripts/fitsdiff -> build/scripts-2.7
> copying and adjusting scripts/fitshead -> build/scripts-2.7
> changing mode of build/scripts-2.7/fitscheck from 664 to 775
> changing mode of build/scripts-2.7/fitsdiff from 664 to 775
> changing mode of build/scripts-2.7/fitshead from 664 to 775
> I: pybuild base:184: /usr/bin/python3.6 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_3.6/build/pyfits
> copying pyfits/file.py -> /<>/.pybuild/pythonX.Y_3.6/build/pyfits
> copying pyfits/card.py -> /<>/.pybuild/pythonX.Y_3.6/build/pyfits
> copying pyfits/verify.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/pyfits
> copying pyfits/_numpy_hacks.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/pyfits
> copying pyfits/py3compat.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/pyfits
> copying pyfits/header.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/pyfits
> copying pyfits/core.py -> /<>/.pybuild/pythonX.Y_3.6/build/pyfits
> copying pyfits/_release.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/pyfits
> copying pyfits/__init__.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/pyfits
> copying pyfits/column.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/pyfits
> copying pyfits/util.py -> /<>/.pybuild/pythonX.Y_3.6/build/pyfits
> copying pyfits/convenience.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/pyfits
> copying pyfits/version.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/pyfits
> copying pyfits/diff.py -> /<>/.pybuild/pythonX.Y_3.6/build/pyfits
> copying pyfits/fitsrec.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/pyfits
> creating /<>/.pybuild/pythonX.Y_3.6/build/pyfits/_compat
> copying pyfits/_compat/__init__.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/pyfits/_compat
> copying pyfits/_compat/weakref.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/pyfits/_compat
> copying pyfits/_compat/odict.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/pyfits/_compat
> creating /<>/.pybuild/pythonX.Y_3.6/build/pyfits/extern
> copying pyfits/extern/six.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/pyfits/extern
> copying pyfits/extern/__init__.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/pyfits/extern
> creating /<>/.pybuild/pythonX.Y_3.6/build/pyfits/hdu
> copying pyfits/hdu/table.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/pyfits/hdu
> copying pyfits/hdu/image.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/pyfits/hdu
> copying pyfits/hdu/__init__.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/pyfits/hdu
> copying pyfits/hdu/compressed.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/pyfits/hdu
> copying pyfits/hdu/hdulist.py -> 
> /<>/.pyb

[Python-modules-team] Bug#871127: pytest-mock: FTBFS: Test failures

[Lucas Nussbaum]

Source: pytest-mock
Version: 1.3.0-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> collected 1 item
> 
> test_mock_fixture_is_deprecated.py .
> 
> === warnings summary 
> ===
> test_mock_fixture_is_deprecated.py::test_foo
>   /<>/pytest_mock.py:152: DeprecationWarning: "mock" fixture has 
> been deprecated, use "mocker" instead
> DeprecationWarning)
> 
> -- Docs: http://doc.pytest.org/en/latest/warnings.html
> = 1 passed, 1 warnings in 0.01 seconds 
> =
>  Interrupted: stopping after 1 failures 
> 
> == 1 failed, 4 passed in 0.22 seconds 
> ==
> E: pybuild pybuild:283: test: plugin custom failed with: exit code=2: 
> python2.7 -m pytest -v -x
> dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned 
> exit code 13
> debian/rules:9: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2017/08/05/pytest-mock_1.3.0-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#871064: pyqt5: FTBFS: build-dependency not installable: qtwebengine5-dev (>= 5.7.1+dfsg-3~)

[Lucas Nussbaum]

Source: pyqt5
Version: 5.7+dfsg-5
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), dh-python, dpkg-dev (>= 1.16.1~), 
> libdbus-1-dev (>= 1.0.2), libglib2.0-dev, libicu-dev, libpulse-dev, 
> libqt5opengl5-dev (>= 5.7.0), libqt5sensors5-dev (>= 5.7.0), 
> libqt5serialport5-dev (>= 5.7.0), libqt5svg5-dev (>= 5.7.0), 
> libqt5webchannel5-dev (>= 5.7.1), libqt5webkit5-dev (>= 5.7.0), 
> libqt5websockets5-dev (>= 5.7.0), libqt5x11extras5-dev (>= 5.7.0), 
> libqt5xmlpatterns5-dev (>= 5.7.0), libsqlite3-dev, libudev-dev, libxml2-dev, 
> libxslt1-dev, python-all-dbg, python-all-dev (>= 2.6.6-3~), python-dbus, 
> python-dbus-dbg, python-dbus-dev, python-sip-dbg, python-sip-dev (>= 4.18), 
> python3-all-dbg, python3-all-dev (>= 3.3.2-5~), python3-dbus, 
> python3-dbus-dbg, python3-sip-dbg, python3-sip-dev (>= 4.18), 
> qtdeclarative5-dev (>= 5.7.0), qtlocation5-dev (>= 5.7.0), qtmultimedia5-dev 
> (>= 5.7.0), qtpositioning5-dev (>= 5.7.0), qttools5-dev (>= 5.7.0), 
> qtwebengine5-dev (>= 5.7.1+dfsg-3~), fdupes, python3-sphinx (>= 1.3)
> Filtered Build-Depends: debhelper (>= 9), dh-python, dpkg-dev (>= 1.16.1~), 
> libdbus-1-dev (>= 1.0.2), libglib2.0-dev, libicu-dev, libpulse-dev, 
> libqt5opengl5-dev (>= 5.7.0), libqt5sensors5-dev (>= 5.7.0), 
> libqt5serialport5-dev (>= 5.7.0), libqt5svg5-dev (>= 5.7.0), 
> libqt5webchannel5-dev (>= 5.7.1), libqt5webkit5-dev (>= 5.7.0), 
> libqt5websockets5-dev (>= 5.7.0), libqt5x11extras5-dev (>= 5.7.0), 
> libqt5xmlpatterns5-dev (>= 5.7.0), libsqlite3-dev, libudev-dev, libxml2-dev, 
> libxslt1-dev, python-all-dbg, python-all-dev (>= 2.6.6-3~), python-dbus, 
> python-dbus-dbg, python-dbus-dev, python-sip-dbg, python-sip-dev (>= 4.18), 
> python3-all-dbg, python3-all-dev (>= 3.3.2-5~), python3-dbus, 
> python3-dbus-dbg, python3-sip-dbg, python3-sip-dev (>= 4.18), 
> qtdeclarative5-dev (>= 5.7.0), qtlocation5-dev (>= 5.7.0), qtmultimedia5-dev 
> (>= 5.7.0), qtpositioning5-dev (>= 5.7.0), qttools5-dev (>= 5.7.0), 
> qtwebengine5-dev (>= 5.7.1+dfsg-3~), fdupes, python3-sphinx (>= 1.3)
> dpkg-deb: building package 'sbuild-build-depends-pyqt5-dummy' in 
> '/<>/resolver-01Uh6s/apt_archive/sbuild-build-depends-pyqt5-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-pyqt5-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-01Uh6s/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-01Uh6s/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-01Uh6s/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-01Uh6s/apt_archive ./ Sources [815 B]
> Get:5 copy:/<>/resolver-01Uh6s/apt_archive ./ Packages [866 B]
> Fetched 2644 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install pyqt5 build dependencies (apt-based resolver)
> -
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> 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:
>  sbuild-build-depends-pyqt5-dummy : Depends: qtwebengine5-dev (>= 
> 5.7.1+dfsg-3~) but it is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2017/08/05/pyqt5_5.7+dfsg-5_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#870983: pisa: should pisa be removed from unstable?

[Lucas Nussbaum]

Source: pisa
User: debian...@lists.debian.org
Usertags: qa-removals-post-stretch

Hi,

Following a discussion[1] on the debian-qa@ mailing list on packages that
missed both jessie and stretch, I am proposing the removal of this package from
unstable, because:

  it was in unstable at the time of the stretch freeze
but wasn't part of stretch
AND
  it was in unstable at the time of the jessie freeze
but it wasn't part of jessie
AND
  it is still not in testing
AND
  it was not uploaded since the beginning of 2017.

If you disagree and think that this package should remain in unstable, feel
free to just close this bug.

If this bug is still open one month from now (on 2017-09-06), it will be turned
into a removal request, using:

  reassign -1 ftp.debian.org
  retitle -1 RM: pisa -- RoQA; missed both jessie and stretch
  thanks

- Lucas, for the QA team.


[1] https://lists.debian.org/debian-qa/2017/07/msg00021.html

___
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#870935: pyfltk: should pyfltk be removed from unstable?

[Lucas Nussbaum]

Source: pyfltk
User: debian...@lists.debian.org
Usertags: qa-removals-post-stretch

Hi,

Following a discussion[1] on the debian-qa@ mailing list on packages that
missed both jessie and stretch, I am proposing the removal of this package from
unstable, because:

  it was in unstable at the time of the stretch freeze
but wasn't part of stretch
AND
  it was in unstable at the time of the jessie freeze
but it wasn't part of jessie
AND
  it is still not in testing
AND
  it was not uploaded since the beginning of 2017.

If you disagree and think that this package should remain in unstable, feel
free to just close this bug.

If this bug is still open one month from now (on 2017-09-06), it will be turned
into a removal request, using:

  reassign -1 ftp.debian.org
  retitle -1 RM: pyfltk -- RoQA; missed both jessie and stretch
  thanks

- Lucas, for the QA team.


[1] https://lists.debian.org/debian-qa/2017/07/msg00021.html

___
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#869016: pyqt5: FTBFS: build-dependency not installable: qtwebengine5-dev (>= 5.7.1+dfsg-3~)

[Lucas Nussbaum]

Source: pyqt5
Version: 5.7+dfsg-5
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), dh-python, dpkg-dev (>= 1.16.1~), 
> libdbus-1-dev (>= 1.0.2), libglib2.0-dev, libicu-dev, libpulse-dev, 
> libqt5opengl5-dev (>= 5.7.0), libqt5sensors5-dev (>= 5.7.0), 
> libqt5serialport5-dev (>= 5.7.0), libqt5svg5-dev (>= 5.7.0), 
> libqt5webchannel5-dev (>= 5.7.1), libqt5webkit5-dev (>= 5.7.0), 
> libqt5websockets5-dev (>= 5.7.0), libqt5x11extras5-dev (>= 5.7.0), 
> libqt5xmlpatterns5-dev (>= 5.7.0), libsqlite3-dev, libudev-dev, libxml2-dev, 
> libxslt1-dev, python-all-dbg, python-all-dev (>= 2.6.6-3~), python-dbus, 
> python-dbus-dbg, python-dbus-dev, python-sip-dbg, python-sip-dev (>= 4.18), 
> python3-all-dbg, python3-all-dev (>= 3.3.2-5~), python3-dbus, 
> python3-dbus-dbg, python3-sip-dbg, python3-sip-dev (>= 4.18), 
> qtdeclarative5-dev (>= 5.7.0), qtlocation5-dev (>= 5.7.0), qtmultimedia5-dev 
> (>= 5.7.0), qtpositioning5-dev (>= 5.7.0), qttools5-dev (>= 5.7.0), 
> qtwebengine5-dev (>= 5.7.1+dfsg-3~), fdupes, python3-sphinx (>= 1.3)
> Filtered Build-Depends: debhelper (>= 9), dh-python, dpkg-dev (>= 1.16.1~), 
> libdbus-1-dev (>= 1.0.2), libglib2.0-dev, libicu-dev, libpulse-dev, 
> libqt5opengl5-dev (>= 5.7.0), libqt5sensors5-dev (>= 5.7.0), 
> libqt5serialport5-dev (>= 5.7.0), libqt5svg5-dev (>= 5.7.0), 
> libqt5webchannel5-dev (>= 5.7.1), libqt5webkit5-dev (>= 5.7.0), 
> libqt5websockets5-dev (>= 5.7.0), libqt5x11extras5-dev (>= 5.7.0), 
> libqt5xmlpatterns5-dev (>= 5.7.0), libsqlite3-dev, libudev-dev, libxml2-dev, 
> libxslt1-dev, python-all-dbg, python-all-dev (>= 2.6.6-3~), python-dbus, 
> python-dbus-dbg, python-dbus-dev, python-sip-dbg, python-sip-dev (>= 4.18), 
> python3-all-dbg, python3-all-dev (>= 3.3.2-5~), python3-dbus, 
> python3-dbus-dbg, python3-sip-dbg, python3-sip-dev (>= 4.18), 
> qtdeclarative5-dev (>= 5.7.0), qtlocation5-dev (>= 5.7.0), qtmultimedia5-dev 
> (>= 5.7.0), qtpositioning5-dev (>= 5.7.0), qttools5-dev (>= 5.7.0), 
> qtwebengine5-dev (>= 5.7.1+dfsg-3~), fdupes, python3-sphinx (>= 1.3)
> dpkg-deb: building package 'sbuild-build-depends-pyqt5-dummy' in 
> '/<>/resolver-Yj9i1S/apt_archive/sbuild-build-depends-pyqt5-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-pyqt5-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-Yj9i1S/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-Yj9i1S/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-Yj9i1S/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-Yj9i1S/apt_archive ./ Sources [815 B]
> Get:5 copy:/<>/resolver-Yj9i1S/apt_archive ./ Packages [864 B]
> Fetched 2642 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install pyqt5 build dependencies (apt-based resolver)
> -
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> 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:
>  sbuild-build-depends-pyqt5-dummy : Depends: qtwebengine5-dev (>= 
> 5.7.1+dfsg-3~) but it is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2017/07/19/pyqt5_5.7+dfsg-5_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#868971: python-feather-format: FTBFS: feather/ext.cpp:28:20: fatal error: Python.h: No such file or directory

[Lucas Nussbaum]

Source: python-feather-format
Version: 0.3.1+dfsg1-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall 
> -Wstrict-prototypes -g -O2 
> -fdebug-prefix-map=/<>/python-feather-format-0.3.1+dfsg1=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -fPIC -Ifeather 
> -I/usr/lib/python3/dist-packages/numpy/core/include 
> -I/<>/python-feather-format-0.3.1+dfsg1/src 
> -I/usr/include/python3.6m -c feather/ext.cpp -o 
> build/temp.linux-amd64-3.6/feather/ext.o -std=c++11 -O3
> cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for 
> C/ObjC but not for C++
> feather/ext.cpp:28:20: fatal error: Python.h: No such file or directory
>  #include "Python.h"
> ^
> compilation terminated.
> error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
> E: pybuild pybuild:283: build: plugin distutils failed with: exit code=1: 
> /usr/bin/python3.6 setup.py build 
> dh_auto_build: pybuild --build -i python{version} -p 3.6 3.5 returned exit 
> code 13
> debian/rules:8: recipe for target 'build' failed
> make: *** [build] Error 25

The full build log is available from:
   
http://aws-logs.debian.net/2017/07/19/python-feather-format_0.3.1+dfsg1-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#860673: Bug#860673: python-django: FTBFS on i386: E: Build killed with signal TERM after 150 minutes of inactivity

[Lucas Nussbaum]

On 20/04/17 at 06:54 +1000, Brian May wrote:
> Chris Lamb  writes:
> 
> > Lucas Nussbaum wrote:
> >
> >> > test_output_verbose (test_runner.test_debug_sql.TestDebugSQL) ... ok
> >> > E: Build killed with signal TERM after 150 minutes of inactivity
> >
> > Can't reproduce this locally alas...
> 
> I couldn't reproduce this locally. I use a 32bit schroot.

I tried on a smaller EC2 instance (m4.4xlarge, with 16 cores instead of
64) and it did not fail.

Lucas

___
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#860663: Bug#860663: pytest: FTBFS on i386: segfault during tests

[Lucas Nussbaum]

On 19/04/17 at 22:15 +0200, Lucas Nussbaum wrote:
> On 19/04/17 at 20:42 +0200, Sebastian Ramacher wrote:
> > Control: tags -1 + moreinfo unreproducible
> > 
> > On 2017-04-19 09:26:48, Lucas Nussbaum wrote:
> > > Source: pytest
> > > Version: 3.0.6-1
> > > Severity: serious
> > > Tags: stretch sid
> > > User: debian...@lists.debian.org
> > > Usertags: qa-ftbfs-20170418-i386 qa-ftbfs
> > > Justification: FTBFS in stretch on i386
> > > 
> > > Hi,
> > > 
> > > During a rebuild of all packages in stretch (in a stretch chroot, not a
> > > sid chroot), your package failed to build on i386.
> > > 
> > > Relevant part (hopefully):
> > > > ../../../testing/test_pluginmanager.py ...
> > > > ../../../testing/test_pytester.py x...
> > > > ../../../testing/test_recwarn.py ..
> > > > ../../../testing/test_resultlog.py ...
> > > > ../../../testing/test_runner.py 
> > > > ...sss.....x...
> > > > ../../../testing/test_runner_xunit.py ...
> > > > ../../../testing/test_session.py .
> > > > ../../../testing/test_skipping.py 
> > > > ..x..
> > > > ../../../testing/test_terminal.py 
> > > > ..s..s.
> > > > ../../../testing/test_tmpdir.py ...s
> > > > ../../../testing/test_unittest.py 
> > > > 
> > > > ../../../testing/code/test_code.py ..
> > > > ../../../testing/code/test_excinfo.py Segmentation fault
> > > > E: pybuild pybuild:283: test: plugin custom failed with: exit code=139: 
> > > > cd debian/tmp/test-working-directory && pypy -m pytest --lsof -rfsxX 
> > > > --ignore=/<>/testing/freeze 
> > > > --ignore=/<>/testing/test_entry_points.py 
> > > > --ignore=/<>/testing/test_pdb.py /<>/testing
> > > > dh_auto_test: pybuild --test -i pypy -p 5.6 --system=custom 
> > > > --test-args=cd debian/tmp/test-working-directory && {interpreter} -m 
> > > > pytest --lsof -rfsxX --ignore={dir}/testing/freeze 
> > > > --ignore={dir}/testing/test_entry_points.py 
> > > > --ignore={dir}/testing/test_pdb.py {dir}/testing returned exit code 13
> > > > debian/rules:20: recipe for target 'override_dh_auto_test' failed
> > 
> > I'm unable to reproduce the crash. Could you please provide a backtrace?
> 
> Can you provide a build log and diff it with mine?

I dug a bit more, and can say that:
- it also fails on a smaller EC2 instance, so it's not related to the
  fact that the first instance was quite powerful, many cores, etc.
- it also fails on a completely up-to-date jessie host (still with a
  stretch/i386 chroot) -- my kernel wasn't entirely up-to-date

I've generated a core file and put it at:
http://aws-logs.debian.net/2017/04/18/pypy-segfault.core.gz

The backtrace looks like:
#0  0xf553ba24 in pypy_g_handle_bytecode__AccessDirect_None () from 
/usr/lib/pypy/bin/libpypy-c.so
#1  0xf5b3282f in pypy_g_portal_5 () from /usr/lib/pypy/bin/libpypy-c.so
#2  0xf5e68bb4 in pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () 
from /usr/lib/pypy/bin/libpypy-c.so
#3  0xf5b327d8 in pypy_g_PyFrame_dispatch () from /usr/lib/pypy/bin/libpypy-c.so
#4  0xf54e954e in pypy_g_execute_frame () from /usr/lib/pypy/bin/libpypy-c.so
#5  0xf636b801 in pypy_g_execute_frame_rvmprof.star_3 () from 
/usr/lib/pypy/bin/libpypy-c.so
#6  0xf54bc07c in pypy_g_PyFrame_run () from /usr/lib/pypy/bin/libpypy-c.so
#7  0xf5533573 in pypy_g_CALL_FUNCTION__AccessDirect_None () from 
/usr/lib/pypy/bin/libpypy-c.so
#8  0xf5537eba in pypy_g_dispatch_bytecode__AccessDirect_None () from 
/usr/lib/pypy/bin/libpypy-c.so
#9  0xf553ba29 in pypy_g_handle_bytecode__AccessDirect_None () from 
/usr/lib/pypy/bin/libpypy-c.so
#10 0xf5b3282f in pypy_g_portal_5 () from /usr/lib/pypy/bin/libpypy-c.so
#11 0xf5e68bb4 in pypy_g_ll_portal_runner__Unsigned_Bool_pypy_interpreter () 
from /usr/lib/pypy/bin/libpypy-c.so
#12 0xf5b327d8 in pypy_g_PyFrame_dispatch () from /usr/lib/pypy/bin/libpypy-c.so
#13 0xf54e954e in pypy_g_execute_frame () from /usr/lib/pypy/bin/libpypy-c.so
#14 0xf636b801 in pypy_g_execute_frame_rvmprof.star_3 () from 
/usr/lib/pypy/bin/libpypy-c.so
#15 0xf54bc07c in pypy_g_PyFrame_run () from /usr/lib/pypy/bin/libpypy-c.so
#16 0xf5533573 in pypy_g_CALL_FUNCTION__AccessDirect_None () from 
/usr/lib/pypy/bin/libpypy-c.so
#17 0xf5537eba in pypy_g_dispatch_bytecode__AccessDirect_None () from 
/usr/lib/pypy/bin/libpypy-c.so
#18 0xf553ba29 in pypy_g_handle_bytecode__AccessDirect_None () from 
/usr/lib/pypy/bin/libpypy-c.so

Lucas

___
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#860663: Bug#860663: pytest: FTBFS on i386: segfault during tests

[Lucas Nussbaum]

On 19/04/17 at 20:42 +0200, Sebastian Ramacher wrote:
> Control: tags -1 + moreinfo unreproducible
> 
> On 2017-04-19 09:26:48, Lucas Nussbaum wrote:
> > Source: pytest
> > Version: 3.0.6-1
> > Severity: serious
> > Tags: stretch sid
> > User: debian...@lists.debian.org
> > Usertags: qa-ftbfs-20170418-i386 qa-ftbfs
> > Justification: FTBFS in stretch on i386
> > 
> > Hi,
> > 
> > During a rebuild of all packages in stretch (in a stretch chroot, not a
> > sid chroot), your package failed to build on i386.
> > 
> > Relevant part (hopefully):
> > > ../../../testing/test_pluginmanager.py ...
> > > ../../../testing/test_pytester.py x...
> > > ../../../testing/test_recwarn.py ..
> > > ../../../testing/test_resultlog.py ...
> > > ../../../testing/test_runner.py 
> > > ...sss.....x...
> > > ../../../testing/test_runner_xunit.py ...
> > > ../../../testing/test_session.py .
> > > ../../../testing/test_skipping.py 
> > > ..x..
> > > ../../../testing/test_terminal.py 
> > > ..s..s.
> > > ../../../testing/test_tmpdir.py ...s
> > > ../../../testing/test_unittest.py 
> > > 
> > > ../../../testing/code/test_code.py ..
> > > ../../../testing/code/test_excinfo.py Segmentation fault
> > > E: pybuild pybuild:283: test: plugin custom failed with: exit code=139: 
> > > cd debian/tmp/test-working-directory && pypy -m pytest --lsof -rfsxX 
> > > --ignore=/<>/testing/freeze 
> > > --ignore=/<>/testing/test_entry_points.py 
> > > --ignore=/<>/testing/test_pdb.py /<>/testing
> > > dh_auto_test: pybuild --test -i pypy -p 5.6 --system=custom 
> > > --test-args=cd debian/tmp/test-working-directory && {interpreter} -m 
> > > pytest --lsof -rfsxX --ignore={dir}/testing/freeze 
> > > --ignore={dir}/testing/test_entry_points.py 
> > > --ignore={dir}/testing/test_pdb.py {dir}/testing returned exit code 13
> > > debian/rules:20: recipe for target 'override_dh_auto_test' failed
> 
> I'm unable to reproduce the crash. Could you please provide a backtrace?

Can you provide a build log and diff it with mine?

Lucas

___
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#860673: python-django: FTBFS on i386: E: Build killed with signal TERM after 150 minutes of inactivity

[Lucas Nussbaum]

On 19/04/17 at 16:18 +0100, Chris Lamb wrote:
> Lucas Nussbaum wrote:
> 
> > That's a build log for amd64, not i386.
> 
> D'oh!
> 
> > python2.7[39117]: segfault at ffc2cffc ip f61a8170 sp 
> > ffc2d000 error 6 in libsqlite3.so.0.8.6[f6135000+115000]
> 
> I don't have stretch/i386 within reach atm but this looks like it has
> narrowed it down. Any chance of getting a backtrace with symbols?

(Interestingly, when restricting the testsuite to the relevant module,
it doesn't segfault)

Here is the backtrace:

Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
Core was generated by `python2.7 ./runtests.py --verbosity=2 --parallel 1 
--failfast'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0xf61c70f0 in sqlite3Select (pParse=pParse@entry=0xff954300, 
p=p@entry=0xfee8ed60, pDest=pDest@entry=0xff91e124) at sqlite3.c:120376
120376  sqlite3.c: No such file or directory.

#0  0xf61c70f0 in sqlite3Select (pParse=pParse@entry=0xff954300, 
p=p@entry=0xfee8ed60, pDest=pDest@entry=0xff91e124) at sqlite3.c:120376
#1  0xf61d1f4a in multiSelect (pParse=pParse@entry=0xff954300, 
p=p@entry=0xfe9c0dc0, pDest=pDest@entry=0xff91e314) at sqlite3.c:117808
#2  0xf61c7731 in sqlite3Select (pParse=pParse@entry=0xff954300, 
p=p@entry=0xfe9c0dc0, pDest=pDest@entry=0xff91e314) at sqlite3.c:120465
#3  0xf61d1f4a in multiSelect (pParse=pParse@entry=0xff954300, 
p=p@entry=0xfea6d498, pDest=pDest@entry=0xff91e504) at sqlite3.c:117808
#4  0xf61c7731 in sqlite3Select (pParse=pParse@entry=0xff954300, 
p=p@entry=0xfea6d498, pDest=pDest@entry=0xff91e504) at sqlite3.c:120465
#5  0xf61d1f4a in multiSelect (pParse=pParse@entry=0xff954300, 
p=p@entry=0xfed837c8, pDest=pDest@entry=0xff91e6f4) at sqlite3.c:117808
#6  0xf61c7731 in sqlite3Select (pParse=pParse@entry=0xff954300, 
p=p@entry=0xfed837c8, pDest=pDest@entry=0xff91e6f4) at sqlite3.c:120465
#7  0xf61d1f4a in multiSelect (pParse=pParse@entry=0xff954300, 
p=p@entry=0xff10c728, pDest=pDest@entry=0xff91e8e4) at sqlite3.c:117808
#8  0xf61c7731 in sqlite3Select (pParse=pParse@entry=0xff954300, 
p=p@entry=0xff10c728, pDest=pDest@entry=0xff91e8e4) at sqlite3.c:120465
#9  0xf61d1f4a in multiSelect (pParse=pParse@entry=0xff954300, 
p=p@entry=0xfb40d7a8, pDest=pDest@entry=0xff91ead4) at sqlite3.c:117808
#10 0xf61c7731 in sqlite3Select (pParse=pParse@entry=0xff954300, 
p=p@entry=0xfb40d7a8, pDest=pDest@entry=0xff91ead4) at sqlite3.c:120465
#11 0xf61d1f4a in multiSelect (pParse=pParse@entry=0xff954300, 
p=p@entry=0xf9caeb60, pDest=pDest@entry=0xff91ecc4) at sqlite3.c:117808
#12 0xf61c7731 in sqlite3Select (pParse=pParse@entry=0xff954300, 
p=p@entry=0xf9caeb60, pDest=pDest@entry=0xff91ecc4) at sqlite3.c:120465
#13 0xf61d1f4a in multiSelect (pParse=pParse@entry=0xff954300, 
p=p@entry=0xff183400, pDest=pDest@entry=0xff91eeb4) at sqlite3.c:117808
#14 0xf61c7731 in sqlite3Select (pParse=pParse@entry=0xff954300, 
p=p@entry=0xff183400, pDest=pDest@entry=0xff91eeb4) at sqlite3.c:120465
#15 0xf61d1f4a in multiSelect (pParse=pParse@entry=0xff954300, 
p=p@entry=0xf9c57408, pDest=pDest@entry=0xff91f0a4) at sqlite3.c:117808
#16 0xf61c7731 in sqlite3Select (pParse=pParse@entry=0xff954300, 
p=p@entry=0xf9c57408, pDest=pDest@entry=0xff91f0a4) at sqlite3.c:120465
#17 0xf61d1f4a in multiSelect (pParse=pParse@entry=0xff954300, 
p=p@entry=0xf9ca9488, pDest=pDest@entry=0xff91f294) at sqlite3.c:117808
#18 0xf61c7731 in sqlite3Select (pParse=pParse@entry=0xff954300, 
p=p@entry=0xf9ca9488, pDest=pDest@entry=0xff91f294) at sqlite3.c:120465
#19 0xf61d1f4a in multiSelect (pParse=pParse@entry=0xff954300, 
p=p@entry=0xfbc66de0, pDest=pDest@entry=0xff91f484) at sqlite3.c:117808
#20 0xf61c7731 in sqlite3Select (pParse=pParse@entry=0xff954300, 
p=p@entry=0xfbc66de0, pDest=pDest@entry=0xff91f484) at sqlite3.c:120465
#21 0xf61d1f4a in multiSelect (pParse=pParse@entry=0xff954300, 
p=p@entry=0xff0763a8, pDest=pDest@entry=0xff91f674) at sqlite3.c:117808
#22 0xf61c7731 in sqlite3Select (pParse=pParse@entry=0xff954300, 
p=p@entry=0xff0763a8, pDest=pDest@entry=0xff91f674) at sqlite3.c:120465
#23 0xf61d1f4a in multiSelect (pParse=pParse@entry=0xff954300, 
p=p@entry=0xfead0a80, pDest=pDest@entry=0xff91f864) at sqlite3.c:117808
#24 0xf61c7731 in sqlite3Select (pParse=pParse@entry=0xff954300, 
p=p@entry=0xfead0a80, pDest=pDest@entry=0xff91f864) at sqlite3.c:120465
#25 0xf61d1f4a in multiSelect (pParse=pParse@entry=0xff954300, 
p=p@entry=0xff0878a0, pDest=pDest@entry=0xff91fa54) at sqlite3.c:117808
#26 0xf61c7731 in sqlite3Select (pParse=pParse@entry=0xff954300, 
p=p@entry=0xff0878a0, pDest=pDest@entry=0xff91fa54) at sqlite3.c:120465
#27 0xf61d1f4a in multiSelect (pParse=pParse@entry=0xff954300, 
p=p@entry=0xee765630, pDest=pDest@entry=0xff91fc44) at sqlite3.c:117808
#28 0xf61c7731 in sqlite3Select (pParse=pParse@entry=0xff954300, 
p=p@entry=0xee765630, pDest=pDest@entry=0xff91fc44) at sqlite3.c:120465
#29 0xf

[Python-modules-team] Bug#860673: python-django: FTBFS on i386: E: Build killed with signal TERM after 150 minutes of inactivity

[Lucas Nussbaum]

On 19/04/17 at 15:59 +0100, Chris Lamb wrote:
> Hi Lucas,
> 
> > I tried again and still can; maybe diff your build log with mine to see
> > if something comes up?
> 
> Good idea; mine is at:
> 
>   https://gist.github.com/lamby/e2152b47a6d3d69d29e34975059c6be7/raw

That's a build log for amd64, not i386.

> (Testsuite runs in parallel so this might be difficult...)

Indeed. However, the test suite also fails when run manually, with
python2.7 ./runtests.py --verbosity=2 --parallel 1 --failfast

I get:
test_can_defer_constraint_checks (delete.tests.DeletionTests) ... skipped 
"Database doesn't support feature(s): can_defer_constraint_checks"
test_cannot_defer_constraint_checks (delete.tests.DeletionTests) ... ok
test_delete_with_keeping_parents (delete.tests.DeletionTests) ... ok
test_delete_with_keeping_parents_relationships (delete.tests.DeletionTests) ... 
ok
test_deletion_order (delete.tests.DeletionTests) ... ok
test_hidden_related (delete.tests.DeletionTests) ... ok
test_instance_update (delete.tests.DeletionTests) ... ok
test_large_delete (delete.tests.DeletionTests) ... Segmentation fault

dmesg shows:
python2.7[39117]: segfault at ffc2cffc ip f61a8170 sp ffc2d000 
error 6 in libsqlite3.so.0.8.6[f6135000+115000]

Lucas

___
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#860673: python-django: FTBFS on i386: E: Build killed with signal TERM after 150 minutes of inactivity

[Lucas Nussbaum]

Hi!

On 19/04/17 at 14:02 +0100, Chris Lamb wrote:
> Lucas Nussbaum wrote:
> 
> > > test_output_verbose (test_runner.test_debug_sql.TestDebugSQL) ... ok
> > > E: Build killed with signal TERM after 150 minutes of inactivity
> 
> Can't reproduce this locally alas...

I tried again and still can; maybe diff your build log with mine to see
if something comes up?

Lucas

___
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#860668: sorl-thumbnail: FTBFS on i386: segfault during tests

[Lucas Nussbaum]

Source: sorl-thumbnail
Version: 12.3+git20160928-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170418-i386 qa-ftbfs
Justification: FTBFS in stretch on i386

Hi,

During a rebuild of all packages in stretch (in a stretch chroot, not a
sid chroot), your package failed to build on i386.

Relevant part (hopefully):
> tests/thumbnail_tests/test_filters.py 
> tests/thumbnail_tests/test_kvstore.py .
> tests/thumbnail_tests/test_parsers.py .
> tests/thumbnail_tests/test_storage.py 
> tests/thumbnail_tests/test_templatetags.py ss.
> 
> === 63 passed, 3 skipped, 2 xfailed in 5.14 seconds 
> 
> = test session starts 
> ==
> platform linux2 -- Python 2.7.13, pytest-3.0.6, py-1.4.32, pluggy-0.4.0
> django settings: tests.settings.wand (from environment variable)
> rootdir: /<>/sorl-thumbnail-12.3+git20160928, inifile: tox.ini
> plugins: django-2.9.1
> collected 68 items
> 
> tests/thumbnail_tests/test_alternative_resolutions.py Segmentation fault
> debian/rules:22: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   
http://aws-logs.debian.net/2017/04/18/sorl-thumbnail_12.3+git20160928-1_testing-i386.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#860673: python-django: FTBFS on i386: E: Build killed with signal TERM after 150 minutes of inactivity

[Lucas Nussbaum]

Source: python-django
Version: 1:1.10.7-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170418-i386 qa-ftbfs
Justification: FTBFS in stretch on i386

Hi,

During a rebuild of all packages in stretch (in a stretch chroot, not a
sid chroot), your package failed to build on i386.

Relevant part (hopefully):
> Ensure is_null is handled correctly. ... ok
> test_limited_filter (admin_views.tests.AdminViewBasicTest)
> Ensure admin changelist filters do not contain objects excluded via 
> limit_choices_to. ... ok
> test_logout_and_password_change_URLs (admin_views.tests.AdminViewBasicTest) 
> ... ok
> test_multiple_sort_same_field (admin_views.tests.AdminViewBasicTest) ... ok
> test_named_group_field_choices_change_list 
> (admin_views.tests.AdminViewBasicTest) ... ok
> test_named_group_field_choices_filter (admin_views.tests.AdminViewBasicTest) 
> ... ok
> test_popup_add_POST (admin_views.tests.AdminViewBasicTest) ... ok
> test_popup_dismiss_related (admin_views.tests.AdminViewBasicTest) ... ok
> test_relation_spanning_filters (admin_views.tests.AdminViewBasicTest) ... ok
> test_resolve_admin_views (admin_views.tests.AdminViewBasicTest) ... ok
> test_sort_indicators_admin_order (admin_views.tests.AdminViewBasicTest) ... ok
> test_trailing_slash_required (admin_views.tests.AdminViewBasicTest) ... ok
> test_output_normal (test_runner.test_debug_sql.TestDebugSQL) ... ok
> test_output_verbose (test_runner.test_debug_sql.TestDebugSQL) ... ok
> E: Build killed with signal TERM after 150 minutes of inactivity

The full build log is available from:
   http://aws-logs.debian.net/2017/04/18/python-django_1.10.7-1_testing-i386.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#860663: pytest: FTBFS on i386: segfault during tests

[Lucas Nussbaum]

Source: pytest
Version: 3.0.6-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170418-i386 qa-ftbfs
Justification: FTBFS in stretch on i386

Hi,

During a rebuild of all packages in stretch (in a stretch chroot, not a
sid chroot), your package failed to build on i386.

Relevant part (hopefully):
> ../../../testing/test_pluginmanager.py ...
> ../../../testing/test_pytester.py x...
> ../../../testing/test_recwarn.py ..
> ../../../testing/test_resultlog.py ...
> ../../../testing/test_runner.py 
> ...sss.....x...
> ../../../testing/test_runner_xunit.py ...
> ../../../testing/test_session.py .
> ../../../testing/test_skipping.py 
> ..x..
> ../../../testing/test_terminal.py 
> ..s..s.
> ../../../testing/test_tmpdir.py ...s
> ../../../testing/test_unittest.py 
> ../../../testing/code/test_code.py ..
> ../../../testing/code/test_excinfo.py Segmentation fault
> E: pybuild pybuild:283: test: plugin custom failed with: exit code=139: cd 
> debian/tmp/test-working-directory && pypy -m pytest --lsof -rfsxX 
> --ignore=/<>/testing/freeze 
> --ignore=/<>/testing/test_entry_points.py 
> --ignore=/<>/testing/test_pdb.py /<>/testing
> dh_auto_test: pybuild --test -i pypy -p 5.6 --system=custom --test-args=cd 
> debian/tmp/test-working-directory && {interpreter} -m pytest --lsof -rfsxX 
> --ignore={dir}/testing/freeze --ignore={dir}/testing/test_entry_points.py 
> --ignore={dir}/testing/test_pdb.py {dir}/testing returned exit code 13
> debian/rules:20: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2017/04/18/pytest_3.0.6-1_testing-i386.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#860656: python-biplist: FTBFS on i386: dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 returned exit code 13

[Lucas Nussbaum]

Source: python-biplist
Version: 1.0.1-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170418-i386 qa-ftbfs
Justification: FTBFS in stretch on i386

Hi,

During a rebuild of all packages in stretch (in a stretch chroot, not a
sid chroot), your package failed to build on i386.

Relevant part (hopefully):
>  debian/rules build
> dh build --with python2,python3 --buildsystem=pybuild
>dh_testdir -O--buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:184: python2.7 setup.py config 
> running config
> I: pybuild base:184: python3.5 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:184: /usr/bin/python setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_2.7/build/biplist
> copying biplist/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/biplist
> running egg_info
> writing biplist.egg-info/PKG-INFO
> writing top-level names to biplist.egg-info/top_level.txt
> writing dependency_links to biplist.egg-info/dependency_links.txt
> reading manifest file 'biplist.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> writing manifest file 'biplist.egg-info/SOURCES.txt'
> I: pybuild base:184: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_3.5/build/biplist
> copying biplist/__init__.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/biplist
> running egg_info
> writing dependency_links to biplist.egg-info/dependency_links.txt
> writing biplist.egg-info/PKG-INFO
> writing top-level names to biplist.egg-info/top_level.txt
> reading manifest file 'biplist.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> writing manifest file 'biplist.egg-info/SOURCES.txt'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:184: cd /<>/.pybuild/pythonX.Y_2.7/build; 
> python2.7 -m nose tests
> .F...
> ==
> FAIL: testIntBoundaries (test_write.TestWritePlist)
> --
> Traceback (most recent call last):
>   File "/<>/.pybuild/pythonX.Y_2.7/build/tests/test_write.py", 
> line 272, in testIntBoundaries
> self.roundTrip(cases)
>   File "/<>/.pybuild/pythonX.Y_2.7/build/tests/test_write.py", 
> line 41, in roundTrip
> self.assertEqual(repr(case if expected is None else expected), 
> repr(readResult))
> AssertionError: '[4294967295L, 4294967294L, 4294967296L, 4294967293L, 
> 4294967297L, 8589934590L, 2147483647L]' != '[4294967295L, 4294967294L, 
> 4294967296L, 4294967293L, 4294967297L, 8589934590L, 2147483647]'
> 
> --
> Ran 41 tests in 0.128s
> 
> FAILED (failures=1)
> E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: cd 
> /<>/.pybuild/pythonX.Y_2.7/build; python2.7 -m nose tests
> dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 returned 
> exit code 13

The full build log is available from:
   http://aws-logs.debian.net/2017/04/18/python-biplist_1.0.1-1_testing-i386.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#860619: python-passlib: FTBFS on i386: Test failures

[Lucas Nussbaum]

Source: python-passlib
Version: 1.7.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170418-i386 qa-ftbfs
Justification: FTBFS in stretch on i386

Hi,

During a rebuild of all packages in stretch (in a stretch chroot, not a
sid chroot), your package failed to build on i386.

Relevant part (hopefully):
>   File "", line 673, in _load_unlocked
>   File "", line 673, in exec_module
>   File "", line 222, in _call_with_frames_removed
>   File "/<>/passlib/tests/test_totp.py", line 61, in 
> datetime.datetime.utcfromtimestamp(max_time_t << 1)
> OverflowError: timestamp out of range for platform time_t
> 
> --
> Ran 2810 tests in 217.655s
> 
> FAILED (errors=1, skipped=1191)
> Test failed: 
> error: Test failed:  failures=0>
> E: pybuild pybuild:283: test: plugin custom failed with: exit code=1: 
> python3.5 setup.py test
> dh_auto_test: pybuild --test --test-nose -i python{version} -p 3.5 
> --system=custom --test-args={interpreter} setup.py test returned exit code 13
> debian/rules:9: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2017/04/18/python-passlib_1.7.0-1_testing-i386.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#855924: fedmsg: FTBFS: Test failures

[Lucas Nussbaum]

Source: fedmsg
Version: 0.9.3-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170221 qa-ftbfs
Justification: FTBFS in stretch on amd64

Hi,

During a rebuild of all packages in stretch (in a stretch chroot, not a
sid chroot), your package failed to build on amd64.

Relevant part (hopefully):
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/dist-packages/mock/mock.py", line 1305, in patched
> return func(*args, **keywargs)
>   File "/<>/fedmsg/tests/test_commands.py", line 167, in 
> test_tail_really_pretty
> assert(expected in output)
> AssertionError
> 
> --
> Ran 115 tests in 17.699s
> 
> FAILED (failures=1, errors=6, skipped=44)
> Test failed: 
> error: Test failed:  failures=1>
> E: pybuild pybuild:283: test: plugin custom failed with: exit code=1: 
> python2.7 setup.py test
> dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 returned 
> exit code 13
> debian/rules:39: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2017/02/21/fedmsg_0.9.3-2_testing.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#851043: Bug#834921: python-ws4py: FTBFS on single CPU machines

[Lucas Nussbaum]

On 13/01/17 at 22:43 +0200, Adrian Bunk wrote:
> On Thu, Dec 08, 2016 at 05:47:52PM +0100, Santiago Vila wrote:
> > retitle 834921 python-ws4py: FTBFS on single CPU machines
> > thanks
> > 
> > I tried to build this package 200 times today and it failed 200 times.
> > Then I tried once with a 2-CPU machine and it built ok.
> > 
> > Therefore, to reproduce, please try building on a single-CPU machine.
> 
> What Lucas has reported in #851043 looks like the same test failure.
> 
> Lucas, I assume you were not using a single CPU machine?

By, CPU, do you mean core? no, that Amazon EC2 VM had 63 cores.
If you mean CPU, I don't know what is exposed inside the VM. I could
check if needed. Maybe all 63 cores are seen as from the same CPU.

Lucas

___
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#851043: python-ws4py: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13

[Lucas Nussbaum]

Source: python-ws4py
Version: 0.3.4-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>  debian/rules build
> dh build --with python2,python3,sphinxdoc --buildsystem=pybuild
>dh_testdir -O--buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:184: python2.7 setup.py config 
> running config
> I: pybuild base:184: python3.5 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:184: /usr/bin/python setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_2.7/build/ws4py
> copying ws4py/websocket.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/ws4py
> copying ws4py/compat.py -> /<>/.pybuild/pythonX.Y_2.7/build/ws4py
> copying ws4py/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/ws4py
> copying ws4py/utf8validator.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/ws4py
> copying ws4py/framing.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/ws4py
> copying ws4py/exc.py -> /<>/.pybuild/pythonX.Y_2.7/build/ws4py
> copying ws4py/manager.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/ws4py
> copying ws4py/streaming.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/ws4py
> copying ws4py/messaging.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/ws4py
> creating /<>/.pybuild/pythonX.Y_2.7/build/ws4py/client
> copying ws4py/client/threadedclient.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/ws4py/client
> copying ws4py/client/tornadoclient.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/ws4py/client
> copying ws4py/client/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/ws4py/client
> copying ws4py/client/geventclient.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/ws4py/client
> creating /<>/.pybuild/pythonX.Y_2.7/build/ws4py/server
> copying ws4py/server/cherrypyserver.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/ws4py/server
> copying ws4py/server/geventserver.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/ws4py/server
> copying ws4py/server/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/ws4py/server
> copying ws4py/server/wsgiutils.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/ws4py/server
> copying ws4py/server/wsgirefserver.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/ws4py/server
> I: pybuild base:184: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_3.5/build/ws4py
> copying ws4py/websocket.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/ws4py
> copying ws4py/compat.py -> /<>/.pybuild/pythonX.Y_3.5/build/ws4py
> copying ws4py/__init__.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/ws4py
> copying ws4py/utf8validator.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/ws4py
> copying ws4py/framing.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/ws4py
> copying ws4py/async_websocket.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/ws4py
> copying ws4py/exc.py -> /<>/.pybuild/pythonX.Y_3.5/build/ws4py
> copying ws4py/manager.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/ws4py
> copying ws4py/streaming.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/ws4py
> copying ws4py/messaging.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/ws4py
> creating /<>/.pybuild/pythonX.Y_3.5/build/ws4py/client
> copying ws4py/client/threadedclient.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/ws4py/client
> copying ws4py/client/tornadoclient.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/ws4py/client
> copying ws4py/client/__init__.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/ws4py/client
> copying ws4py/client/geventclient.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/ws4py/client
> creating /<>/.pybuild/pythonX.Y_3.5/build/ws4py/server
> copying ws4py/server/cherrypyserver.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/ws4py/server
> copying ws4py/server/geventserver.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/ws4py/server
> copying ws4py/server/__init__.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/ws4py/server
> copying ws4py/server/tulipserver.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/ws4py/server
> copying ws4py/server/wsgiutils.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/ws4py/server
> copying ws4py/server/wsgirefserver.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/ws4py/server
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild pybuild:212: cp -r /<>/test 
> /<>/.pybuild/pythonX.Y_2.7/build
> I: pybuild base:184: cd /<>/.pybuild/pythonX.Y_2.7/build; 
> python2.7 -m nose test
> F.
> ==
> FAIL: test_mainloop_can_be_stopped_when_no_websocket_were_registered 
> (test.test_manager.WSManagerTest)
> --
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/dist-packages/mock/mock.py", line 1305, in patched
> return func(*args, **

[Python-modules-team] Bug#851014: python-xmp-toolkit: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13

[Lucas Nussbaum]

Source: python-xmp-toolkit
Version: 2.0.1+git20140309.5437b0a-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>  debian/rules build
> dh build  --with python2,python3,sphinxdoc --buildsystem=pybuild
>dh_testdir -O--buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:184: python2.7 setup.py config 
> running config
> I: pybuild base:184: python3.5 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:184: /usr/bin/python setup.py build 
> running build
> running build_py
> creating 
> /<>/python-xmp-toolkit-2.0.1+git20140309.5437b0a/.pybuild/pythonX.Y_2.7/build/libxmp
> copying libxmp/utils.py -> 
> /<>/python-xmp-toolkit-2.0.1+git20140309.5437b0a/.pybuild/pythonX.Y_2.7/build/libxmp
> copying libxmp/files.py -> 
> /<>/python-xmp-toolkit-2.0.1+git20140309.5437b0a/.pybuild/pythonX.Y_2.7/build/libxmp
> copying libxmp/exempi.py -> 
> /<>/python-xmp-toolkit-2.0.1+git20140309.5437b0a/.pybuild/pythonX.Y_2.7/build/libxmp
> copying libxmp/core.py -> 
> /<>/python-xmp-toolkit-2.0.1+git20140309.5437b0a/.pybuild/pythonX.Y_2.7/build/libxmp
> copying libxmp/__init__.py -> 
> /<>/python-xmp-toolkit-2.0.1+git20140309.5437b0a/.pybuild/pythonX.Y_2.7/build/libxmp
> copying libxmp/consts.py -> 
> /<>/python-xmp-toolkit-2.0.1+git20140309.5437b0a/.pybuild/pythonX.Y_2.7/build/libxmp
> copying libxmp/version.py -> 
> /<>/python-xmp-toolkit-2.0.1+git20140309.5437b0a/.pybuild/pythonX.Y_2.7/build/libxmp
> I: pybuild base:184: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating 
> /<>/python-xmp-toolkit-2.0.1+git20140309.5437b0a/.pybuild/pythonX.Y_3.5/build/libxmp
> copying libxmp/utils.py -> 
> /<>/python-xmp-toolkit-2.0.1+git20140309.5437b0a/.pybuild/pythonX.Y_3.5/build/libxmp
> copying libxmp/files.py -> 
> /<>/python-xmp-toolkit-2.0.1+git20140309.5437b0a/.pybuild/pythonX.Y_3.5/build/libxmp
> copying libxmp/exempi.py -> 
> /<>/python-xmp-toolkit-2.0.1+git20140309.5437b0a/.pybuild/pythonX.Y_3.5/build/libxmp
> copying libxmp/core.py -> 
> /<>/python-xmp-toolkit-2.0.1+git20140309.5437b0a/.pybuild/pythonX.Y_3.5/build/libxmp
> copying libxmp/__init__.py -> 
> /<>/python-xmp-toolkit-2.0.1+git20140309.5437b0a/.pybuild/pythonX.Y_3.5/build/libxmp
> copying libxmp/consts.py -> 
> /<>/python-xmp-toolkit-2.0.1+git20140309.5437b0a/.pybuild/pythonX.Y_3.5/build/libxmp
> copying libxmp/version.py -> 
> /<>/python-xmp-toolkit-2.0.1+git20140309.5437b0a/.pybuild/pythonX.Y_3.5/build/libxmp
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:184: python2.7 setup.py test 
> running test
> running egg_info
> creating python_xmp_toolkit.egg-info
> writing requirements to python_xmp_toolkit.egg-info/requires.txt
> writing python_xmp_toolkit.egg-info/PKG-INFO
> writing top-level names to python_xmp_toolkit.egg-info/top_level.txt
> writing dependency_links to python_xmp_toolkit.egg-info/dependency_links.txt
> writing manifest file 'python_xmp_toolkit.egg-info/SOURCES.txt'
> reading manifest file 'python_xmp_toolkit.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> writing manifest file 'python_xmp_toolkit.egg-info/SOURCES.txt'
> running build_ext
> test_jpeg (test.test_roundtrip.TestRoundTrip)
> Create XMP from scratch to store in a jpeg. ... ok
> test_sturm_und_drang (test.test_roundtrip.TestRoundTrip)
> Should be able to write a property which includes umlauts. ... ok
> test_tiff (test.test_roundtrip.TestRoundTrip)
> Write to a TIFF that does not already have the XMP tag. ... ok
> test_3 (test.test_exempi.TestExempi)
> Corresponds to test3.cpp ... ok
> test_bad_formats (test.test_exempi.TestExempi)
> Verify check_file_format on PDF, Adobe Illustrator, XMP. ... skipped 'Issue 
> 26'
> test_bgo (test.test_exempi.TestExempi)
> Corresponds to test-bgo.cpp ... ok
> test_exempi_core (test.test_exempi.TestExempi)
> According to test-exempi-core.cpp ... ok
> test_formats (test.test_exempi.TestExempi)
> Verify that check_file_format function works as expected. ... ok
> test_serialize (test.test_exempi.TestExempi)
> Corresponds to test-serialize.cpp ... ok
> test_tiff_leak (test.test_exempi.TestExempi)
> Corresponds to test-tiff-leak.cpp ... ok
> test_write_new_date_property (test.test_exempi.TestExempi) ... ok
> test_write_new_property (test.test_exempi.TestExempi)
> Corresponds to test-write-new-property.cpp ... ok
> test_xmp_files (test.test_exempi.TestExempi)
> Corresponds to test_xmp_files.cpp ... ok
> test_xmpfiles_write (test.test_exempi.TestExempi)
> According to test-xmpfiles-write.cpp ... ok
> test_init (test.test_exempi.TestInit)
> TODO:  fill in the docstring ... ok
> test_iter_skip_subtree (test.test_exempi.TestIteration)
> Alter the iteration midstream. ... ok
> test_nam

[Python-modules-team] Bug#851020: python-asyncssh: FTBFS: Test failures

[Lucas Nussbaum]

Source: python-asyncssh
Version: 1.8.1-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> sig = yield from agent_key.sign(b'test')
>   File "/<>/asyncssh/agent.py", line 148, in sign
> data, self._flags))
>   File "/<>/asyncssh/agent.py", line 272, in sign
> raise ValueError('Unable to sign with requested key')
> ValueError: Unable to sign with requested key
> 
> --
> Ran 638 tests in 248.313s
> 
> FAILED (errors=1, skipped=2)
> Test failed: 
> error: Test failed:  failures=0>
> E: pybuild pybuild:276: test: plugin distutils failed with: exit code=1: 
> python3.5 setup.py test 
> dh_auto_test: pybuild --test -i python{version} -p 3.5 returned exit code 13
> debian/rules:15: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2017/01/11/python-asyncssh_1.8.1-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#851010: txfixtures: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13

[Lucas Nussbaum]

Source: txfixtures
Version: 0.2.5-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>  debian/rules build
> dh build --with python2,python3 --buildsystem=pybuild
>dh_testdir -O--buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:184: python2.7 setup.py config 
> running config
> I: pybuild base:184: python3.5 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:184: /usr/bin/python setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_2.7/build/txfixtures
> creating /<>/.pybuild/pythonX.Y_2.7/build/txfixtures/_twisted
> copying txfixtures/_twisted/testing.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/txfixtures/_twisted
> copying txfixtures/_twisted/threading.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/txfixtures/_twisted
> copying txfixtures/_twisted/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/txfixtures/_twisted
> creating /<>/.pybuild/pythonX.Y_2.7/build/txfixtures/tests
> copying txfixtures/tests/test_mongodb.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/txfixtures/tests
> copying txfixtures/tests/test_service.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/txfixtures/tests
> copying txfixtures/tests/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/txfixtures/tests
> copying txfixtures/tests/test_phantomjs.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/txfixtures/tests
> copying txfixtures/tests/test_reactor.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/txfixtures/tests
> copying txfixtures/phantomjs.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/txfixtures
> copying txfixtures/tachandler.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/txfixtures
> copying txfixtures/mongodb.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/txfixtures
> copying txfixtures/_testtools.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/txfixtures
> copying txfixtures/osutils.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/txfixtures
> copying txfixtures/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/txfixtures
> copying txfixtures/service.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/txfixtures
> copying txfixtures/reactor.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/txfixtures
> creating 
> /<>/.pybuild/pythonX.Y_2.7/build/txfixtures/_twisted/tests
> copying txfixtures/_twisted/tests/test_threading.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/txfixtures/_twisted/tests
> copying txfixtures/_twisted/tests/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/txfixtures/_twisted/tests
> running egg_info
> writing requirements to txfixtures.egg-info/requires.txt
> writing txfixtures.egg-info/PKG-INFO
> writing top-level names to txfixtures.egg-info/top_level.txt
> writing dependency_links to txfixtures.egg-info/dependency_links.txt
> [pbr] Reusing existing SOURCES.txt
> I: pybuild base:184: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_3.5/build/txfixtures
> creating /<>/.pybuild/pythonX.Y_3.5/build/txfixtures/tests
> copying txfixtures/tests/test_mongodb.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/txfixtures/tests
> copying txfixtures/tests/test_service.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/txfixtures/tests
> copying txfixtures/tests/__init__.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/txfixtures/tests
> copying txfixtures/tests/test_phantomjs.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/txfixtures/tests
> copying txfixtures/tests/test_reactor.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/txfixtures/tests
> copying txfixtures/phantomjs.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/txfixtures
> copying txfixtures/tachandler.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/txfixtures
> copying txfixtures/mongodb.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/txfixtures
> copying txfixtures/_testtools.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/txfixtures
> copying txfixtures/osutils.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/txfixtures
> copying txfixtures/__init__.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/txfixtures
> copying txfixtures/service.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/txfixtures
> copying txfixtures/reactor.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/txfixtures
> creating /<>/.pybuild/pythonX.Y_3.5/build/txfixtures/_twisted
> creating 
> /<>/.pybuild/pythonX.Y_3.5/build/txfixtures/_twisted/tests
> copying txfixtures/_twisted/tests/test_threading.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/txfixtures/_twisted/tests
> copying txfixtures/_twisted/tests/__init__.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/txfixtures/_twisted/tests
> copying txfixtures/_twisted/testing.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/txfixtures/_twisted
> copying txfixtures/_twisted/threading.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/txfixtures/_twisted
> copying txfixtures/_twisted/__init__.py -> 
> /<>/.py

[Python-modules-team] Bug#851001: python-restless: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 3.5 returned exit code 13

[Lucas Nussbaum]

Source: python-restless
Version: 2.0.3-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> I: pybuild base:184: /usr/bin/python setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_2.7/build/restless
> copying restless/it.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/restless
> copying restless/data.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/restless
> copying restless/preparers.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/restless
> copying restless/dj.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/restless
> copying restless/constants.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/restless
> copying restless/pyr.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/restless
> copying restless/utils.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/restless
> copying restless/resources.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/restless
> copying restless/exceptions.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/restless
> copying restless/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/restless
> copying restless/fl.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/restless
> copying restless/tnd.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/restless
> copying restless/serializers.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/restless
> I: pybuild base:184: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_3.5/build/restless
> copying restless/it.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/restless
> copying restless/data.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/restless
> copying restless/preparers.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/restless
> copying restless/dj.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/restless
> copying restless/constants.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/restless
> copying restless/pyr.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/restless
> copying restless/utils.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/restless
> copying restless/resources.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/restless
> copying restless/exceptions.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/restless
> copying restless/__init__.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/restless
> copying restless/fl.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/restless
> copying restless/tnd.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/restless
> copying restless/serializers.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/restless
> PYTHONPATH=. http_proxy='127.0.0.1:9' sphinx-build -N -bhtml docs/ build/html
> Running Sphinx v1.4.9
> making output directory...
> loading pickled environment... not yet created
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 23 source files that are out of date
> updating environment: 23 added, 0 changed, 0 removed
> reading sources... [  4%] contributing
> reading sources... [  8%] cookbook
> reading sources... [ 13%] extending
> reading sources... [ 17%] index
> reading sources... [ 21%] philosophy
> reading sources... [ 26%] reference/constants
> reading sources... [ 30%] reference/data
> reading sources... [ 34%] reference/exceptions
> reading sources... [ 39%] reference/preparers
> reading sources... [ 43%] reference/resources
> reading sources... [ 47%] reference/serializers
> reading sources... [ 52%] reference/utils
> reading sources... [ 56%] releasenotes/v1.0.0
> reading sources... [ 60%] releasenotes/v1.1.0
> reading sources... [ 65%] releasenotes/v1.2.0
> reading sources... [ 69%] releasenotes/v1.3.0
> reading sources... [ 73%] releasenotes/v1.4.0
> reading sources... [ 78%] releasenotes/v2.0.0
> reading sources... [ 82%] releasenotes/v2.0.1
> reading sources... [ 86%] releasenotes/v2.0.2
> reading sources... [ 91%] releasenotes/v2.0.3
> reading sources... [ 95%] security
> reading sources... [100%] tutorial
> 
> /<>/docs/reference/resources.rst:42: WARNING: autodoc: failed to 
> import module u'restless.it'; the following exception was raised:
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/dist-packages/sphinx/ext/autodoc.py", line 529, in 
> import_object
> __import__(self.modname)
>   File "/<>/restless/it.py", line 3, in 
> import itty
> ImportError: No module named itty
> /<>/docs/releasenotes/v2.0.0.rst:64: WARNING: Inline literal 
> start-string without end-string.
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> writing output... [  4%] contributing
> writing output... [  8%] cookbook
> writing output... [ 13%] extending
> writing output... [ 17%] index
> writing output... [ 21%] philosophy
> writing output... [ 26%] reference/constants
> writing output... [ 30%] reference/data
> writing output... [ 34%] reference/exceptions
> writing output..

[Python-modules-team] Bug#850975: sorl-thumbnail: FTBFS: unsatisfiable build-dependencies: python-wand, python3-wand

[Lucas Nussbaum]

Source: sorl-thumbnail
Version: 12.3+git20160928-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), dh-python, graphicsmagick, 
> imagemagick, locales, lsof, python-all, python-django, python-pil, 
> python-pgmagick, python-pytest, python-pytest-django, python-setuptools, 
> python-wand, python3-all, python3-django, python3-pil, python3-pytest, 
> python3-pytest-django, python3-setuptools, python3-wand, python-sphinx (>= 
> 1.0.7+dfsg)
> Merged Build-Conflicts: locales-all (<< 2.21-1)
> Filtered Build-Depends: debhelper (>= 9), dh-python, graphicsmagick, 
> imagemagick, locales, lsof, python-all, python-django, python-pil, 
> python-pgmagick, python-pytest, python-pytest-django, python-setuptools, 
> python-wand, python3-all, python3-django, python3-pil, python3-pytest, 
> python3-pytest-django, python3-setuptools, python3-wand, python-sphinx (>= 
> 1.0.7+dfsg)
> Filtered Build-Conflicts: locales-all (<< 2.21-1)
> dpkg-deb: building package 'sbuild-build-depends-sorl-thumbnail-dummy' in 
> '/<>/resolver-rhhBir/apt_archive/sbuild-build-depends-sorl-thumbnail-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-sorl-thumbnail-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-rhhBir/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-rhhBir/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-rhhBir/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-rhhBir/apt_archive ./ Sources [634 B]
> Get:5 copy:/<>/resolver-rhhBir/apt_archive ./ Packages [715 B]
> Fetched 2312 B in 0s (0 B/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install sorl-thumbnail build dependencies (apt-based resolver)
> --
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> 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:
>  sbuild-build-depends-sorl-thumbnail-dummy : Depends: python-wand but it is 
> not going to be installed
>  Depends: python3-wand but it is 
> not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   
http://aws-logs.debian.net/2017/01/11/sorl-thumbnail_12.3+git20160928-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#850977: willow: FTBFS: build-dependency not installable: python-wand

[Lucas Nussbaum]

Source: willow
Version: 0.3.1-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: dh-python, python-setuptools (>= 0.6b3), python-all (>= 
> 2.6.6-3), debhelper (>= 9), python-sphinx, python-sphinx-rtd-theme, 
> python-sphinxcontrib.spelling, python-mock, python-pil, python-opencv, 
> python-wand
> Filtered Build-Depends: dh-python, python-setuptools (>= 0.6b3), python-all 
> (>= 2.6.6-3), debhelper (>= 9), python-sphinx, python-sphinx-rtd-theme, 
> python-sphinxcontrib.spelling, python-mock, python-pil, python-opencv, 
> python-wand
> dpkg-deb: building package 'sbuild-build-depends-willow-dummy' in 
> '/<>/resolver-CdsBgb/apt_archive/sbuild-build-depends-willow-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-willow-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-CdsBgb/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-CdsBgb/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-CdsBgb/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-CdsBgb/apt_archive ./ Sources [571 B]
> Get:5 copy:/<>/resolver-CdsBgb/apt_archive ./ Packages [649 B]
> Fetched 2183 B in 0s (0 B/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install willow build dependencies (apt-based resolver)
> --
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> 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:
>  sbuild-build-depends-willow-dummy : Depends: python-wand but it is not going 
> to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2017/01/11/willow_0.3.1-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#846771: python-traits: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13

[Lucas Nussbaum]

On 01/01/17 at 18:58 +0500, Andrey Rahmatullin wrote:
> On Sun, Jan 01, 2017 at 02:05:44PM +0100, Lucas Nussbaum wrote:
> > I could on 2016-12-19. Could you post a build log and diff it with mine?
> Attached. I couldn't see anything interesting in the diff, but the failing
> tests succeed and are not skipped.

Strange. Here is an updated build log from today...

Lucas


python-traits.log.gz
Description: application/gzip


signature.asc
Description: PGP signature
___
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#846771: python-traits: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13

[Lucas Nussbaum]

Hi

On 01/01/17 at 17:00 +0500, Andrey Rahmatullin wrote:
> I cannot reproduce this.

I could on 2016-12-19. Could you post a build log and diff it with mine?

Thanks

Lucas


signature.asc
Description: PGP signature
___
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#848779: pyfits: FTBFS: dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 returned exit code 13

[Lucas Nussbaum]

Source: pyfits
Version: 1:3.4-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161219 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>  debian/rules build
> dh build --with python2,python3 --buildsystem=pybuild --parallel 
>dh_testdir -O--buildsystem=pybuild -O--parallel
>dh_update_autotools_config -O--buildsystem=pybuild -O--parallel
>dh_auto_configure -O--buildsystem=pybuild -O--parallel
> I: pybuild base:184: python2.7 setup.py config 
> running config
> I: pybuild base:184: python3.5 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild -O--parallel
> I: pybuild base:184: /usr/bin/python setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_2.7/build/pyfits
> copying pyfits/file.py -> /<>/.pybuild/pythonX.Y_2.7/build/pyfits
> copying pyfits/card.py -> /<>/.pybuild/pythonX.Y_2.7/build/pyfits
> copying pyfits/verify.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits
> copying pyfits/_numpy_hacks.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits
> copying pyfits/py3compat.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits
> copying pyfits/header.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits
> copying pyfits/core.py -> /<>/.pybuild/pythonX.Y_2.7/build/pyfits
> copying pyfits/_release.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits
> copying pyfits/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits
> copying pyfits/column.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits
> copying pyfits/util.py -> /<>/.pybuild/pythonX.Y_2.7/build/pyfits
> copying pyfits/convenience.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits
> copying pyfits/version.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits
> copying pyfits/diff.py -> /<>/.pybuild/pythonX.Y_2.7/build/pyfits
> copying pyfits/fitsrec.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits
> creating /<>/.pybuild/pythonX.Y_2.7/build/pyfits/_compat
> copying pyfits/_compat/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits/_compat
> copying pyfits/_compat/weakref.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits/_compat
> copying pyfits/_compat/odict.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits/_compat
> creating 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits/_compat/_odict_py2
> copying pyfits/_compat/_odict_py2/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits/_compat/_odict_py2
> creating 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits/_compat/_weakset_py2
> copying pyfits/_compat/_weakset_py2/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits/_compat/_weakset_py2
> creating /<>/.pybuild/pythonX.Y_2.7/build/pyfits/extern
> copying pyfits/extern/six.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits/extern
> copying pyfits/extern/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits/extern
> creating /<>/.pybuild/pythonX.Y_2.7/build/pyfits/hdu
> copying pyfits/hdu/table.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits/hdu
> copying pyfits/hdu/image.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits/hdu
> copying pyfits/hdu/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits/hdu
> copying pyfits/hdu/compressed.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits/hdu
> copying pyfits/hdu/hdulist.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits/hdu
> copying pyfits/hdu/streaming.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits/hdu
> copying pyfits/hdu/base.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits/hdu
> copying pyfits/hdu/groups.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits/hdu
> copying pyfits/hdu/nonstandard.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits/hdu
> creating /<>/.pybuild/pythonX.Y_2.7/build/pyfits/scripts
> copying pyfits/scripts/fitscheck.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits/scripts
> copying pyfits/scripts/fitsinfo.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits/scripts
> copying pyfits/scripts/fitsheader.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits/scripts
> copying pyfits/scripts/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits/scripts
> copying pyfits/scripts/fitsdiff.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits/scripts
> creating /<>/.pybuild/pythonX.Y_2.7/build/pyfits/tests
> copying pyfits/tests/test_header.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits/tests
> copying pyfits/tests/test_checksum.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits/tests
> copying pyfits/tests/test_diff.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits/tests
> copying pyfits/tests/test_table.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits/tests
> copying pyfits/tests/test_core.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits/tests
> copying pyfits/tests/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits/tests
> copying pyfits/tests/util.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits/tests
> copying pyfits/tests/test_image.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits/tests
> copying py

[Python-modules-team] Bug#846771: python-traits: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13

[Lucas Nussbaum]

Source: python-traits
Version: 4.6.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161202 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>  debian/rules build
> dh build --with python2,python3,sphinxdoc --buildsystem=pybuild
>dh_testdir -O--buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
>   pybuild --configure -i python{version} -p 2.7
> I: pybuild base:184: python2.7 setup.py config 
> running config
>   pybuild --configure -i python{version} -p 3.5
> I: pybuild base:184: python3.5 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
>   pybuild --build -i python{version} -p 2.7
> I: pybuild base:184: /usr/bin/python setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_2.7/build/traits
> copying traits/_version.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/traits
> copying traits/trait_notifiers.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/traits
> copying traits/_py2to3.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/traits
> copying traits/trait_types.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/traits
> copying traits/traits.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/traits
> copying traits/has_traits.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/traits
> copying traits/category.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/traits
> copying traits/trait_value.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/traits
> copying traits/api.py -> /<>/.pybuild/pythonX.Y_2.7/build/traits
> copying traits/traits_listener.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/traits
> copying traits/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/traits
> copying traits/ustr_trait.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/traits
> copying traits/interface_checker.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/traits
> copying traits/trait_base.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/traits
> copying traits/trait_numeric.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/traits
> copying traits/trait_handlers.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/traits
> copying traits/adapter.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/traits
> copying traits/has_dynamic_views.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/traits
> copying traits/trait_errors.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/traits
> creating /<>/.pybuild/pythonX.Y_2.7/build/traits/util
> copying traits/util/resource.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/traits/util
> copying traits/util/trait_documenter.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/traits/util
> copying traits/util/event_tracer.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/traits/util
> copying traits/util/camel_case.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/traits/util
> copying traits/util/toposort.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/traits/util
> copying traits/util/async_trait_wait.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/traits/util
> copying traits/util/api.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/traits/util
> copying traits/util/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/traits/util
> copying traits/util/home_directory.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/traits/util
> copying traits/util/deprecated.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/traits/util
> copying traits/util/import_symbol.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/traits/util
> copying traits/util/clean_strings.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/traits/util
> creating /<>/.pybuild/pythonX.Y_2.7/build/traits/tests
> copying traits/tests/test_interfaces.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/traits/tests
> copying traits/tests/test_trait_get_set.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/traits/tests
> copying traits/tests/test_traits.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/traits/tests
> copying traits/tests/test_interfaces_with_implements.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/traits/tests
> copying traits/tests/test_get_traits.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/traits/tests
> copying traits/tests/test_dict.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/traits/tests
> copying traits/tests/test_float.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/traits/tests
> copying traits/tests/test_target.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/traits/tests
> copying traits/tests/test_dynamic_notifiers.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/traits/tests
> copying traits/tests/test_listeners.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/traits/tests
> copying traits/tests/test_rich_compare.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/traits/tests
> copying traits/tests/test_trait_types.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/traits/tests
> copying traits/tests/test_dynamic_trait_definition.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/traits/tests
> copying traits/tests/test_property_delete.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/traits/tests
> copying traits/te

[Python-modules-team] Bug#846730: cf-python: FTBFS: XXX

[Lucas Nussbaum]

Source: cf-python
Version: 1.3.2+dfsg1-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161202 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>/cf-python-1.3.2+dfsg1'
> PYTHONPATH=. http_proxy='127.0.0.1:9' sphinx-build -E -b html docs/source 
> docs/build/html
> Running Sphinx v1.4.9
> making output directory...
> 
> Exception occurred:
>   File "/<>/cf-python-1.3.2+dfsg1/cf/units.py", line 267, in 
> 
> _DateFromNoLeapDay = netCDF4.netcdftime.netcdftime._DateFromNoLeapDay
> AttributeError: 'module' object has no attribute 'netcdftime'
> The full traceback has been saved in /tmp/sphinx-err-hCNhQ8.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:14: recipe for target 'override_dh_auto_build-indep' failed
> make[1]: *** [override_dh_auto_build-indep] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2016/12/02/cf-python_1.3.2+dfsg1-3_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#846697: python-aiohttp: FTBFS: dpkg-buildpackage: error: dpkg-source -b python-aiohttp-1.1.5 gave error exit status 2

[Lucas Nussbaum]

Source: python-aiohttp
Version: 1.1.5-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161202 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> rm -rf .cache
> dh_auto_clean
> I: pybuild base:184: python3.5 setup.py clean 
> Compiling aiohttp/_websocket.pyx because it depends on 
> /usr/lib/python3/dist-packages/Cython/Includes/libc/string.pxd.
> [1/1] Cythonizing aiohttp/_websocket.pyx
> running clean
> removing '/<>/.pybuild/pythonX.Y_3.5/build' (and everything 
> under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.5' does not exist -- can't clean it
> I: pybuild base:184: python3.5-dbg setup.py clean 
> running clean
> removing '/<>/.pybuild/pythonX.Y-dbg_3.5/build' (and everything 
> under it)
> setup.py:65: ResourceWarning: unclosed file <_io.TextIOWrapper 
> name='README.rst' mode='r' encoding='ANSI_X3.4-1968'>
>   return open(os.path.join(os.path.dirname(__file__), f)).read().strip()
> setup.py:65: ResourceWarning: unclosed file <_io.TextIOWrapper 
> name='CHANGES.rst' mode='r' encoding='ANSI_X3.4-1968'>
>   return open(os.path.join(os.path.dirname(__file__), f)).read().strip()
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.5' does not exist -- can't clean it
> make[1]: Leaving directory '/<>'
>dh_clean -O--buildsystem=pybuild
>  dpkg-source -b python-aiohttp-1.1.5
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building python-aiohttp using existing 
> ./python-aiohttp_1.1.5.orig.tar.gz
> dpkg-source: info: local changes detected, the modified files are:
>  python-aiohttp-1.1.5/aiohttp/_websocket.c
> dpkg-source: error: aborting due to unexpected upstream changes, see 
> /tmp/python-aiohttp_1.1.5-1.diff.i9z41W
> dpkg-source: info: you can integrate the local changes with dpkg-source 
> --commit
> dpkg-buildpackage: error: dpkg-source -b python-aiohttp-1.1.5 gave error exit 
> status 2
> 
> Build finished at 2016-12-02T19:07:28Z

The full build log is available from:
   http://aws-logs.debian.net/2016/12/02/python-aiohttp_1.1.5-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#846673: pyzmq: FTBFS: timer_createQCzujp.c:(.text+0x15): undefined reference to `timer_create'

[Lucas Nussbaum]

Source: pyzmq
Version: 15.4.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161202 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> cc build/temp.linux-x86_64-2.7/scratch/tmp/timer_createQCzujp.o -o 
> build/temp.linux-x86_64-2.7/scratch/a.out
> build/temp.linux-x86_64-2.7/scratch/tmp/timer_createQCzujp.o: In function 
> `main':
> timer_createQCzujp.c:(.text+0x15): undefined reference to `timer_create'
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://aws-logs.debian.net/2016/12/02/pyzmq_15.4.0-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#844919: Bug#844919: pytest: FTBFS: Tests failures

[Lucas Nussbaum]

On 19/11/16 at 11:06 +0100, Sebastian Ramacher wrote:
> Control: severity -1 important
> 
> On 2016-11-19 08:04:11, Lucas Nussbaum wrote:
> > Source: pytest
> > Version: 3.0.3-1
> > Severity: serious
> > Tags: stretch sid
> > User: debian...@lists.debian.org
> > Usertags: qa-ftbfs-20161118 qa-ftbfs
> > Justification: FTBFS on amd64
> > 
> > Hi,
> > 
> > During a rebuild of all packages in sid, your package failed to build on
> > amd64.
> > 
> > Relevant part (hopefully):
> > > /usr/lib/python2.7/dist-packages/twisted/trial/_synctest.py:23: in 
> > > 
> > > from twisted.trial import itrial, util
> > > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> > > _ _ _ 
> > > 
> > > """
> > > 
> > > from __future__ import division, absolute_import
> > > 
> > > >   import zope.interface as zi
> > > E   AttributeError: 'module' object has no attribute 'interface'
> > > 
> > > /usr/lib/python2.7/dist-packages/twisted/trial/itrial.py:12: 
> > > AttributeError
> > > === 3 failed, 1640 passed, 26 skipped, 13 xfailed, 4 error in 71.75 
> > > seconds 
> > > E: pybuild pybuild:276: test: plugin custom failed with: exit code=1: cd 
> > > debian/tmp/test-working-directory && python2.7 -m pytest --lsof -rfsxX 
> > > --ignore=/<>/testing/freeze 
> > > --ignore=/<>/testing/test_entry_points.py 
> > > --ignore=/<>/testing/test_pdb.py /<>/testing
> > > dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 
> > > --system=custom --test-args=cd debian/tmp/test-working-directory && 
> > > {interpreter} -m pytest --lsof -rfsxX --ignore={dir}/testing/freeze 
> > > --ignore={dir}/testing/test_entry_points.py 
> > > --ignore={dir}/testing/test_pdb.py {dir}/testing returned exit code 13
> > > debian/rules:25: recipe for target 'override_dh_auto_test' failed
> 
> I added a workaround in 3.0.4-1 by moving twisted to Build-Conflicts. Keeping
> the bug report open until the upstream issue is fixed.

That's strange: the build was done in a clean chroot, so twisted is
probably pulled by a build-dep

Lucas

___
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#844934: obsub: FTBFS: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 2855: ordinal not in range(128)

[Lucas Nussbaum]

Source: obsub
Version: 0.2-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --with python2,python3 --buildsystem=pybuild
>dh_testdir -O--buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:184: python2.7 setup.py clean 
> running clean
> removing '/<>/.pybuild/pythonX.Y_2.7/build' (and everything 
> under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-2.7' does not exist -- can't clean it
> I: pybuild base:184: python3.5 setup.py clean 
> Traceback (most recent call last):
>   File "setup.py", line 10, in 
> long_description = open('README.rst').read()
>   File "/usr/lib/python3.5/encodings/ascii.py", line 26, in decode
> return codecs.ascii_decode(input, self.errors)[0]
> UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 2855: 
> ordinal not in range(128)
> E: pybuild pybuild:276: clean: plugin distutils failed with: exit code=1: 
> python3.5 setup.py clean 
> dh_auto_clean: pybuild --clean --test-nose -i python{version} -p 3.5 returned 
> exit code 13
> debian/rules:6: recipe for target 'clean' failed
> make: *** [clean] Error 25

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/obsub_0.2-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#844907: python-tornado: FTBFS: Tests failures

[Lucas Nussbaum]

Source: python-tornado
Version: 4.4.2-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> 
> --
> Ran 1463 tests in 10.780s
> 
> FAILED (failures=1, errors=7, skipped=57)
> Some tests were skipped because: PEP 380 (yield from) not available,
> PEP 492 (async/await) not available, Prevent internet access during
> build, asyncio 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
> [E 161118 23:29:11 testing:735] FAIL
> [E 161118 23:29:11 runtests:182] logged 17 warnings and 2 errors
> E: pybuild pybuild:276: test: plugin custom failed with: exit code=1: 
> python2.7 ./tornado/test/runtests.py --verbose
> dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
> debian/rules:14: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/python-tornado_4.4.2-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#844919: pytest: FTBFS: Tests failures

[Lucas Nussbaum]

Source: pytest
Version: 3.0.3-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> /usr/lib/python2.7/dist-packages/twisted/trial/_synctest.py:23: in 
> from twisted.trial import itrial, util
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> 
> """
> 
> from __future__ import division, absolute_import
> 
> >   import zope.interface as zi
> E   AttributeError: 'module' object has no attribute 'interface'
> 
> /usr/lib/python2.7/dist-packages/twisted/trial/itrial.py:12: AttributeError
> === 3 failed, 1640 passed, 26 skipped, 13 xfailed, 4 error in 71.75 seconds 
> 
> E: pybuild pybuild:276: test: plugin custom failed with: exit code=1: cd 
> debian/tmp/test-working-directory && python2.7 -m pytest --lsof -rfsxX 
> --ignore=/<>/testing/freeze 
> --ignore=/<>/testing/test_entry_points.py 
> --ignore=/<>/testing/test_pdb.py /<>/testing
> dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 
> --system=custom --test-args=cd debian/tmp/test-working-directory && 
> {interpreter} -m pytest --lsof -rfsxX --ignore={dir}/testing/freeze 
> --ignore={dir}/testing/test_entry_points.py 
> --ignore={dir}/testing/test_pdb.py {dir}/testing returned exit code 13
> debian/rules:25: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/pytest_3.0.3-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#844863: python-mysqldb: FTBFS: x86_64-linux-gnu-gcc: error: .specs: No such file or directory

[Lucas Nussbaum]

Source: python-mysqldb
Version: 1.3.7-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall 
> -Wstrict-prototypes -fno-strict-aliasing -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
> -Dversion_info=(1,3,7,'final',1) -D__version__=1.3.7 -I/usr/include/mysql 
> -I/usr/include/python2.7 -c _mysql.c -o build/temp.linux-x86_64-2.7/_mysql.o 
> -fdebug-prefix-map=/build/mysql-5.7-lG4h93/mysql-5.7-5.7.16=. .specs 
> -fabi-version=2 -fno-omit-frame-pointer
> x86_64-linux-gnu-gcc: error: .specs: No such file or directory
> error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
> E: pybuild pybuild:276: 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 returned exit code 13
> debian/rules:15: recipe for target 'build' failed
> make: *** [build] Error 25

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/python-mysqldb_1.3.7-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#844792: python-django-debug-toolbar: FTBFS: unsatisfiable build-dependencies: python-sqlparse (< 0.2.0), python3-sqlparse (< 0.2.0)

[Lucas Nussbaum]

Source: python-django-debug-toolbar
Version: 1:1.5-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), dh-python, python-all, python3-all, 
> python-django, python3-django, python-setuptools, python3-setuptools, 
> python-sphinx (>= 1.0.7+dfsg-1~), python-sqlparse (<< 0.2.0), 
> python3-sqlparse (<< 0.2.0)
> Filtered Build-Depends: debhelper (>= 9), dh-python, python-all, python3-all, 
> python-django, python3-django, python-setuptools, python3-setuptools, 
> python-sphinx (>= 1.0.7+dfsg-1~), python-sqlparse (<< 0.2.0), 
> python3-sqlparse (<< 0.2.0)
> dpkg-deb: building package 
> 'sbuild-build-depends-python-django-debug-toolbar-dummy' in 
> '/<>/resolver-7Z5M46/apt_archive/sbuild-build-depends-python-django-debug-toolbar-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   
> sbuild-build-depends-python-django-debug-toolbar-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-7Z5M46/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-7Z5M46/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/resolver-7Z5M46/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-7Z5M46/apt_archive ./ Sources [430 B]
> Get:5 copy:/<>/resolver-7Z5M46/apt_archive ./ Packages [523 B]
> Fetched 1910 B in 0s (171 kB/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install python-django-debug-toolbar build dependencies (apt-based resolver)
> ---
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> 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:
>  sbuild-build-depends-python-django-debug-toolbar-dummy : Depends: 
> python-sqlparse (< 0.2.0) but it is not going to be installed
>   Depends: 
> python3-sqlparse (< 0.2.0) but it is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   
http://aws-logs.debian.net/2016/11/18/python-django-debug-toolbar_1.5-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#844795: datanommer.consumer: FTBFS: build-dependency not installable: python-datanommer.models

[Lucas Nussbaum]

Source: datanommer.consumer
Version: 0.6.1-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), dh-python, python-all, 
> python-datanommer.models, python-fedmsg, python-mock, python-nose, 
> python-setuptools
> Filtered Build-Depends: debhelper (>= 9), dh-python, python-all, 
> python-datanommer.models, python-fedmsg, python-mock, python-nose, 
> python-setuptools
> dpkg-deb: building package 'sbuild-build-depends-datanommer.consumer-dummy' 
> in 
> '/<>/resolver-MChyJR/apt_archive/sbuild-build-depends-datanommer.consumer-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-datanommer.consumer-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-MChyJR/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-MChyJR/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/resolver-MChyJR/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-MChyJR/apt_archive ./ Sources [396 B]
> Get:5 copy:/<>/resolver-MChyJR/apt_archive ./ Packages [485 B]
> Fetched 1838 B in 0s (0 B/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install datanommer.consumer build dependencies (apt-based resolver)
> ---
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> 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:
>  sbuild-build-depends-datanommer.consumer-dummy : Depends: 
> python-datanommer.models but it is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   
http://aws-logs.debian.net/2016/11/18/datanommer.consumer_0.6.1-2_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#844139: python-django: FTBFS: Tests failures

[Lucas Nussbaum]

Hi,

On 16/11/16 at 18:44 +0100, Raphael Hertzog wrote:
> Hi,
> 
> On Sat, 12 Nov 2016, Scott Kitterman wrote:
> > > This failure happens on a CPU with TSX extensions available, but is not
> > > reproducible on a machine without them. 
> 
> I can't reproduce this either on my machine. But I have other failures
> (see below).
> 
> Lucas, can you see if you reproduce your problem with this small
> patch:
> --- a/debian/rules
> +++ b/debian/rules
> @@ -23,7 +23,7 @@ override_dh_auto_test:
>  ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
> set -e; cd tests && for python in $$(pyversions -s) $$(py3versions 
> -s); do \
> echo "——— Running tests with $$python ———"; \
> -   LC_ALL=C.UTF-8 PYTHONPATH=.. $$python ./runtests.py 
> --verbosity=2; \
> +   LC_ALL=C.UTF-8 PYTHONPATH=.. $$python ./runtests.py 
> --verbosity=2 --parallel=4; \
> done
>  endif

I can still reproduce the problem today _without_ the patch;
and adding --parallel=4 "fixes" the problem.

Lucas

___
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#844139: python-django: FTBFS: Tests failures

[Lucas Nussbaum]

Source: python-django
Version: 1:1.10.3-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-2016 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> Destroying test database for alias 'other' (':memory:')...
> Destroying test database for alias 'other' (':memory:')...
> Destroying test database for alias 'other' (':memory:')...
> Destroying test database for alias 'other' (':memory:')...
> Destroying test database for alias 'other' (':memory:')...
> Destroying test database for alias 'other' (':memory:')...
> Destroying test database for alias 'other' (':memory:')...
> Destroying test database for alias 'other' (':memory:')...
> Destroying test database for alias 'other' (':memory:')...
> Destroying test database for alias 'other' (':memory:')...
> Destroying test database for alias 'other' (':memory:')...
> Destroying test database for alias 'other' (':memory:')...
> Destroying test database for alias 'other' (':memory:')...
> Destroying test database for alias 'other' (':memory:')...
> Destroying test database for alias 'other' (':memory:')...
> debian/rules:24: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2016/11/11/python-django_1.10.3-1_unstable.log

This failure happens on a CPU with TSX extensions available, but is not
reproducible on a machine without them. For context, I recommend reading the
thread starting at https://lists.debian.org/debian-devel/2016/11/msg00210.html

The node used is an Amazon EC2 VM with 64 cores. /proc/cpuinfo says:
   model: 79
   model name : Intel(R) Xeon(R) CPU E5-2686 v4 @ 2.30GHz
   stepping : 1

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#841596: sqlobject: FTBFS: tests failed

[Lucas Nussbaum]

Source: sqlobject
Version: 3.1.0+dfsg-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>  debian/rules build
> dh build --with python2,python3 --buildsystem=pybuild
>dh_testdir -O--buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:184: python2.7 setup.py config 
> running config
> I: pybuild base:184: python3.5 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:184: /usr/bin/python setup.py build 
> running build
> running build_py
> creating 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject
> copying sqlobject/events.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject
> copying sqlobject/joins.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject
> copying sqlobject/styles.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject
> copying sqlobject/cache.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject
> copying sqlobject/conftest.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject
> copying sqlobject/converters.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject
> copying sqlobject/wsgi_middleware.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject
> copying sqlobject/classregistry.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject
> copying sqlobject/compat.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject
> copying sqlobject/views.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject
> copying sqlobject/__init__.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject
> copying sqlobject/main.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject
> copying sqlobject/sqlbuilder.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject
> copying sqlobject/col.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject
> copying sqlobject/boundattributes.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject
> copying sqlobject/dbconnection.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject
> copying sqlobject/__version__.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject
> copying sqlobject/declarative.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject
> copying sqlobject/dberrors.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject
> copying sqlobject/sresults.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject
> copying sqlobject/constraints.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject
> copying sqlobject/index.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject
> creating 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject/firebird
> copying sqlobject/firebird/firebirdconnection.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject/firebird
> copying sqlobject/firebird/__init__.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject/firebird
> creating 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject/include
> copying sqlobject/include/hashcol.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject/include
> copying sqlobject/include/__init__.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject/include
> creating 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject/include/tests
> copying sqlobject/include/tests/__init__.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject/include/tests
> copying sqlobject/include/tests/test_hashcol.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject/include/tests
> creating 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject/inheritance
> copying sqlobject/inheritance/__init__.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject/inheritance
> copying sqlobject/inheritance/iteration.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject/inheritance
> creating 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject/inheritance/tests
> copying sqlobject/inheritance/tests/test_aggregates.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject/inheritance/tests
> copying sqlobject/inheritance/tests/test_indexes.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject/inheritance/tests
> copying sqlobject/inheritance/tests/test_foreignKey.py -> 
> /<>/sqlobject-3.1.0+dfsg/.pybuild/pythonX.Y_2.7/build/sqlobject/inheritance/tests
> cop

[Python-modules-team] Bug#841582: sphinxcontrib-doxylink: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13

[Lucas Nussbaum]

Source: sphinxcontrib-doxylink
Version: 1.3-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>  debian/rules build
> dh build --with python2,python3 --buildsystem=pybuild
>dh_testdir -O--buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:184: python2.7 setup.py config 
> running config
> I: pybuild base:184: python3.5 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:184: /usr/bin/python setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_2.7/build/sphinxcontrib
> copying sphinxcontrib/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/sphinxcontrib
> creating /<>/.pybuild/pythonX.Y_2.7/build/tests
> copying tests/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/tests
> copying tests/test_parser.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/tests
> creating /<>/.pybuild/pythonX.Y_2.7/build/sphinxcontrib/doxylink
> copying sphinxcontrib/doxylink/doxylink.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/sphinxcontrib/doxylink
> copying sphinxcontrib/doxylink/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/sphinxcontrib/doxylink
> copying sphinxcontrib/doxylink/parsing.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/sphinxcontrib/doxylink
> running egg_info
> writing requirements to sphinxcontrib_doxylink.egg-info/requires.txt
> writing sphinxcontrib_doxylink.egg-info/PKG-INFO
> writing namespace_packages to 
> sphinxcontrib_doxylink.egg-info/namespace_packages.txt
> writing top-level names to sphinxcontrib_doxylink.egg-info/top_level.txt
> writing dependency_links to 
> sphinxcontrib_doxylink.egg-info/dependency_links.txt
> reading manifest file 'sphinxcontrib_doxylink.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no files found matching 'LICENSE'
> writing manifest file 'sphinxcontrib_doxylink.egg-info/SOURCES.txt'
> I: pybuild base:184: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_3.5/build/sphinxcontrib
> copying sphinxcontrib/__init__.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/sphinxcontrib
> creating /<>/.pybuild/pythonX.Y_3.5/build/tests
> copying tests/__init__.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/tests
> copying tests/test_parser.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/tests
> creating /<>/.pybuild/pythonX.Y_3.5/build/sphinxcontrib/doxylink
> copying sphinxcontrib/doxylink/doxylink.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/sphinxcontrib/doxylink
> copying sphinxcontrib/doxylink/__init__.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/sphinxcontrib/doxylink
> copying sphinxcontrib/doxylink/parsing.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/sphinxcontrib/doxylink
> running egg_info
> writing dependency_links to 
> sphinxcontrib_doxylink.egg-info/dependency_links.txt
> writing top-level names to sphinxcontrib_doxylink.egg-info/top_level.txt
> writing namespace_packages to 
> sphinxcontrib_doxylink.egg-info/namespace_packages.txt
> writing sphinxcontrib_doxylink.egg-info/PKG-INFO
> writing requirements to sphinxcontrib_doxylink.egg-info/requires.txt
> reading manifest file 'sphinxcontrib_doxylink.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no files found matching 'LICENSE'
> writing manifest file 'sphinxcontrib_doxylink.egg-info/SOURCES.txt'
> Fixing 
> /<>/.pybuild/pythonX.Y_3.5/build/sphinxcontrib/__init__.py 
> /<>/.pybuild/pythonX.Y_3.5/build/tests/__init__.py 
> /<>/.pybuild/pythonX.Y_3.5/build/tests/test_parser.py 
> /<>/.pybuild/pythonX.Y_3.5/build/sphinxcontrib/doxylink/doxylink.py
>  
> /<>/.pybuild/pythonX.Y_3.5/build/sphinxcontrib/doxylink/__init__.py
>  
> /<>/.pybuild/pythonX.Y_3.5/build/sphinxcontrib/doxylink/parsing.py
> Skipping optional fixer: buffer
> Skipping optional fixer: idioms
> Skipping optional fixer: set_literal
> Skipping optional fixer: ws_comma
> Fixing 
> /<>/.pybuild/pythonX.Y_3.5/build/sphinxcontrib/__init__.py 
> /<>/.pybuild/pythonX.Y_3.5/build/tests/__init__.py 
> /<>/.pybuild/pythonX.Y_3.5/build/tests/test_parser.py 
> /<>/.pybuild/pythonX.Y_3.5/build/sphinxcontrib/doxylink/doxylink.py
>  
> /<>/.pybuild/pythonX.Y_3.5/build/sphinxcontrib/doxylink/__init__.py
>  
> /<>/.pybuild/pythonX.Y_3.5/build/sphinxcontrib/doxylink/parsing.py
> Skipping optional fixer: buffer
> Skipping optional fixer: idioms
> Skipping optional fixer: set_literal
> Skipping optional fixer: ws_comma
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:184: python2.7 setup.py test 
> running test
> running egg_info
> writing requirements to sphinxcontrib_doxylink.egg-info/requires.txt
> writing sphinxcontrib_doxylink.egg-info/PKG-INFO
> writing namespace_packages to 
> sphinxcontrib_doxylink.egg-info/namespace_packages.tx

[Python-modules-team] Bug#841552: python-feather-format: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13

[Lucas Nussbaum]

Source: python-feather-format
Version: 0.3.0+dfsg1-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>  debian/rules build
> dh build --with python2,python3 --buildsystem=pybuild
>dh_testdir -O--buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:184: python2.7 setup.py config 
> Compiling feather/ext.pyx because it changed.
> [1/1] Cythonizing feather/ext.pyx
> running config
> I: pybuild base:184: python3.5 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:184: /usr/bin/python setup.py build 
> running build
> running build_py
> creating 
> /<>/python-feather-format-0.3.0+dfsg1/.pybuild/pythonX.Y_2.7/build/feather
> copying feather/api.py -> 
> /<>/python-feather-format-0.3.0+dfsg1/.pybuild/pythonX.Y_2.7/build/feather
> copying feather/compat.py -> 
> /<>/python-feather-format-0.3.0+dfsg1/.pybuild/pythonX.Y_2.7/build/feather
> copying feather/__init__.py -> 
> /<>/python-feather-format-0.3.0+dfsg1/.pybuild/pythonX.Y_2.7/build/feather
> copying feather/version.py -> 
> /<>/python-feather-format-0.3.0+dfsg1/.pybuild/pythonX.Y_2.7/build/feather
> creating 
> /<>/python-feather-format-0.3.0+dfsg1/.pybuild/pythonX.Y_2.7/build/feather/tests
> copying feather/tests/test_reader.py -> 
> /<>/python-feather-format-0.3.0+dfsg1/.pybuild/pythonX.Y_2.7/build/feather/tests
> copying feather/tests/__init__.py -> 
> /<>/python-feather-format-0.3.0+dfsg1/.pybuild/pythonX.Y_2.7/build/feather/tests
> copying feather/libfeather.pxd -> 
> /<>/python-feather-format-0.3.0+dfsg1/.pybuild/pythonX.Y_2.7/build/feather
> copying feather/ext.pyx -> 
> /<>/python-feather-format-0.3.0+dfsg1/.pybuild/pythonX.Y_2.7/build/feather
> running build_ext
> building 'feather.ext' extension
> creating build
> creating build/temp.linux-x86_64-2.7
> creating build/temp.linux-x86_64-2.7/feather
> creating build/temp.linux-x86_64-2.7/src
> creating build/temp.linux-x86_64-2.7/src/feather
> x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall 
> -Wstrict-prototypes -fno-strict-aliasing -g -O2 
> -fdebug-prefix-map=/<>/python-feather-format-0.3.0+dfsg1=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -fPIC -Ifeather 
> -I/usr/lib/python2.7/dist-packages/numpy/core/include 
> -I/<>/python-feather-format-0.3.0+dfsg1/src 
> -I/usr/include/python2.7 -c feather/ext.cpp -o 
> build/temp.linux-x86_64-2.7/feather/ext.o -std=c++11 -O3
> cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for 
> C/ObjC but not for C++
> In file included from 
> /usr/lib/python2.7/dist-packages/numpy/core/include/numpy/ndarraytypes.h:1777:0,
>  from 
> /usr/lib/python2.7/dist-packages/numpy/core/include/numpy/ndarrayobject.h:18,
>  from 
> /usr/lib/python2.7/dist-packages/numpy/core/include/numpy/arrayobject.h:4,
>  from feather/ext.cpp:318:
> /usr/lib/python2.7/dist-packages/numpy/core/include/numpy/npy_1_7_deprecated_api.h:15:2:
>  warning: #warning "Using deprecated NumPy API, disable it by " "#defining 
> NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION" [-Wcpp]
>  #warning "Using deprecated NumPy API, disable it by " \
>   ^~~
> x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall 
> -Wstrict-prototypes -fno-strict-aliasing -g -O2 
> -fdebug-prefix-map=/<>/python-feather-format-0.3.0+dfsg1=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -fPIC -Ifeather 
> -I/usr/lib/python2.7/dist-packages/numpy/core/include 
> -I/<>/python-feather-format-0.3.0+dfsg1/src 
> -I/usr/include/python2.7 -c src/feather/buffer.cc -o 
> build/temp.linux-x86_64-2.7/src/feather/buffer.o -std=c++11 -O3
> cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for 
> C/ObjC but not for C++
> x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall 
> -Wstrict-prototypes -fno-strict-aliasing -g -O2 
> -fdebug-prefix-map=/<>/python-feather-format-0.3.0+dfsg1=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -fPIC -Ifeather 
> -I/usr/lib/python2.7/dist-packages/numpy/core/include 
> -I/<>/python-feather-format-0.3.0+dfsg1/src 
> -I/usr/include/python2.7 -c src/feather/io.cc -o 
> build/temp.linux-x86_64-2.7/src/feather/io.o -std=c++11 -O3
> cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for 
> C/ObjC but not for C++
> x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall 
> -Wstrict-prototypes -fno-strict-aliasing -g -O2 
> -fdebug-prefix-map=/<>/python-feather-format-0.3.0+dfsg1=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_

[Python-modules-team] Bug#839366: pysvn: FTBFS: unsatisfiable build-dependencies: python-cxx-dev (< 6.2.7), python3-cxx-dev (< 6.2.7)

[Lucas Nussbaum]

Source: pysvn
Version: 1.8.0-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160930 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), dh-python, libapr1-dev, 
> libaprutil1-dev, libneon27-gnutls-dev, libsvn-dev (>= 1.8.10), 
> python-all-dbg, python-all-dev (>= 2.7.8), python-cxx-dev (<< 6.2.7), 
> python-setuptools, python3-all (>= 3.4.2), python3-all-dev (>= 3.4.2), 
> python3-setuptools (>= 5.5.1), python3-cxx-dev (<< 6.2.7), subversion (>= 
> 1.8.10)
> Filtered Build-Depends: debhelper (>= 9), dh-python, libapr1-dev, 
> libaprutil1-dev, libneon27-gnutls-dev, libsvn-dev (>= 1.8.10), 
> python-all-dbg, python-all-dev (>= 2.7.8), python-cxx-dev (<< 6.2.7), 
> python-setuptools, python3-all (>= 3.4.2), python3-all-dev (>= 3.4.2), 
> python3-setuptools (>= 5.5.1), python3-cxx-dev (<< 6.2.7), subversion (>= 
> 1.8.10)
> dpkg-deb: building package 'sbuild-build-depends-pysvn-dummy' in 
> '/<>/resolver-T8ycuP/apt_archive/sbuild-build-depends-pysvn-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-pysvn-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-T8ycuP/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-T8ycuP/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/resolver-T8ycuP/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-T8ycuP/apt_archive ./ Sources [461 B]
> Get:5 copy:/<>/resolver-T8ycuP/apt_archive ./ Packages [550 B]
> Fetched 1968 B in 0s (0 B/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install pysvn build dependencies (apt-based resolver)
> -
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> 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:
>  sbuild-build-depends-pysvn-dummy : Depends: python-cxx-dev (< 6.2.7) but it 
> is not going to be installed
> Depends: python3-cxx-dev (< 6.2.7) but it 
> is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2016/09/30/pysvn_1.8.0-2_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#839299: quark-sphinx-theme: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 3.5 returned exit code 13

[Lucas Nussbaum]

Source: quark-sphinx-theme
Version: 0.3.2-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160930 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>  debian/rules build
> dh build --with python2,python3 --buildsystem=pybuild
>dh_testdir -O--buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:184: python2.7 setup.py config 
> running config
> I: pybuild base:184: python3.5 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:184: /usr/bin/python setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_2.7/build/quark_sphinx_theme
> copying quark_sphinx_theme/_mixin.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/quark_sphinx_theme
> copying quark_sphinx_theme/_lovelace.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/quark_sphinx_theme
> copying quark_sphinx_theme/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/quark_sphinx_theme
> copying quark_sphinx_theme/__version__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/quark_sphinx_theme
> creating /<>/.pybuild/pythonX.Y_2.7/build/quark_sphinx_theme/ext
> copying quark_sphinx_theme/ext/html_compat.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/quark_sphinx_theme/ext
> copying quark_sphinx_theme/ext/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/quark_sphinx_theme/ext
> creating 
> /<>/.pybuild/pythonX.Y_2.7/build/quark_sphinx_theme/ext/html_rewrite
> copying quark_sphinx_theme/ext/html_rewrite/compat.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/quark_sphinx_theme/ext/html_rewrite
> copying quark_sphinx_theme/ext/html_rewrite/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/quark_sphinx_theme/ext/html_rewrite
> copying quark_sphinx_theme/ext/html_rewrite/boxes.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/quark_sphinx_theme/ext/html_rewrite
> copying quark_sphinx_theme/ext/html_rewrite/literal_blocks.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/quark_sphinx_theme/ext/html_rewrite
> running egg_info
> writing quark_sphinx_theme.egg-info/PKG-INFO
> writing top-level names to quark_sphinx_theme.egg-info/top_level.txt
> writing dependency_links to quark_sphinx_theme.egg-info/dependency_links.txt
> writing entry points to quark_sphinx_theme.egg-info/entry_points.txt
> reading manifest file 'quark_sphinx_theme.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> writing manifest file 'quark_sphinx_theme.egg-info/SOURCES.txt'
> creating 
> /<>/.pybuild/pythonX.Y_2.7/build/quark_sphinx_theme/quark
> copying quark_sphinx_theme/quark/domainindex.html -> 
> /<>/.pybuild/pythonX.Y_2.7/build/quark_sphinx_theme/quark
> copying quark_sphinx_theme/quark/genindex-single.html -> 
> /<>/.pybuild/pythonX.Y_2.7/build/quark_sphinx_theme/quark
> copying quark_sphinx_theme/quark/genindex.html -> 
> /<>/.pybuild/pythonX.Y_2.7/build/quark_sphinx_theme/quark
> copying quark_sphinx_theme/quark/layout.html -> 
> /<>/.pybuild/pythonX.Y_2.7/build/quark_sphinx_theme/quark
> copying quark_sphinx_theme/quark/theme.conf -> 
> /<>/.pybuild/pythonX.Y_2.7/build/quark_sphinx_theme/quark
> creating 
> /<>/.pybuild/pythonX.Y_2.7/build/quark_sphinx_theme/quark/static
> copying quark_sphinx_theme/quark/static/quark.css_t -> 
> /<>/.pybuild/pythonX.Y_2.7/build/quark_sphinx_theme/quark/static
> I: pybuild base:184: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_3.5/build/quark_sphinx_theme
> copying quark_sphinx_theme/_mixin.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/quark_sphinx_theme
> copying quark_sphinx_theme/_lovelace.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/quark_sphinx_theme
> copying quark_sphinx_theme/__init__.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/quark_sphinx_theme
> copying quark_sphinx_theme/__version__.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/quark_sphinx_theme
> creating /<>/.pybuild/pythonX.Y_3.5/build/quark_sphinx_theme/ext
> copying quark_sphinx_theme/ext/html_compat.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/quark_sphinx_theme/ext
> copying quark_sphinx_theme/ext/__init__.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/quark_sphinx_theme/ext
> creating 
> /<>/.pybuild/pythonX.Y_3.5/build/quark_sphinx_theme/ext/html_rewrite
> copying quark_sphinx_theme/ext/html_rewrite/compat.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/quark_sphinx_theme/ext/html_rewrite
> copying quark_sphinx_theme/ext/html_rewrite/__init__.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/quark_sphinx_theme/ext/html_rewrite
> copying quark_sphinx_theme/ext/html_rewrite/boxes.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/quark_sphinx_theme/ext/html_rewrite
> copying quark_sphinx_theme/ext/html_rewrite/literal_blocks.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/quark_sphinx_theme/ext/html_rewrite
> running egg_info
> writing top-level names to quark_sphinx_theme.egg-info/top_level.txt
> writi

[Python-modules-team] Bug#837295: python-rply: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13

[Lucas Nussbaum]

Source: python-rply
Version: 0.7.4-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160910 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>  fakeroot debian/rules clean
> CDBS WARNING:  copyright-check disabled - licensecheck is missing.
> debian/rules:25: *** target file 'debian/python-module-stampdir/pypy-rply' 
> has both : and :: entries.  Stop.
> dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2
> 
> Build finished at 2016-09-09T15:14:04Z

The full build log is available from:
   http://aws-logs.debian.net/2016/09/10/python-rply_0.7.4-1_unstable.log
(That DNS record was just updated. Use
http://ec2-52-58-237-241.eu-central-1.compute.amazonaws.com if it
doesn't work)

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#837262: python-axiom: FTBFS: debian/rules:15: *** no python implementation resolved from flavor "python". Stop.

[Lucas Nussbaum]

Source: python-axiom
Version: 0.7.5-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160910 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>  fakeroot debian/rules binary
> test -x debian/rules
> dh_testroot
> dh_prep 
>   rm -f debian/python-axiom.substvars
>   rm -f debian/python-axiom.*.debhelper
>   rm -rf debian/python-axiom/
> dh_installdirs -A 
>   install -d debian/python-axiom
> mkdir -p "."
> mkdir -p debian/python-module-stampdir
> cd . && python setup.py build --build-base="/<>/./build"
> running build
> running build_py
> package init file 'twisted/plugins/__init__.py' not found (or not a regular 
> file)
> running egg_info
> writing requirements to Axiom.egg-info/requires.txt
> writing Axiom.egg-info/PKG-INFO
> writing top-level names to Axiom.egg-info/top_level.txt
> writing dependency_links to Axiom.egg-info/dependency_links.txt
> reading manifest file 'Axiom.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> writing manifest file 'Axiom.egg-info/SOURCES.txt'
> warning: build_py: byte-compiling is disabled, skipping.
> 
> running build_scripts
> touch debian/python-module-stampdir/python-axiom
> Adding cdbs dependencies to debian/python-axiom.substvars
> dh_installdirs -ppython-axiom \
>   
> cd . && python setup.py install 
> --root="/<>/debian/python-axiom/" --install-layout=deb 
> --no-compile -O0
> running install
> running build
> running build_py
> package init file 'twisted/plugins/__init__.py' not found (or not a regular 
> file)
> running egg_info
> writing requirements to Axiom.egg-info/requires.txt
> writing Axiom.egg-info/PKG-INFO
> writing top-level names to Axiom.egg-info/top_level.txt
> writing dependency_links to Axiom.egg-info/dependency_links.txt
> reading manifest file 'Axiom.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> writing manifest file 'Axiom.egg-info/SOURCES.txt'
> warning: build_py: byte-compiling is disabled, skipping.
> 
> running build_scripts
> running install_lib
> creating /<>/debian/python-axiom/usr
> creating /<>/debian/python-axiom/usr/lib
> creating /<>/debian/python-axiom/usr/lib/python2.7
> creating /<>/debian/python-axiom/usr/lib/python2.7/dist-packages
> creating 
> /<>/debian/python-axiom/usr/lib/python2.7/dist-packages/axiom
> copying build/lib.linux-x86_64-2.7/axiom/_pysqlite2.py -> 
> /<>/debian/python-axiom/usr/lib/python2.7/dist-packages/axiom
> copying build/lib.linux-x86_64-2.7/axiom/sequence.py -> 
> /<>/debian/python-axiom/usr/lib/python2.7/dist-packages/axiom
> creating 
> /<>/debian/python-axiom/usr/lib/python2.7/dist-packages/axiom/plugins
> copying build/lib.linux-x86_64-2.7/axiom/plugins/__init__.py -> 
> /<>/debian/python-axiom/usr/lib/python2.7/dist-packages/axiom/plugins
> copying build/lib.linux-x86_64-2.7/axiom/plugins/axiom_plugins.py -> 
> /<>/debian/python-axiom/usr/lib/python2.7/dist-packages/axiom/plugins
> copying build/lib.linux-x86_64-2.7/axiom/_version.py -> 
> /<>/debian/python-axiom/usr/lib/python2.7/dist-packages/axiom
> copying build/lib.linux-x86_64-2.7/axiom/iaxiom.py -> 
> /<>/debian/python-axiom/usr/lib/python2.7/dist-packages/axiom
> copying build/lib.linux-x86_64-2.7/axiom/batch.py -> 
> /<>/debian/python-axiom/usr/lib/python2.7/dist-packages/axiom
> copying build/lib.linux-x86_64-2.7/axiom/errors.py -> 
> /<>/debian/python-axiom/usr/lib/python2.7/dist-packages/axiom
> copying build/lib.linux-x86_64-2.7/axiom/substore.py -> 
> /<>/debian/python-axiom/usr/lib/python2.7/dist-packages/axiom
> creating 
> /<>/debian/python-axiom/usr/lib/python2.7/dist-packages/axiom/examples
> copying build/lib.linux-x86_64-2.7/axiom/examples/library.py -> 
> /<>/debian/python-axiom/usr/lib/python2.7/dist-packages/axiom/examples
> copying build/lib.linux-x86_64-2.7/axiom/examples/bucket.py -> 
> /<>/debian/python-axiom/usr/lib/python2.7/dist-packages/axiom/examples
> creating 
> /<>/debian/python-axiom/usr/lib/python2.7/dist-packages/axiom/test
> copying build/lib.linux-x86_64-2.7/axiom/test/oldobsolete.py -> 
> /<>/debian/python-axiom/usr/lib/python2.7/dist-packages/axiom/test
> copying build/lib.linux-x86_64-2.7/axiom/test/newobsolete.py -> 
> /<>/debian/python-axiom/usr/lib/python2.7/dist-packages/axiom/test
> copying build/lib.linux-x86_64-2.7/axiom/test/test_scheduler.py -> 
> /<>/debian/python-axiom/usr/lib/python2.7/dist-packages/axiom/test
> copying build/lib.linux-x86_64-2.7/axiom/test/test_batch.py -> 
> /<>/debian/python-axiom/usr/lib/python2.7/dist-packages/axiom/test
> copying build/lib.linux-x86_64-2.7/axiom/test/test_item.py -> 
> /<>/debian/python-axiom/usr/lib/python2.7/dist-packages/axiom/test
> copying build/lib.linux-x86_64-2.7/axiom/test/toonewapp.py -> 
> /<>/debian/python-axiom/usr/lib/python2.7/dist-packages/axiom/test
> copying build/lib.linux-x86_64-2.7/axiom/test/deleteswordapp.py -> 
> /<>/debian/python-

[Python-modules-team] Bug#830377: Reduce bug`s severity?

[Lucas Nussbaum]

On 03/09/16 at 22:37 +0200, Anton Gladky wrote:
> Hi all,
> 
> it looks like this test failure is the random case. I was not
> able to reproduce it building it 2 times on barriere.debian.org.
> 
> I propose to reduce the bug severity to "normal".

I gave it another try, and it fails reproducibly for me.

Interestingly, it fails with:
python2.7 -m unittest discover -v -f

but doesn't fail with:
python2.7 -m unittest discover -v -f -p "test_regression*"

So it might be a breakage elsewhere in the test suite causing this
particular test to fail.

I don't think that this should be downgraded before it's understood why
it fails reproducibly for me but doesn't for you, but of course it's up
to the release team to decide.

Lucas

___
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#835722: python-pgmagick: FTBFS: ./src/_Image.cpp:68:116: error: no matching function for call to 'boost::python::class_::def(const char [18],

[Lucas Nussbaum]

Source: python-pgmagick
Version: 0.6.2-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall 
> -Wstrict-prototypes -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 -g 
> -fdebug-prefix-map=/build/python2.7-oH9M6v/python2.7-2.7.12=. 
> -fstack-protector-strong -Wformat -Werror=format-security -fPIC 
> -I/usr/include/python2.7 -I/usr/include/GraphicsMagick/ 
> -I/usr/include/python2.7 -c ./src/_Image.cpp -o 
> build/temp.linux-x86_64-2.7/./src/_Image.o 
> -DPGMAGICK_LIB_GRAPHICSMAGICK_1_3_x -D_LIBRARY_VERSION="1.4"
> cc1plus: warning: command line option '-Wstrict-prototypes' is valid for 
> C/ObjC but not for C++
> ./src/_Image.cpp: In function 'void __Image()':
> ./src/_Image.cpp:68:116: error: no matching function for call to 
> 'boost::python::class_::def(const char [18],  overloaded function type>, 
> {anonymous}::Magick_Image_adaptiveThreshold_overloads_2_3)'
>  .def("adaptiveThreshold", &Magick::Image::adaptiveThreshold, 
> Magick_Image_adaptiveThreshold_overloads_2_3())
>   
>   ^
> In file included from /usr/include/boost/python.hpp:18:0,
>  from ./src/_Image.cpp:1:
> /usr/include/boost/python/class.hpp:223:11: note: candidate: template Derived> boost::python::class_::self& boost::python::class_ X1, X2, X3>::def(const boost::python::def_visitor&) [with Derived = 
> Derived; W = Magick::Image; X1 = boost::python::detail::not_specified; X2 = 
> boost::python::detail::not_specified; X3 = 
> boost::python::detail::not_specified]
>  self& def(def_visitor const& visitor)
>^~~
> /usr/include/boost/python/class.hpp:223:11: note:   template argument 
> deduction/substitution failed:
> ./src/_Image.cpp:68:116: note:   mismatched types 'const 
> boost::python::def_visitor' and 'const char [18]'
>  .def("adaptiveThreshold", &Magick::Image::adaptiveThreshold, 
> Magick_Image_adaptiveThreshold_overloads_2_3())
>   
>   ^
> In file included from /usr/include/boost/python.hpp:18:0,
>  from ./src/_Image.cpp:1:
> /usr/include/boost/python/class.hpp:233:11: note: candidate: template F> boost::python::class_::self& boost::python::class_ X2, X3>::def(const char*, F) [with F = F; W = Magick::Image; X1 = 
> boost::python::detail::not_specified; X2 = 
> boost::python::detail::not_specified; X3 = 
> boost::python::detail::not_specified]
>  self& def(char const* name, F f)
>^~~
> /usr/include/boost/python/class.hpp:233:11: note:   template argument 
> deduction/substitution failed:
> ./src/_Image.cpp:68:116: note:   candidate expects 2 arguments, 3 provided
>  .def("adaptiveThreshold", &Magick::Image::adaptiveThreshold, 
> Magick_Image_adaptiveThreshold_overloads_2_3())
>   
>   ^
> In file included from /usr/include/boost/python.hpp:18:0,
>  from ./src/_Image.cpp:1:
> /usr/include/boost/python/class.hpp:242:11: note: candidate: template A1, class A2> boost::python::class_::self& 
> boost::python::class_::def(const char*, A1, const A2&) [with 
> A1 = A1; A2 = A2; W = Magick::Image; X1 = 
> boost::python::detail::not_specified; X2 = 
> boost::python::detail::not_specified; X3 = 
> boost::python::detail::not_specified]
>  self& def(char const* name, A1 a1, A2 const& a2)
>^~~
> /usr/include/boost/python/class.hpp:242:11: note:   template argument 
> deduction/substitution failed:
> ./src/_Image.cpp:68:116: note:   couldn't deduce template parameter 'A1'
>  .def("adaptiveThreshold", &Magick::Image::adaptiveThreshold, 
> Magick_Image_adaptiveThreshold_overloads_2_3())
>   
>   ^
> In file included from /usr/include/boost/python.hpp:18:0,
>  from ./src/_Image.cpp:1:
> /usr/include/boost/python/class.hpp:249:11: note: candidate: template Fn, class A1, class A2> boost::python::class_::self& 
> boost::python::class_::def(const char*, Fn, const A1&, const 
> A2&) [with Fn = Fn; A1 = A1; A2 = A2; W = Magick::Image; X1 = 
> boost::python::detail::not_specified; X2 = 
> boost::python::detail::not_specified; X3 = 
> boost::python::detail::not_specified]
>  self& def(char const* name, Fn fn, A1 const& a1, A2 const& a2)
>^~~
> /usr/include/boost/python/class.hpp:249:11: note:   template argument 
> deduction/substitution failed:
> ./src/_Image.cpp:68:116: note:   candidate expects 4 a

[Python-modules-team] Bug#835694: python-protobuf.socketrpc: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13

[Lucas Nussbaum]

Source: python-protobuf.socketrpc
Version: 1.3.2-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>  debian/rules build
> dh build --with python2 --buildsystem=pybuild
>dh_testdir -O--buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:184: python2.7 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:184: /usr/bin/python setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_2.7/build/protobuf
> copying src/protobuf/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/protobuf
> creating /<>/.pybuild/pythonX.Y_2.7/build/protobuf/socketrpc
> copying src/protobuf/socketrpc/rpc_pb2.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/protobuf/socketrpc
> copying src/protobuf/socketrpc/controller.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/protobuf/socketrpc
> copying src/protobuf/socketrpc/error.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/protobuf/socketrpc
> copying src/protobuf/socketrpc/channel.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/protobuf/socketrpc
> copying src/protobuf/socketrpc/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/protobuf/socketrpc
> copying src/protobuf/socketrpc/server.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/protobuf/socketrpc
> copying src/protobuf/socketrpc/service.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/protobuf/socketrpc
> copying src/protobuf/socketrpc/logger.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/protobuf/socketrpc
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:184: python2.7 setup.py test 
> running test
> running egg_info
> creating src/protobuf.socketrpc.egg-info
> writing src/protobuf.socketrpc.egg-info/PKG-INFO
> writing top-level names to src/protobuf.socketrpc.egg-info/top_level.txt
> writing dependency_links to 
> src/protobuf.socketrpc.egg-info/dependency_links.txt
> writing manifest file 'src/protobuf.socketrpc.egg-info/SOURCES.txt'
> reading manifest file 'src/protobuf.socketrpc.egg-info/SOURCES.txt'
> writing manifest file 'src/protobuf.socketrpc.egg-info/SOURCES.txt'
> running build_ext
> Traceback (most recent call last):
>   File "setup.py", line 53, in 
> test_suite='protobuf.socketrpc.tests',
>   File "/usr/lib/python2.7/distutils/core.py", line 151, in setup
> dist.run_commands()
>   File "/usr/lib/python2.7/distutils/dist.py", line 953, in run_commands
> self.run_command(cmd)
>   File "/usr/lib/python2.7/distutils/dist.py", line 972, in run_command
> cmd_obj.run()
>   File "/usr/lib/python2.7/dist-packages/setuptools/command/test.py", line 
> 172, in run
> self.run_tests()
>   File "/usr/lib/python2.7/dist-packages/setuptools/command/test.py", line 
> 193, in run_tests
> testRunner=self._resolve_as_ep(self.test_runner),
>   File "/usr/lib/python2.7/unittest/main.py", line 94, in __init__
> self.parseArgs(argv)
>   File "/usr/lib/python2.7/unittest/main.py", line 149, in parseArgs
> self.createTests()
>   File "/usr/lib/python2.7/unittest/main.py", line 158, in createTests
> self.module)
>   File "/usr/lib/python2.7/unittest/loader.py", line 130, in 
> loadTestsFromNames
> suites = [self.loadTestsFromName(name, module) for name in names]
>   File "/usr/lib/python2.7/unittest/loader.py", line 103, in loadTestsFromName
> return self.loadTestsFromModule(obj)
>   File "/usr/lib/python2.7/dist-packages/setuptools/command/test.py", line 
> 40, in loadTestsFromModule
> tests.append(self.loadTestsFromName(submodule))
>   File "/usr/lib/python2.7/unittest/loader.py", line 91, in loadTestsFromName
> module = __import__('.'.join(parts_copy))
>   File "/<>/src/protobuf/socketrpc/tests/service_test.py", line 
> 45, in 
> import fake
>   File "/<>/src/protobuf/socketrpc/tests/fake.py", line 39, in 
> 
> import test_pb2
>   File "/<>/src/protobuf/socketrpc/tests/test_pb2.py", line 15, 
> in 
> 
> serialized_pb='\n\ntest.proto\x12\x12protobuf.socketrpc\"\x1b\n\x07Request\x12\x10\n\x08str_data\x18\x01
>  \x02(\t\".\n\x08Response\x12\x10\n\x08str_data\x18\x01 
> \x02(\t\x12\x10\n\x08int_data\x18\x02 
> \x01(\x05\x32V\n\x0bTestService\x12G\n\nTestMethod\x12\x1b.protobuf.socketrpc.Request\x1a\x1c.protobuf.socketrpc.Response')
>   File "/usr/lib/python2.7/dist-packages/google/protobuf/descriptor.py", line 
> 827, in __new__
> return _message.default_pool.AddSerializedFile(serialized_pb)
> TypeError: Couldn't build proto file into descriptor pool!
> Invalid proto descriptor for file "test.proto":
>   protobuf.socketrpc.Request: "protobuf.socketrpc.Request" is already defined 
> in file "rpc.proto".
>   protobuf.socketrpc.Response: "protobuf.socketrpc.Response" is already 
> defined in file "rpc.proto".
>   protobuf.socketrpc.TestService.TestMetho

[Python-modules-team] Bug#835682: python-socketpool: FTBFS: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 3249: ordinal not in range(128)

[Lucas Nussbaum]

Source: python-socketpool
Version: 0.5.3-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --with python2,python3 --buildsystem=pybuild
>dh_testdir -O--buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:184: python2.7 setup.py clean 
> running clean
> removing '/<>/.pybuild/pythonX.Y_2.7/build' (and everything 
> under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-2.7' does not exist -- can't clean it
> I: pybuild base:184: python3.5 setup.py clean 
> Traceback (most recent call last):
>   File "setup.py", line 26, in 
> long_description = f.read()
>   File "/usr/lib/python3.5/encodings/ascii.py", line 26, in decode
> return codecs.ascii_decode(input, self.errors)[0]
> UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 3249: 
> ordinal not in range(128)
> E: pybuild pybuild:276: clean: plugin distutils failed with: exit code=1: 
> python3.5 setup.py clean 
> dh_auto_clean: pybuild --clean -i python{version} -p 3.5 returned exit code 13
> debian/rules:8: recipe for target 'clean' failed
> make: *** [clean] Error 25

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/08/28/python-socketpool_0.5.3-2_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#832854: python-restless: FTBFS: RuntimeError: Working outside of request context.

[Lucas Nussbaum]

Source: python-restless
Version: 2.0.1-6
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160728 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/«PKGBUILDDIR»'
> dh_auto_build
> I: pybuild base:184: /usr/bin/python setup.py build 
> running build
> running build_py
> creating /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/restless
> copying restless/it.py -> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/restless
> copying restless/data.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/restless
> copying restless/preparers.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/restless
> copying restless/dj.py -> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/restless
> copying restless/constants.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/restless
> copying restless/pyr.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/restless
> copying restless/utils.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/restless
> copying restless/resources.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/restless
> copying restless/exceptions.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/restless
> copying restless/__init__.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/restless
> copying restless/fl.py -> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/restless
> copying restless/tnd.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/restless
> copying restless/serializers.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/restless
> I: pybuild base:184: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/restless
> copying restless/it.py -> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/restless
> copying restless/data.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/restless
> copying restless/preparers.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/restless
> copying restless/dj.py -> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/restless
> copying restless/constants.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/restless
> copying restless/pyr.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/restless
> copying restless/utils.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/restless
> copying restless/resources.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/restless
> copying restless/exceptions.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/restless
> copying restless/__init__.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/restless
> copying restless/fl.py -> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/restless
> copying restless/tnd.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/restless
> copying restless/serializers.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/restless
> PYTHONPATH=. http_proxy='127.0.0.1:9' sphinx-build -N -bhtml docs/ build/html
> Running Sphinx v1.4.5
> making output directory...
> loading pickled environment... not yet created
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 21 source files that are out of date
> updating environment: 21 added, 0 changed, 0 removed
> reading sources... [  4%] contributing
> reading sources... [  9%] cookbook
> reading sources... [ 14%] extending
> reading sources... [ 19%] index
> reading sources... [ 23%] philosophy
> reading sources... [ 28%] reference/constants
> reading sources... [ 33%] reference/data
> reading sources... [ 38%] reference/exceptions
> reading sources... [ 42%] reference/preparers
> reading sources... [ 47%] reference/resources
> 
> Exception occurred:
>   File "/usr/lib/python2.7/dist-packages/flask/globals.py", line 37, in 
> _lookup_req_object
> raise RuntimeError(_request_ctx_err_msg)
> RuntimeError: Working outside of request context.
> 
> This typically means that you attempted to use functionality that needed
> an active HTTP request.  Consult the documentation on testing for
> information about how to avoid this problem.
> The full traceback has been saved in /tmp/sphinx-err-mn4x9G.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!
> make[1]: *** [override_dh_auto_build] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/28/python-restless_2.0.1-6_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failur

[Python-modules-team] Bug#830377: python-traits: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13

[Lucas Nussbaum]

Source: python-traits
Version: 4.5.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160707 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>  debian/rules build
> dh build --with python2,python3,sphinxdoc --buildsystem=pybuild
>dh_testdir -O--buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
>   pybuild --configure -i python{version} -p 2.7
> I: pybuild base:184: python2.7 setup.py config 
> running config
>   pybuild --configure -i python{version} -p 3.5
> I: pybuild base:184: python3.5 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
>   pybuild --build -i python{version} -p 2.7
> I: pybuild base:184: /usr/bin/python setup.py build 
> running build
> running build_py
> creating /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/traits
> copying traits/trait_notifiers.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/traits
> copying traits/_py2to3.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/traits
> copying traits/trait_types.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/traits
> copying traits/traits.py -> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/traits
> copying traits/has_traits.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/traits
> copying traits/category.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/traits
> copying traits/trait_value.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/traits
> copying traits/api.py -> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/traits
> copying traits/traits_listener.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/traits
> copying traits/__init__.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/traits
> copying traits/ustr_trait.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/traits
> copying traits/interface_checker.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/traits
> copying traits/trait_base.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/traits
> copying traits/trait_numeric.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/traits
> copying traits/trait_handlers.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/traits
> copying traits/adapter.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/traits
> copying traits/has_dynamic_views.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/traits
> copying traits/trait_errors.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/traits
> creating /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/traits/util
> copying traits/util/resource.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/traits/util
> copying traits/util/trait_documenter.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/traits/util
> copying traits/util/camel_case.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/traits/util
> copying traits/util/toposort.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/traits/util
> copying traits/util/async_trait_wait.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/traits/util
> copying traits/util/api.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/traits/util
> copying traits/util/__init__.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/traits/util
> copying traits/util/home_directory.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/traits/util
> copying traits/util/deprecated.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/traits/util
> copying traits/util/import_symbol.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/traits/util
> copying traits/util/clean_strings.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/traits/util
> creating /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/traits/tests
> copying traits/tests/test_interfaces.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/traits/tests
> copying traits/tests/test_traits.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/traits/tests
> copying traits/tests/test_interfaces_with_implements.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/traits/tests
> copying traits/tests/test_dict.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/traits/tests
> copying traits/tests/test_target.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/traits/tests
> copying traits/tests/test_dynamic_notifiers.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/traits/tests
> copying traits/tests/test_listeners.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/traits/tests
> copying traits/tests/test_rich_compare.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/traits/tests
> copying traits/tests/test_trait_types.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/traits/tests
> copying traits/tests/test_dynamic_trait_definition.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/traits/tests
> copying traits/tests/test_property_delete.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/traits

[Python-modules-team] Bug#830364: pycairo: FTBFS: /bin/sh: 3: pythonpython2.7-dbg: not found

[Lucas Nussbaum]

Source: pycairo
Version: 1.8.8-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160707 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>  debian/rules build
> dh_listpackages: -s/--same-arch is deprecated; please use -a/--arch instead
> pyversions: missing X(S)-Python-Version in control file, fall back to 
> debian/pyversions
> pyversions: missing debian/pyversions file, fall back to supported versions
> test -x debian/rules
> mkdir -p "."
> CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85
> CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85
> mkdir -p debian/python-module-stampdir
> set -e;   mv ./config.guess ./config.guess.cdbs-orig; cp --remove-destination 
> /usr/share/misc/config.guess ./config.guess;
> set -e;   mv ./config.sub ./config.sub.cdbs-orig; cp --remove-destination 
> /usr/share/misc/config.sub ./config.sub;
> set -e; cd . && python2.7 setup.py build 
> --build-base="/«PKGBUILDDIR»/./build";
> cairo >= 1.8.8 detected
> creating pycairo.pc
> creating src/config.h
> running build
> running build_py
> creating /«PKGBUILDDIR»/build
> creating /«PKGBUILDDIR»/build/lib.linux-x86_64-2.7
> creating /«PKGBUILDDIR»/build/lib.linux-x86_64-2.7/cairo
> copying src/__init__.py -> /«PKGBUILDDIR»/./build/lib.linux-x86_64-2.7/cairo
> running build_ext
> building 'cairo._cairo' extension
> creating /«PKGBUILDDIR»/build/temp.linux-x86_64-2.7
> creating /«PKGBUILDDIR»/build/temp.linux-x86_64-2.7/src
> x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall 
> -Wstrict-prototypes -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 -g 
> -fstack-protector-strong -Wformat -Werror=format-security -fPIC 
> -I/usr/include/cairo -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 
> -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/python2.7 -c 
> src/cairomodule.c -o 
> /«PKGBUILDDIR»/./build/temp.linux-x86_64-2.7/src/cairomodule.o
> x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall 
> -Wstrict-prototypes -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 -g 
> -fstack-protector-strong -Wformat -Werror=format-security -fPIC 
> -I/usr/include/cairo -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 
> -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/python2.7 -c 
> src/context.c -o /«PKGBUILDDIR»/./build/temp.linux-x86_64-2.7/src/context.o
> x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall 
> -Wstrict-prototypes -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 -g 
> -fstack-protector-strong -Wformat -Werror=format-security -fPIC 
> -I/usr/include/cairo -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 
> -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/python2.7 -c 
> src/font.c -o /«PKGBUILDDIR»/./build/temp.linux-x86_64-2.7/src/font.o
> x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall 
> -Wstrict-prototypes -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 -g 
> -fstack-protector-strong -Wformat -Werror=format-security -fPIC 
> -I/usr/include/cairo -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 
> -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/python2.7 -c 
> src/matrix.c -o /«PKGBUILDDIR»/./build/temp.linux-x86_64-2.7/src/matrix.o
> x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall 
> -Wstrict-prototypes -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 -g 
> -fstack-protector-strong -Wformat -Werror=format-security -fPIC 
> -I/usr/include/cairo -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 
> -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/python2.7 -c 
> src/path.c -o /«PKGBUILDDIR»/./build/temp.linux-x86_64-2.7/src/path.o
> x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall 
> -Wstrict-prototypes -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 -g 
> -fstack-protector-strong -Wformat -Werror=format-security -fPIC 
> -I/usr/include/cairo -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 
> -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/python2.7 -c 
> src/pattern.c -o /«PKGBUILDDIR»/./build/temp.linux-x86_64-2.7/src/pattern.o
> x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall 
> -Wstrict-prototypes -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 -g 
> -fstack-protector-strong -Wformat -Werror=format-security -fPIC 
> -I/usr/include/cairo -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 
> -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/python2.7 -c 
> src/surface.c -o /«PKGBUILDDIR»/./build/temp.linux-x86_64-2.7/src/surface.

[Python-modules-team] Bug#830350: templayer: FTBFS: chmod: cannot access 'debian/python-templayer/usr/lib/python*/site-packages/templayer.py': No such file or directory

[Lucas Nussbaum]

Source: templayer
Version: 1.5.1-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160707 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>  fakeroot debian/rules binary
> dh_listpackages: -s/--same-arch is deprecated; please use -a/--arch instead
> pyversions: missing X(S)-Python-Version in control file, fall back to 
> debian/pyversions
> pyversions: missing debian/pyversions file, fall back to supported versions
> test -x debian/rules
> dh_testroot
> dh_clean -k 
> dh_clean: dh_clean -k is deprecated; use dh_prep instead
> dh_installdirs -A 
> mkdir -p "."
> mkdir -p debian/python-module-stampdir
> cd . && python2 setup.py build --build-base="/«PKGBUILDDIR»/./build"
> running build
> running build_py
> touch debian/python-module-stampdir/python-templayer
> Adding cdbs dependencies to debian/python-templayer.substvars
> dh_installdirs -ppython-templayer \
>   
> cd . && python2 setup.py install 
> --root="/«PKGBUILDDIR»/debian/python-templayer/" --install-layout=deb 
> --no-compile -O0
> running install
> running build
> running build_py
> running install_lib
> creating /«PKGBUILDDIR»/debian/python-templayer/usr
> creating /«PKGBUILDDIR»/debian/python-templayer/usr/lib
> creating /«PKGBUILDDIR»/debian/python-templayer/usr/lib/python2.7
> creating 
> /«PKGBUILDDIR»/debian/python-templayer/usr/lib/python2.7/dist-packages
> copying build/lib.linux-x86_64-2.7/templayer.py -> 
> /«PKGBUILDDIR»/debian/python-templayer/usr/lib/python2.7/dist-packages
> running install_egg_info
> Writing 
> /«PKGBUILDDIR»/debian/python-templayer/usr/lib/python2.7/dist-packages/templayer-1.5.1.egg-info
> chmod a+x debian/python-templayer/usr/lib/python*/site-packages/templayer.py
> chmod: cannot access 
> 'debian/python-templayer/usr/lib/python*/site-packages/templayer.py': No such 
> file or directory
> make: *** [install/python-templayer] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/07/templayer_1.5.1-2_unstable_reb.normal.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#830326: django-uwsgi: FTBFS: ImportError: No module named 'sphinx_rtd_theme'

[Lucas Nussbaum]

Source: django-uwsgi
Version: 0.1.3-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160707 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/«PKGBUILDDIR»'
> dh_auto_build
> I: pybuild base:184: /usr/bin/python setup.py build 
> running build
> running build_py
> creating /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/django_uwsgi
> copying django_uwsgi/task.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/django_uwsgi
> copying django_uwsgi/apps.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/django_uwsgi
> copying django_uwsgi/decorators.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/django_uwsgi
> copying django_uwsgi/wagtail_hooks.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/django_uwsgi
> copying django_uwsgi/stats.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/django_uwsgi
> copying django_uwsgi/cache.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/django_uwsgi
> copying django_uwsgi/urls.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/django_uwsgi
> copying django_uwsgi/mail.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/django_uwsgi
> copying django_uwsgi/template.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/django_uwsgi
> copying django_uwsgi/views.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/django_uwsgi
> copying django_uwsgi/__init__.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/django_uwsgi
> copying django_uwsgi/panels.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/django_uwsgi
> creating /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/django_uwsgi/management
> copying django_uwsgi/management/__init__.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/django_uwsgi/management
> creating /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/django_uwsgi/emperor
> copying django_uwsgi/emperor/apps.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/django_uwsgi/emperor
> copying django_uwsgi/emperor/admin.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/django_uwsgi/emperor
> copying django_uwsgi/emperor/models.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/django_uwsgi/emperor
> copying django_uwsgi/emperor/__init__.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/django_uwsgi/emperor
> creating 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/django_uwsgi/management/commands
> copying django_uwsgi/management/commands/runuwsgi.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/django_uwsgi/management/commands
> copying django_uwsgi/management/commands/__init__.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/django_uwsgi/management/commands
> running egg_info
> writing requirements to django_uwsgi.egg-info/requires.txt
> writing django_uwsgi.egg-info/PKG-INFO
> writing top-level names to django_uwsgi.egg-info/top_level.txt
> writing dependency_links to django_uwsgi.egg-info/dependency_links.txt
> reading manifest file 'django_uwsgi.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no previously-included files matching '__pycache__' found under 
> directory '*'
> writing manifest file 'django_uwsgi.egg-info/SOURCES.txt'
> creating /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/django_uwsgi/templates
> creating 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/django_uwsgi/templates/uwsgi
> copying django_uwsgi/templates/uwsgi/panel.html -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/django_uwsgi/templates/uwsgi
> copying django_uwsgi/templates/uwsgi/uwsgi.html -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/django_uwsgi/templates/uwsgi
> copying django_uwsgi/templates/uwsgi/wagtail_dashboard_item.html -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/django_uwsgi/templates/uwsgi
> copying django_uwsgi/templates/uwsgi/wagtail_uwsgi.html -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/django_uwsgi/templates/uwsgi
> I: pybuild base:184: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/django_uwsgi
> copying django_uwsgi/task.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/django_uwsgi
> copying django_uwsgi/apps.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/django_uwsgi
> copying django_uwsgi/decorators.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/django_uwsgi
> copying django_uwsgi/wagtail_hooks.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/django_uwsgi
> copying django_uwsgi/stats.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/django_uwsgi
> copying django_uwsgi/cache.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/django_uwsgi
> copying django_uwsgi/urls.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/django_uwsgi
> copying django_uwsgi/mail.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/django_uwsgi
> copying django_uwsgi/template.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/django_uwsgi

[Python-modules-team] Bug#768752: python-oerplib: FTBFS in jessie: dh_auto_clean: unable to load build system class 'pybuild'

[Lucas Nussbaum]

Source: python-oerplib
Version: 0.8.3-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141108 qa-ftbfs
Justification: FTBFS in jessie on amd64

Hi,

During a rebuild of all packages in jessie (in a jessie chroot, not a
sid chroot), your package failed to build on amd64.

Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --with python2,sphinxdoc --buildsystem=pybuild
>dh_testdir -O--buildsystem=pybuild
>debian/rules override_dh_auto_clean
> make[1]: Entering directory '/«PKGBUILDDIR»'
> rm -rf doc.debian
> dh_auto_clean
> dh_auto_clean: unable to load build system class 'pybuild': Can't locate 
> Debian/Debhelper/Buildsystem/pybuild.pm in @INC (you may need to install the 
> Debian::Debhelper::Buildsystem::pybuild module) (@INC contains: /etc/perl 
> /usr/local/lib/x86_64-linux-gnu/perl/5.20.1 /usr/local/share/perl/5.20.1 
> /usr/lib/x86_64-linux-gnu/perl5/5.20 /usr/share/perl5 
> /usr/lib/x86_64-linux-gnu/perl/5.20 /usr/share/perl/5.20 
> /usr/local/lib/site_perl .) at (eval 3) line 2.
> BEGIN failed--compilation aborted at (eval 3) line 2.
> 
> make[1]: *** [override_dh_auto_clean] Error 2

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/11/08/python-oerplib_0.8.3-2_jessie.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#768743: python-gear: FTBFS in jessie: build-dependency not installable: python-statsd (>= 1.0.0)

[Lucas Nussbaum]

Source: python-gear
Version: 0.5.4-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141108 qa-ftbfs
Justification: FTBFS in jessie on amd64

Hi,

During a rebuild of all packages in jessie (in a jessie chroot, not a
sid chroot), your package failed to build on amd64.

Relevant part (hopefully):
> ┌──┐
> │ Install python-gear build dependencies (apt-based resolver) 
>  │
> └──┘
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> 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:
>  sbuild-build-depends-python-gear-dummy : Depends: python-statsd (>= 1.0.0) 
> but it is not installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/11/08/python-gear_0.5.4-1_jessie.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#759981: stdeb: FTBFS: help2man: can't get `--help' info from /«PKGBUILDDIR»/debian/python-stdeb/usr/bin/pypi-install

[Lucas Nussbaum]

Source: stdeb
Version: 0.8.2-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140830 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/«PKGBUILDDIR»'
> PYTHONPATH=/«PKGBUILDDIR» help2man -N --version-string=0.8.2 -o py2dsc.1 -n 
> 'creates Debian source package from Python package' 
> /«PKGBUILDDIR»/debian/python-stdeb/usr/bin/py2dsc
> PYTHONPATH=/«PKGBUILDDIR» help2man -N --version-string=0.8.2 -o py2dsc-deb.1 
> -n 'dpkg-buildpackage wrapper that integrates with py2dsc and build binary 
> package' /«PKGBUILDDIR»/debian/python-stdeb/usr/bin/py2dsc-deb
> PYTHONPATH=/«PKGBUILDDIR» help2man -N --version-string=0.8.2 -o 
> pypi-install.1 -n 'downloads Python package from PyPI, creates Debian package 
> and then installs it' /«PKGBUILDDIR»/debian/python-stdeb/usr/bin/pypi-install
> help2man: can't get `--help' info from 
> /«PKGBUILDDIR»/debian/python-stdeb/usr/bin/pypi-install
> Try `--no-discard-stderr' if option outputs to stderr
> make[1]: *** [pypi-install.1] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/08/30/stdeb_0.8.2-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures. The build
was done with DEB_BUILD_OPTIONS="parallel=4", so if your packaging tries
to support this, it might be a good idea to explore whether this might
be the cause of the failure.

___
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#759908: python-graph: FTBFS: tests segfault

[Lucas Nussbaum]

Source: python-graph
Version: 1.8.2-4
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140830 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[2]: Entering directory '/«PKGBUILDDIR»'
> export PYTHONPATH=../core/build/lib.linux-x86_64-2.7 && cd "tests/" && 
> python2.7 testrunner.py
> No handlers could be found for logger "__main__"
> test_accessibility_hypergraph (unittests-accessibility.test_accessibility) 
> ... ok
> test_accessibility_in_digraph (unittests-accessibility.test_accessibility) 
> ... ok
> test_accessibility_in_graph (unittests-accessibility.test_accessibility) ... 
> ok
> test_accessibility_on_very_deep_graph 
> (unittests-accessibility.test_accessibility) ... ok
> test_connected_components_hypergraph 
> (unittests-accessibility.test_accessibility) ... ok
> test_connected_components_in_graph 
> (unittests-accessibility.test_accessibility) ... ok
> test_connected_components_on_very_deep_graph 
> (unittests-accessibility.test_accessibility) ... ok
> test_cut_edges_in_graph (unittests-accessibility.test_accessibility) ... ok
> test_cut_edges_in_hypergraph (unittests-accessibility.test_accessibility) ... 
> ok
> test_cut_edges_on_very_deep_graph 
> (unittests-accessibility.test_accessibility) ... ok
> test_cut_nodes_in_graph (unittests-accessibility.test_accessibility) ... ok
> test_cut_nodes_in_hypergraph (unittests-accessibility.test_accessibility) ... 
> ok
> test_cut_nodes_on_very_deep_graph 
> (unittests-accessibility.test_accessibility) ... ok
> test_mutual_accessibility_in_digraph 
> (unittests-accessibility.test_accessibility) ... ok
> test_mutual_accessibility_in_graph 
> (unittests-accessibility.test_accessibility) ... ok
> test_mutual_accessibility_on_very_deep_graph 
> (unittests-accessibility.test_accessibility) ... ok
> test_critical_path 
> (unittests-critical.test_critical_path_and_transitive_edges) ... ok
> test_critical_path_with_cycle 
> (unittests-critical.test_critical_path_and_transitive_edges) ... ok
> test_empty_intersection 
> (unittests-critical.test_critical_path_and_transitive_edges) ... ok
> test_partial_intersection 
> (unittests-critical.test_critical_path_and_transitive_edges) ... ok
> test_transitivity 
> (unittests-critical.test_critical_path_and_transitive_edges) ... ok
> test_transitivity_with_cycle 
> (unittests-critical.test_critical_path_and_transitive_edges) ... ok
> test_find_cycle_on_digraph (unittests-cycles.test_find_cycle) ... ok
> test_find_cycle_on_digraph_without_cycles (unittests-cycles.test_find_cycle) 
> ... ok
> test_find_cycle_on_graph (unittests-cycles.test_find_cycle) ... ok
> test_find_cycle_on_graph_withot_cycles (unittests-cycles.test_find_cycle) ... 
> ok
> test_find_cycle_on_very_deep_graph (unittests-cycles.test_find_cycle) ... 
> Segmentation fault
> make[2]: *** [test] Error 139

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/08/30/python-graph_1.8.2-4_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures. The build
was done with DEB_BUILD_OPTIONS="parallel=4", so if your packaging tries
to support this, it might be a good idea to explore whether this might
be the cause of the failure.

___
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#759858: python-igraph: FTBFS: src/graphobject.c:3734:9: error: too few arguments to function 'igraph_closeness'

[Lucas Nussbaum]

Source: python-igraph
Version: 0.6.5-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140830 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall 
> -Wstrict-prototypes -fno-strict-aliasing -D_FORTIFY_SOURCE=2 -g 
> -fstack-protector-strong -Wformat -Werror=format-security -fPIC 
> -I/usr/include/igraph -I/usr/local/include/igraph -I../../build/include 
> -I../../include -I/usr/local/include -I/usr/include -I/usr/include/python2.7 
> -c src/graphobject.c -o build/temp.linux-x86_64-2.7/src/graphobject.o
> src/graphobject.c: In function 'igraphmodule_Graph_closeness':
> src/graphobject.c:3734:9: error: too few arguments to function 
> 'igraph_closeness'
>  if (igraph_closeness(&self->g, &res, vs, mode, weights)) {
>  ^
> In file included from /usr/include/igraph/igraph.h:60:0,
>  from src/graphobject.h:27,
>  from src/arpackobject.h:28,
>  from src/graphobject.c:24:
> /usr/include/igraph/igraph_centrality.h:49:5: note: declared here
>  int igraph_closeness(const igraph_t *graph, igraph_vector_t *res, 
>  ^
> src/graphobject.c:3747:9: error: too few arguments to function 
> 'igraph_closeness_estimate'
>  if (igraph_closeness_estimate(&self->g, &res, vs, mode,
>  ^
> In file included from /usr/include/igraph/igraph.h:60:0,
>  from src/graphobject.h:27,
>  from src/arpackobject.h:28,
>  from src/graphobject.c:24:
> /usr/include/igraph/igraph_centrality.h:52:5: note: declared here
>  int igraph_closeness_estimate(const igraph_t *graph, igraph_vector_t *res, 
>  ^
> src/graphobject.c: In function 'igraphmodule_Graph_get_shortest_paths':
> src/graphobject.c:4317:7: error: too few arguments to function 
> 'igraph_get_shortest_paths_dijkstra'
>if (igraph_get_shortest_paths_dijkstra(&self->g, use_edges ? 0 : ptrvec,
>^
> In file included from /usr/include/igraph/igraph.h:61:0,
>  from src/graphobject.h:27,
>  from src/arpackobject.h:28,
>  from src/graphobject.c:24:
> /usr/include/igraph/igraph_paths.h:92:5: note: declared here
>  int igraph_get_shortest_paths_dijkstra(const igraph_t *graph,
>  ^
> src/graphobject.c: In function 'igraphmodule_Graph_personalized_pagerank':
> src/graphobject.c:4694:14: error: incompatible type for argument 2 of 
> 'igraph_personalized_pagerank_vs'
>  retval = igraph_personalized_pagerank_vs(&self->g, &res, 0, vs, 
> PyObject_IsTrue(directed),
>   ^
> In file included from /usr/include/igraph/igraph.h:60:0,
>  from src/graphobject.h:27,
>  from src/arpackobject.h:28,
>  from src/graphobject.c:24:
> /usr/include/igraph/igraph_centrality.h:123:5: note: expected 
> 'igraph_pagerank_algo_t' but argument is of type 'struct igraph_vector_t *'
>  int igraph_personalized_pagerank_vs(const igraph_t *graph, 
>  ^
> src/graphobject.c:4694:14: error: incompatible type for argument 4 of 
> 'igraph_personalized_pagerank_vs'
>  retval = igraph_personalized_pagerank_vs(&self->g, &res, 0, vs, 
> PyObject_IsTrue(directed),
>   ^
> In file included from /usr/include/igraph/igraph.h:60:0,
>  from src/graphobject.h:27,
>  from src/arpackobject.h:28,
>  from src/graphobject.c:24:
> /usr/include/igraph/igraph_centrality.h:123:5: note: expected 'igraph_real_t 
> *' but argument is of type 'igraph_vs_t'
>  int igraph_personalized_pagerank_vs(const igraph_t *graph, 
>  ^
> src/graphobject.c:4694:14: error: incompatible type for argument 5 of 
> 'igraph_personalized_pagerank_vs'
>  retval = igraph_personalized_pagerank_vs(&self->g, &res, 0, vs, 
> PyObject_IsTrue(directed),
>   ^
> In file included from /usr/include/igraph/igraph.h:60:0,
>  from src/graphobject.h:27,
>  from src/arpackobject.h:28,
>  from src/graphobject.c:24:
> /usr/include/igraph/igraph_centrality.h:123:5: note: expected 'igraph_vs_t' 
> but argument is of type 'int'
>  int igraph_personalized_pagerank_vs(const igraph_t *graph, 
>  ^
> src/graphobject.c:4694:14: error: incompatible type for argument 7 of 
> 'igraph_personalized_pagerank_vs'
>  retval = igraph_personalized_pagerank_vs(&self->g, &res, 0, vs, 
> PyObject_IsTrue(directed),
>   ^
> In file included from /usr/include/igraph/igraph.h:60:0,
>  from src/graphobject.h:27,
>  from src/arpackobject.h:28,
>  from src/graphobject.c:24:
> /usr/include/igraph/igraph_centrality.h:123:5: note: expected 'igraph_real_t' 
> but argument is of type 'igraph_vs_t'
>  int igraph_personalized_pagerank_vs(const igraph_t *graph, 
>  ^
> src/graphobje

[Python-modules-team] Bug#759824: pyfltk: FTBFS: ./python/fltk_wrap.cpp:5241:35: error: format not a string literal and no format arguments [-Werror=format-security]

[Lucas Nussbaum]

Source: pyfltk
Version: 1.3.0-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140830 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> x86_64-linux-gnu-gcc -pthread -g -O0 -Wall -Wstrict-prototypes 
> -fno-strict-aliasing -g -O0 -fstack-protector-strong -Wformat 
> -Werror=format-security -fPIC -DUNIX=1 -I/usr/include/libpng12 
> -I/usr/include/libdrm -I/usr/include/freetype2 -I/usr/include/pixman-1 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/glib-2.0 
> -I/usr/include/cairo -I./src -I./contrib -I/usr/include 
> -I/usr/include/python2.7_d -c ./python/fltk_wrap.cpp -o 
> build/temp.linux-x86_64-2.7-pydebug/./python/fltk_wrap.o -DDO_NOT_USE_THREADS
> cc1plus: warning: command line option '-Wstrict-prototypes' is valid for 
> C/ObjC but not for C++
> ./python/fltk_wrap.cpp: In function 'const char* fl_vararg_input(const char*, 
> const char*)':
> ./python/fltk_wrap.cpp:5241:35: error: format not a string literal and no 
> format arguments [-Werror=format-security]
>  result = fl_input(label, deflt);
>^
> ./python/fltk_wrap.cpp: In function 'const char* fl_vararg_password(const 
> char*, const char*)':
> ./python/fltk_wrap.cpp:5247:38: error: format not a string literal and no 
> format arguments [-Werror=format-security]
>  result = fl_password(label, deflt);
>   ^
> ./python/fltk_wrap.cpp: In function 'void fl_mt_message(const char*)':
> ./python/fltk_wrap.cpp:5285:20: error: format not a string literal and no 
> format arguments [-Werror=format-security]
>  fl_message(text);
> ^
> ./python/fltk_wrap.cpp: In function 'void fl_mt_alert(const char*)':
> ./python/fltk_wrap.cpp:5291:18: error: format not a string literal and no 
> format arguments [-Werror=format-security]
>  fl_alert(text);
>   ^
> ./python/fltk_wrap.cpp: In function 'int fl_mt_ask(const char*)':
> ./python/fltk_wrap.cpp:5298:14: warning: 'int fl_ask(const char*, ...)' is 
> deprecated (declared at /usr/include/FL/fl_ask.H:47) 
> [-Wdeprecated-declarations]
>  status = fl_ask(text);
>   ^
> ./python/fltk_wrap.cpp:5298:25: error: format not a string literal and no 
> format arguments [-Werror=format-security]
>  status = fl_ask(text);
>  ^
> ./python/fltk_wrap.cpp:5298:25: warning: 'int fl_ask(const char*, ...)' is 
> deprecated (declared at /usr/include/FL/fl_ask.H:47) 
> [-Wdeprecated-declarations]
> ./python/fltk_wrap.cpp: In function 'int fl_mt_choice(const char*, const 
> char*, const char*, const char*)':
> ./python/fltk_wrap.cpp:5306:37: error: format not a string literal and no 
> format arguments [-Werror=format-security]
>  status = fl_choice(q, b0, b1, b2);
>  ^
> ./python/fltk_wrap.cpp: In function 'const char* fl_mt_input(const char*, 
> const char*)':
> ./python/fltk_wrap.cpp:5314:35: error: format not a string literal and no 
> format arguments [-Werror=format-security]
>  result = fl_input(label, deflt);
>^
> ./python/fltk_wrap.cpp: In function 'const char* fl_mt_password(const char*, 
> const char*)':
> ./python/fltk_wrap.cpp:5322:38: error: format not a string literal and no 
> format arguments [-Werror=format-security]
>  result = fl_password(label, deflt);
>   ^
> ./python/fltk_wrap.cpp: In function 'PyObject* 
> _wrap_fl_define_FL_ROUND_UP_BOX(PyObject*, PyObject*)':
> ./python/fltk_wrap.cpp:37722:1: warning: label 'fail' defined but not used 
> [-Wunused-label]
>  fail:
>  ^
> ./python/fltk_wrap.cpp: In function 'PyObject* 
> _wrap_fl_define_FL_SHADOW_BOX(PyObject*, PyObject*)':
> ./python/fltk_wrap.cpp:37734:1: warning: label 'fail' defined but not used 
> [-Wunused-label]
>  fail:
>  ^
> ./python/fltk_wrap.cpp: In function 'PyObject* 
> _wrap_fl_define_FL_ROUNDED_BOX(PyObject*, PyObject*)':
> ./python/fltk_wrap.cpp:37746:1: warning: label 'fail' defined but not used 
> [-Wunused-label]
>  fail:
>  ^
> ./python/fltk_wrap.cpp: In function 'PyObject* 
> _wrap_fl_define_FL_RFLAT_BOX(PyObject*, PyObject*)':
> ./python/fltk_wrap.cpp:37758:1: warning: label 'fail' defined but not used 
> [-Wunused-label]
>  fail:
>  ^
> ./python/fltk_wrap.cpp: In function 'PyObject* 
> _wrap_fl_define_FL_RSHADOW_BOX(PyObject*, PyObject*)':
> ./python/fltk_wrap.cpp:37770:1: warning: label 'fail' defined but not used 
> [-Wunused-label]
>  fail:
>  ^
> ./python/fltk_wrap.cpp: In function 'PyObject* 
> _wrap_fl_define_FL_DIAMOND_BOX(PyObject*, PyObject*)':
> ./python/fltk_wrap.cpp:37782:1: warning: label 'fail' defined but not used 
> [-Wunused-label]
>  fail:
>  ^
> ./python/fltk_wrap.cpp: In function 'PyObject* 
> _wrap_fl_define_FL_OVAL_BOX(PyObject*, PyObject*)':
> ./python/fltk_wrap.cpp:37794:1: w

[Python-modules-team] Bug#713757: circuits: FTBFS: tests failed

[Lucas Nussbaum]

On 22/06/13 at 17:34 +0200, Daniele Tricoli wrote:
> tags 713757 +moreinfo
> thanks
> 
> Hello Lucas,
> many thanks for the report.
> 
> 
> On Saturday 22 June 2013 16:11:43 Lucas Nussbaum wrote:
> > During a rebuild of all packages in sid, your package failed to build on
> > amd64.
> 
> It's the same problem of #680799 and I'm not able to riproduce it in a clean 
> pbuilder chroot on my machine.
> 
> After reading http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684817#19
> I disabled address check if DEB_BUILD_OPTIONS contains "parallel" (see 
> 03_force-localhost-as-host-name.patch) but this bug means the problem is 
> different.
> 
> Instead of using gethostbyname() (it's not very reliable) I will propose 
> upstream to use gethostname() since it's more reliable.
> 
> Only to be sure, can you show me the line containig localhost of the VM 
> /etc/hosts?

Hi,
# grep localhost /etc/hosts
127.0.0.1   localhost localhost.localdomain
::1 localhost ip6-localhost ip6-loopback

Lucas

___
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#713757: circuits: FTBFS: tests failed

[Lucas Nussbaum]

Source: circuits
Version: 2.0.1-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130620 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»'
> # Upstream is calling directly py.test inside a Popen so, for now, tests
> # are run only for the default version
> set -e; python setup.py test;
> running test
> running egg_info
> writing circuits.egg-info/PKG-INFO
> writing top-level names to circuits.egg-info/top_level.txt
> writing dependency_links to circuits.egg-info/dependency_links.txt
> writing entry points to circuits.egg-info/entry_points.txt
> writing manifest file 'circuits.egg-info/SOURCES.txt'
> reading manifest file 'circuits.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> writing manifest file 'circuits.egg-info/SOURCES.txt'
> running build_ext
> = test session starts 
> ==
> platform linux2 -- Python 2.7.5 -- pytest-2.3.5
> collected 214 items / 27 skipped
> 
> tests/app/test_config.py 
> tests/app/test_daemon.py .
> tests/app/test_env.py .
> tests/app/test_logger.py ..
> tests/core/test_channel_selection.py .
> tests/core/test_complete.py ..
> tests/core/test_component_repr.py .
> tests/core/test_component_setup.py ...
> tests/core/test_core.py ..
> tests/core/test_debugger.py .
> tests/core/test_dynamic_handlers.py ..
> tests/core/test_errors.py .
> tests/core/test_event.py 
> tests/core/test_feedback.py ..
> tests/core/test_filter_order.py .
> tests/core/test_filters.py .
> tests/core/test_future.py 
> tests/core/test_generator_value.py ..
> tests/core/test_globals.py ...
> tests/core/test_imports.py .
> tests/core/test_inheritence.py ..
> tests/core/test_loader.py .
> tests/core/test_manager_repr.py .
> tests/core/test_pools.py .
> tests/core/test_priority.py .
> tests/core/test_signals.py .
> tests/core/test_singleton.py ..
> tests/core/test_timers.py ...
> tests/core/test_utils.py .
> tests/core/test_value.py ..
> tests/core/test_workers.py .
> tests/io/test_io.py ...
> tests/io/test_notify.py .
> tests/net/test_client.py ...
> tests/net/test_pipe.py .
> tests/net/test_poller_reuse.py .
> tests/net/test_tcp.py 
> tests/net/test_udp.py ..
> tests/net/test_unix.py .
> tests/net/protocols/test_irc.py ..
> tests/net/protocols/test_line.py ..
> tests/node/test_node.py .
> tests/node/test_utils.py ..
> tests/tools/test_tools.py 
> tests/web/test_100_continue.py .
> tests/web/test_basicauth.py .
> tests/web/test_client.py ...
> tests/web/test_conn.py .
> tests/web/test_cookies.py .
> tests/web/test_core.py ...
> tests/web/test_digestauth.py .
> tests/web/test_dispatcher.py 
> tests/web/test_dispatcher2.py ..
> tests/web/test_disps.py .
> tests/web/test_encodings.py ..
> tests/web/test_exceptions.py ...
> tests/web/test_expires.py ..
> tests/web/test_expose.py .
> tests/web/test_future.py .
> tests/web/test_generator.py .
> tests/web/test_gzip.py .
> tests/web/test_http.py .
> tests/web/test_json.py ..
> tests/web/test_jsonrpc.py .
> tests/web/test_large_post.py .
> tests/web/test_logger.py FFF
> tests/web/test_main.py .
> tests/web/test_multipartformdata.py .
> tests/web/test_null_response.py .
> tests/web/test_request_failure.py .
> tests/web/test_serve_download.py .
> tests/web/test_serve_file.py .
> tests/web/test_servers.py ...
> tests/web/test_sessions.py .
> tests/web/test_static.py .
> tests/web/test_unicode.py .
> tests/web/test_utils.py ..
> tests/web/test_value.py .
> tests/web/test_vpath_args.py .
> tests/web/test_websockets.py .
> tests/web/test_wsgi_application.py ..
> tests/web/test_wsgi_application_generator.py .
> tests/web/test_wsgi_application_yield.py .
> tests/web/test_wsgi_gateway.py .
> tests/web/test_wsgi_gateway_errors.py .
> tests/web/test_wsgi_gateway_generator.py .
> tests/web/test_wsgi_gateway_yield.py .
> tests/web/test_xmlrpc.py .
> tests/web/test_yield.py .
> 
> === FAILURES 
> ===
> __ test_file 
> ___
> 
> webapp = 
> 
> def test_file(webapp):
> logfile = StringIO()
> logger = Logger(file=logfile)
> logger.register(webapp)
> 
> f = urlopen(webapp.server.base)
> s = f.read()
> assert s == b"Hello World!"
> 
> logfile.seek(0)
> s = logfile.read().strip()
> 
> format = logger.format
> 
> try:
> address = gethostbyname('localhost')
> except gaierror:
> address = "127.0.0.1"
> 
> d = {}
> d["h"] = address
> d["l"] = "-"
> d["u"] = "-"
> d["r"] = "GET / HTTP/1.1"
> d["s"] = "200"
> d["b"] = "12"
> d["f"] = ""
>   

[Python-modules-team] Bug#713487: pyamf: FTBFS: cpyamf/util.pyx:331:10: Only final types can have final Python (def/cpdef) methods

[Lucas Nussbaum]

Source: pyamf
Version: 0.6.1+dfsg-3
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130620 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[1]: Entering directory `/«BUILDDIR»/pyamf-0.6.1+dfsg'
> rm -f cpyamf/*.c
> cython cpyamf/*.pyx
> 
> Error compiling Cython file:
> 
> ...
> timezone_offset=self.timezone_offset)
> 
> self.writeType(TYPE_AMF3)
> self.amf3_encoder.writeElement(o)
> 
> cdef inline int handleBasicTypes(self, object element, object py_type) 
> except -1:
> ^
> 
> 
> cpyamf/amf0.pyx:585:9: Overriding final methods is not allowed
> 
> Error compiling Cython file:
> 
> ...
> """
> cdef object proxy = self.context.getProxyForObject(obj)
> 
> return self.writeObject(proxy, 1)
> 
> cdef inline int handleBasicTypes(self, object element, object py_type) 
> except -1:
> ^
> 
> 
> cpyamf/amf3.pyx:1031:9: Overriding final methods is not allowed
> warning: cpyamf/codec.pyx:15:29: Function signature does not match previous 
> declaration
> warning: cpyamf/codec.pyx:16:25: Function signature does not match previous 
> declaration
> warning: cpyamf/codec.pyx:17:25: Function signature does not match previous 
> declaration
> 
> Error compiling Cython file:
> 
> ...
> self._strings = {}
> self.extra = {}
> 
> return 0
> 
> cpdef inline object getObject(self, Py_ssize_t ref):
>  ^
> 
> 
> cpyamf/codec.pyx:224:10: Only final types can have final Python (def/cpdef) 
> methods
> 
> Error compiling Cython file:
> 
> ...
> return 0
> 
> cpdef inline object getObject(self, Py_ssize_t ref):
> return self.objects.getByReference(ref)
> 
> cpdef inline Py_ssize_t getObjectReference(self, object obj) except -2:
>  ^
> 
> 
> cpyamf/codec.pyx:227:10: Only final types can have final Python (def/cpdef) 
> methods
> 
> Error compiling Cython file:
> 
> ...
> return self.objects.getByReference(ref)
> 
> cpdef inline Py_ssize_t getObjectReference(self, object obj) except -2:
> return self.objects.getReferenceTo(obj)
> 
> cpdef inline Py_ssize_t addObject(self, object obj) except -1:
>  ^
> 
> 
> cpyamf/codec.pyx:230:10: Only final types can have final Python (def/cpdef) 
> methods
> 
> Error compiling Cython file:
> 
> ...
> from cpyamf.util cimport cBufferedByteStream, BufferedByteStream
> 
> import types
> import pyamf
> from pyamf import util, xml
> import datetime
>   ^
> 
> 
> cpyamf/codec.pyx:27:7: Assignment to non-lvalue 'datetime'
> 
> Error compiling Cython file:
> 
> ...
> if self.buffer == NULL:
> PyErr_NoMemory()
> 
> return 0
> 
> cpdef inline Py_ssize_t tell(self):
>  ^
> 
> 
> cpyamf/util.pyx:227:10: Only final types can have final Python (def/cpdef) 
> methods
> 
> Error compiling Cython file:
> 
> ...
> 
> self.pos += size
> 
> return 0
> 
> cpdef inline bint at_eof(self) except -1:
>  ^
> 
> 
> cpyamf/util.pyx:323:10: Only final types can have final Python (def/cpdef) 
> methods
> 
> Error compiling Cython file:
> 
> ...
> 
> @rtype: C{bool}
> """
> return self.length == self.pos
> 
> cpdef inline Py_ssize_t remaining(self) except -1:
>  ^
> 
> 
> cpyamf/util.pyx:331:10: Only final types can have final Python (def/cpdef) 
> methods
> warning: cpyamf/util.pyx:951:4: Overriding cdef method with def method.
> warning: cpyamf/util.pyx:972:4: Overriding cdef method with def method.
> warning: cpyamf/util.pyx:991:4: Overriding cdef method with def method.
> warning: cpyamf/util.pyx:1011:4: Overriding cdef method with def method.
> warning: cpyamf/util.pyx:1024:4: Overriding cdef method with def method.
> warning: cpyamf/util.pyx:1037:

[Python-modules-team] Bug#713191: python-pip: FTBFS: /bin/sh: 2: python3.3: not found

[Lucas Nussbaum]

Source: python-pip
Version: 1.1-3
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130620 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»'
> dh_auto_build
> running build
> running build_py
> creating build
> creating build/lib.linux-x86_64-2.7
> creating build/lib.linux-x86_64-2.7/pip
> copying pip/req.py -> build/lib.linux-x86_64-2.7/pip
> copying pip/util.py -> build/lib.linux-x86_64-2.7/pip
> copying pip/status_codes.py -> build/lib.linux-x86_64-2.7/pip
> copying pip/runner.py -> build/lib.linux-x86_64-2.7/pip
> copying pip/log.py -> build/lib.linux-x86_64-2.7/pip
> copying pip/locations.py -> build/lib.linux-x86_64-2.7/pip
> copying pip/index.py -> build/lib.linux-x86_64-2.7/pip
> copying pip/exceptions.py -> build/lib.linux-x86_64-2.7/pip
> copying pip/download.py -> build/lib.linux-x86_64-2.7/pip
> copying pip/baseparser.py -> build/lib.linux-x86_64-2.7/pip
> copying pip/basecommand.py -> build/lib.linux-x86_64-2.7/pip
> copying pip/backwardcompat.py -> build/lib.linux-x86_64-2.7/pip
> copying pip/_pkgutil.py -> build/lib.linux-x86_64-2.7/pip
> copying pip/__init__.py -> build/lib.linux-x86_64-2.7/pip
> creating build/lib.linux-x86_64-2.7/pip/commands
> copying pip/commands/zip.py -> build/lib.linux-x86_64-2.7/pip/commands
> copying pip/commands/unzip.py -> build/lib.linux-x86_64-2.7/pip/commands
> copying pip/commands/uninstall.py -> build/lib.linux-x86_64-2.7/pip/commands
> copying pip/commands/search.py -> build/lib.linux-x86_64-2.7/pip/commands
> copying pip/commands/install.py -> build/lib.linux-x86_64-2.7/pip/commands
> copying pip/commands/help.py -> build/lib.linux-x86_64-2.7/pip/commands
> copying pip/commands/freeze.py -> build/lib.linux-x86_64-2.7/pip/commands
> copying pip/commands/completion.py -> build/lib.linux-x86_64-2.7/pip/commands
> copying pip/commands/bundle.py -> build/lib.linux-x86_64-2.7/pip/commands
> copying pip/commands/__init__.py -> build/lib.linux-x86_64-2.7/pip/commands
> creating build/lib.linux-x86_64-2.7/pip/vcs
> copying pip/vcs/bazaar.py -> build/lib.linux-x86_64-2.7/pip/vcs
> copying pip/vcs/__init__.py -> build/lib.linux-x86_64-2.7/pip/vcs
> copying pip/vcs/subversion.py -> build/lib.linux-x86_64-2.7/pip/vcs
> copying pip/vcs/mercurial.py -> build/lib.linux-x86_64-2.7/pip/vcs
> copying pip/vcs/git.py -> build/lib.linux-x86_64-2.7/pip/vcs
> set -ex; for py in 3.2 3.3 ; do \
>   python$py setup.py build; \
>   done;
> + python3.2 setup.py build
> running build
> running build_py
> creating build/lib
> creating build/lib/pip
> copying pip/req.py -> build/lib/pip
> copying pip/util.py -> build/lib/pip
> copying pip/status_codes.py -> build/lib/pip
> copying pip/runner.py -> build/lib/pip
> copying pip/log.py -> build/lib/pip
> copying pip/locations.py -> build/lib/pip
> copying pip/index.py -> build/lib/pip
> copying pip/exceptions.py -> build/lib/pip
> copying pip/download.py -> build/lib/pip
> copying pip/baseparser.py -> build/lib/pip
> copying pip/basecommand.py -> build/lib/pip
> copying pip/backwardcompat.py -> build/lib/pip
> copying pip/_pkgutil.py -> build/lib/pip
> copying pip/__init__.py -> build/lib/pip
> creating build/lib/pip/commands
> copying pip/commands/zip.py -> build/lib/pip/commands
> copying pip/commands/unzip.py -> build/lib/pip/commands
> copying pip/commands/uninstall.py -> build/lib/pip/commands
> copying pip/commands/search.py -> build/lib/pip/commands
> copying pip/commands/install.py -> build/lib/pip/commands
> copying pip/commands/help.py -> build/lib/pip/commands
> copying pip/commands/freeze.py -> build/lib/pip/commands
> copying pip/commands/completion.py -> build/lib/pip/commands
> copying pip/commands/bundle.py -> build/lib/pip/commands
> copying pip/commands/__init__.py -> build/lib/pip/commands
> creating build/lib/pip/vcs
> copying pip/vcs/bazaar.py -> build/lib/pip/vcs
> copying pip/vcs/__init__.py -> build/lib/pip/vcs
> copying pip/vcs/subversion.py -> build/lib/pip/vcs
> copying pip/vcs/mercurial.py -> build/lib/pip/vcs
> copying pip/vcs/git.py -> build/lib/pip/vcs
> + python3.3 setup.py build
> /bin/sh: 2: python3.3: not found
> make[1]: *** [override_dh_auto_build] Error 127

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/06/20/python-pip_1.1-3_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-mo

[Python-modules-team] Bug#713123: pyside-tools: FTBFS: build-dependency not installable: libpyside-dev (>= 1.0.6)

[Lucas Nussbaum]

Source: pyside-tools
Version: 0.2.14-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130620 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> ┌──┐
> │ Install pyside-tools build dependencies (apt-based resolver)
>  │
> └──┘
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> 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:
>  sbuild-build-depends-pyside-tools-dummy : Depends: libpyside-dev (>= 1.0.6) 
> but it is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/06/20/pyside-tools_0.2.14-2_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#713092: flask-silk: FTBFS: pkg_resources.VersionConflict: (itsdangerous 0.17 (/usr/lib/python2.7/dist-packages), Requirement.parse('itsdangerous>=0.21'))

[Lucas Nussbaum]

Source: flask-silk
Version: 0.2-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130620 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»'
> set -ex && for py in 2.7; do \
>   PYTHONPATH=$(ls -d /«PKGBUILDDIR»/build/lib.*-$py) python$py 
> setup.py test ;\
>   done
> + ls -d /«PKGBUILDDIR»/build/lib.linux-x86_64-2.7
> + PYTHONPATH=/«PKGBUILDDIR»/build/lib.linux-x86_64-2.7 python2.7 setup.py test
> running test
> Traceback (most recent call last):
>   File "setup.py", line 46, in 
> 'Topic :: Software Development :: Libraries :: Python Modules'
>   File "/usr/lib/python2.7/distutils/core.py", line 152, in setup
> dist.run_commands()
>   File "/usr/lib/python2.7/distutils/dist.py", line 953, in run_commands
> self.run_command(cmd)
>   File "/usr/lib/python2.7/distutils/dist.py", line 972, in run_command
> cmd_obj.run()
>   File "/usr/lib/python2.7/dist-packages/setuptools/command/test.py", line 
> 128, in run
> self.distribution.fetch_build_eggs(self.distribution.install_requires)
>   File "/usr/lib/python2.7/dist-packages/setuptools/dist.py", line 245, in 
> fetch_build_eggs
> parse_requirements(requires), installer=self.fetch_build_egg
>   File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 598, in 
> resolve
> raise VersionConflict(dist,req) # XXX put more info here
> pkg_resources.VersionConflict: (itsdangerous 0.17 
> (/usr/lib/python2.7/dist-packages), Requirement.parse('itsdangerous>=0.21'))
> make[1]: *** [override_dh_auto_test] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/06/20/flask-silk_0.2-2_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#713089: flask-autoindex: FTBFS: pkg_resources.VersionConflict: (itsdangerous 0.17 (/usr/lib/python2.7/dist-packages), Requirement.parse('itsdangerous>=0.21'))

[Lucas Nussbaum]

Source: flask-autoindex
Version: 0.5-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130620 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»'
> set -ex && for py in 2.7; do \
>   PYTHONPATH=$(ls -d /«PKGBUILDDIR»/build/lib.*-$py) python$py 
> setup.py test ;\
>   done
> + ls -d /«PKGBUILDDIR»/build/lib.linux-x86_64-2.7
> + PYTHONPATH=/«PKGBUILDDIR»/build/lib.linux-x86_64-2.7 python2.7 setup.py test
> running test
> Traceback (most recent call last):
>   File "setup.py", line 54, in 
> 'Topic :: Software Development :: Libraries :: Python Modules'
>   File "/usr/lib/python2.7/distutils/core.py", line 152, in setup
> dist.run_commands()
>   File "/usr/lib/python2.7/distutils/dist.py", line 953, in run_commands
> self.run_command(cmd)
>   File "/usr/lib/python2.7/distutils/dist.py", line 972, in run_command
> cmd_obj.run()
>   File "/usr/lib/python2.7/dist-packages/setuptools/command/test.py", line 
> 128, in run
> self.distribution.fetch_build_eggs(self.distribution.install_requires)
>   File "/usr/lib/python2.7/dist-packages/setuptools/dist.py", line 245, in 
> fetch_build_eggs
> parse_requirements(requires), installer=self.fetch_build_egg
>   File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 598, in 
> resolve
> raise VersionConflict(dist,req) # XXX put more info here
> pkg_resources.VersionConflict: (itsdangerous 0.17 
> (/usr/lib/python2.7/dist-packages), Requirement.parse('itsdangerous>=0.21'))
> make[1]: *** [override_dh_auto_test] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/06/20/flask-autoindex_0.5-2_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#713076: epsilon: FTBFS: tests failed

[Lucas Nussbaum]

Source: epsilon
Version: 0.6.0-3
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130620 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  fakeroot debian/rules binary
> pyversions: missing X(S)-Python-Version in control file, fall back to 
> debian/pyversions
> pyversions: missing debian/pyversions file, fall back to supported versions
> test -x debian/rules
> dh_testroot
> dh_clean -k 
> dh_clean: dh_clean -k is deprecated; use dh_prep instead
> dh_installdirs -A 
> mkdir -p "."
> mkdir -p debian/python-module-stampdir
> cd . && \
>   python setup.py build \
>   --build-base="/«PKGBUILDDIR»/./build"
> Files in package 'epsilon':
> ['setuphelper.pyc',
>  '_version.pyc',
>  '__init__.pyc',
>  'setuphelper.py',
>  'view.py',
>  'unrepr.py',
>  'structlike.py',
>  'sslverify.py',
>  'spewer.py',
>  'release.py',
>  'react.py',
>  'process.py',
>  'pending.py',
>  'modal.py',
>  'liner.py',
>  'juice.py',
>  'iepsilon.py',
>  'hotfix.py',
>  'extime.py',
>  'expose.py',
>  'descriptor.py',
>  'cooperator.py',
>  'caseless.py',
>  'asplode.py',
>  'amprouter.py',
>  'ampauth.py',
>  '_version.py',
>  '__init__.py',
>  'test',
>  'scripts',
>  'hotfixes']
> Automatically determined setup() args:
> {   'package_data': {   'epsilon': []},
> 'packages': [   'epsilon',
> 'epsilon.test',
> 'epsilon.scripts',
> 'epsilon.hotfixes']}
> running build
> running build_py
> running build_scripts
> touch debian/python-module-stampdir/python-epsilon
> Adding cdbs dependencies to debian/python-epsilon.substvars
> dh_installdirs -ppython-epsilon 
> cd . && \
>   python setup.py install \
>   --root="/«PKGBUILDDIR»/debian/python-epsilon/" \
>   --install-purelib=/usr/lib/python2.7/site-packages/ \
>   --prefix=/usr --no-compile -O0 
> Files in package 'epsilon':
> ['setuphelper.pyc',
>  '_version.pyc',
>  '__init__.pyc',
>  'setuphelper.py',
>  'view.py',
>  'unrepr.py',
>  'structlike.py',
>  'sslverify.py',
>  'spewer.py',
>  'release.py',
>  'react.py',
>  'process.py',
>  'pending.py',
>  'modal.py',
>  'liner.py',
>  'juice.py',
>  'iepsilon.py',
>  'hotfix.py',
>  'extime.py',
>  'expose.py',
>  'descriptor.py',
>  'cooperator.py',
>  'caseless.py',
>  'asplode.py',
>  'amprouter.py',
>  'ampauth.py',
>  '_version.py',
>  '__init__.py',
>  'test',
>  'scripts',
>  'hotfixes']
> Automatically determined setup() args:
> {   'package_data': {   'epsilon': []},
> 'packages': [   'epsilon',
> 'epsilon.test',
> 'epsilon.scripts',
> 'epsilon.hotfixes']}
> running install
> running build
> running build_py
> running build_scripts
> running install_lib
> creating /«PKGBUILDDIR»/debian/python-epsilon/usr
> creating /«PKGBUILDDIR»/debian/python-epsilon/usr/lib
> creating /«PKGBUILDDIR»/debian/python-epsilon/usr/lib/python2.7
> creating /«PKGBUILDDIR»/debian/python-epsilon/usr/lib/python2.7/site-packages
> creating 
> /«PKGBUILDDIR»/debian/python-epsilon/usr/lib/python2.7/site-packages/epsilon
> creating 
> /«PKGBUILDDIR»/debian/python-epsilon/usr/lib/python2.7/site-packages/epsilon/hotfixes
> copying build/lib.linux-x86_64-2.7/epsilon/hotfixes/__init__.py -> 
> /«PKGBUILDDIR»/debian/python-epsilon/usr/lib/python2.7/site-packages/epsilon/hotfixes
> copying 
> build/lib.linux-x86_64-2.7/epsilon/hotfixes/deferredgenerator_tfailure.py -> 
> /«PKGBUILDDIR»/debian/python-epsilon/usr/lib/python2.7/site-packages/epsilon/hotfixes
> copying build/lib.linux-x86_64-2.7/epsilon/hotfixes/delayedcall_seconds.py -> 
> /«PKGBUILDDIR»/debian/python-epsilon/usr/lib/python2.7/site-packages/epsilon/hotfixes
> copying build/lib.linux-x86_64-2.7/epsilon/hotfixes/filepath_copyTo.py -> 
> /«PKGBUILDDIR»/debian/python-epsilon/usr/lib/python2.7/site-packages/epsilon/hotfixes
> copying build/lib.linux-x86_64-2.7/epsilon/hotfixes/internet_task_clock.py -> 
> /«PKGBUILDDIR»/debian/python-epsilon/usr/lib/python2.7/site-packages/epsilon/hotfixes
> copying 
> build/lib.linux-x86_64-2.7/epsilon/hotfixes/loopbackasync_reentrancy.py -> 
> /«PKGBUILDDIR»/debian/python-epsilon/usr/lib/python2.7/site-packages/epsilon/hotfixes
> copying build/lib.linux-x86_64-2.7/epsilon/hotfixes/plugin_package_paths.py 
> -> 
> /«PKGBUILDDIR»/debian/python-epsilon/usr/lib/python2.7/site-packages/epsilon/hotfixes
> copying 
> build/lib.linux-x86_64-2.7/epsilon/hotfixes/proto_helpers_stringtransport.py 
> -> 
> /«PKGBUILDDIR»/debian/python-epsilon/usr/lib/python2.7/site-packages/epsilon/hotfixes
> copying build/lib.linux-x86_64-2.7/epsilon/hotfixes/timeoutmixin_calllater.py 
> -> 
> /«PKGBUILDDIR»/debian/python-epsilon/usr/lib/python2.7/site-packages/epsilon/hotfixes
> copying build/lib.linux-x86_64-2.7/epsilon/hotfixes/trial_assertwarns.py -> 
> /«PKGBUILDDIR»/

[Python-modules-team] Bug#707529: cssutils: FTBFS: /bin/sh: 3: nosetests-3.3: not found

[Lucas Nussbaum]

Source: cssutils
Version: 0.9.10~b1-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130509 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»'
> set -ex; \
>   for py in 2.7; do \
>   nosetests-$py -v \
> --exclude='test_parseString' \
> --exclude='test_parseFile' \
> --exclude='test_parseUrl' \
> --exclude='test_combine' \
> --exclude='test_cssText2' \
> --exclude='test_getMetaInfo' \
> --exclude='test_errorhandler.py' \
> --where /«PKGBUILDDIR»/build/lib.linux-*/tests; \
>   done
> + nosetests-2.7 -v --exclude=test_parseString --exclude=test_parseFile 
> --exclude=test_parseUrl --exclude=test_combine --exclude=test_cssText2 
> --exclude=test_getMetaInfo --exclude=test_errorhandler.py --where 
> /«PKGBUILDDIR»/build/lib.linux-x86_64-2.7/tests
> codec.decode (force) ... ok
> codecs.decoder ... ok
> codec.detectencoding_str() ... ok
> codec.detectencoding_unicode() ... ok
> codec.encoder ... ok
> codec._fixencoding() ... ok
> CSSMediaRule.cssRules.parentRule .parentStyleSheet .type ... ok
> CSSCharsetRule InvalidModificationErr ... ok
> CSSCharsetRule.cssText ... ok
> CSSCharsetRule.encoding ... ok
> CSSCharsetRule.__init__() ... ok
> CSSCharsetRule.__init__(encoding) ... ok
> CSSRule.parentRule .parentStyleSheet .type ... ok
> CSSRule readonly ... ok
> CSSCharsetRule.__repr__() ... ok
> CSSCharsetRule.__repr__(), .__str__() ... ok
> CSSMediaRule.cssRules.parentRule .parentStyleSheet .type ... ok
> CSSComment.cssText InvalidModificationErr ... ok
> CSSComment.cssText ... ok
> CSSComment.type and init ... ok
> CSSRule.parentRule .parentStyleSheet .type ... ok
> CSSRule readonly ... ok
> CSSComment.__repr__(), .__str__() ... ok
> CSSMediaRule.cssRules.parentRule .parentStyleSheet .type ... ok
> CSSFontFaceRule.cssText InvalidModificationErr ... ok
> CSSFontFaceRule.cssText ... ok
> CSSFontFaceRule (incomplete) ... ok
> CSSFontFaceRule.__init__() ... ok
> CSSRule.parentRule .parentStyleSheet .type ... ok
> CSSFontFaceRule.style properties ... ok
> CSSRule readonly ... ok
> CSSFontFaceRule.__repr__(), .__str__() ... ok
> CSSFontFaceRule.style (and references) ... ok
> CSSFontFaceRule.valid ... ok
> CSSMediaRule.cssRules.parentRule .parentStyleSheet .type ... ok
> CSSImportRule.cssText InvalidModificationErr ... ok
> CSSImportRule.cssText ... ok
> CSSImportRule.href ... ok
> CSSImportRule.hrefFound ... ok
> CSSImportRule.hreftype ... ok
> CSSImportRule (incomplete) ... ok
> CSSImportRule.__init__() ... ok
> CSSImportRule.media ... ok
> CSSImportRule.name ... ok
> CSSRule.parentRule .parentStyleSheet .type ... ok
> CSSRule readonly ... ok
> CSSImportRule.__repr__(), .__str__() ... ok
> CSSImportRule.styleSheet ... ok
> CSSMediaRule.cssRules.parentRule .parentStyleSheet .type ... ok
> CSSMediaRule.cssText InvalidModificationErr ... ok
> CSSMediaRule.add() ... ok
> CSSMediaRule.cssRules ... ok
> CSSMediaRule.cssText ... ok
> CSSMediaRule.deleteRule(rule) ... ok
> CSSMediaRule.deleteRule(index) ... ok
> CSSMediaRule (incomplete) ... ok
> CSSMediaRule.__init__() ... ok
> CSSMediaRule.insertRule ... ok
> CSSMediaRule.__iter__() ... ok
> CSSMediaRule.media ... ok
> CSSMediaRule.name ... ok
> CSSRule.parentRule .parentStyleSheet .type ... ok
> CSSRule readonly ... ok
> CSSStylesheet references ... ok
> CSSMediaRule.__repr__(), .__str__() ... ok
> CSSMediaRule.cssRules.parentRule .parentStyleSheet .type ... ok
> CSSNamespaceRule.cssText InvalidModificationErr ... ok
> CSSNamespaceRule.cssText ... ok
> CSSNamespaceRule (incomplete) ... ok
> CSSNamespaceRule.__init__() ... ok
> CSSNamespaceRule.namespaceURI ... ok
> CSSRule.parentRule .parentStyleSheet .type ... ok
> CSSNamespaceRule.prefix ... ok
> CSSRule readonly ... ok
> CSSNamespaceRule.__repr__(), .__str__() ... ok
> CSSMediaRule.cssRules.parentRule .parentStyleSheet .type ... ok
> CSSPageRule.cssText InvalidModificationErr ... ok
> CSSPageRule.cssRules ... ok
> CSSPageRule.cssText ... ok
> CSSPageRule (incomplete) ... ok
> CSSPageRule.__init__() ... ok
> CSSRule.parentRule .parentStyleSheet .type ... ok
> CSSPageRule.style properties ... ok
> CSSRule readonly ... ok
> CSSPageRule.__repr__(), .__str__() ... ok
> CSSPageRule.selectorText ... ok
> CSSPageRule.specificity ... ok
> CSSPageRule.style (and references) ... ok
> CSS2Properties ... ok
> cssproperties _toCSSname(DOMname) ... ok
> cssproperties _toDOMname(CSSname) ... ok
> CSSMediaRule.cssRules.parentRule .parentStyleSheet .type ... ok
> CSSRule.type and init ... ok
> CSSRule.parentRule .parentStyleSheet .type ... ok
> CSSRule readonly ... ok
> CSSRuleList.__init__() ... ok
> CSSRuleList.rulesOfType() ... ok
> CSSStyleDeclaration._

[Python-modules-team] Bug#707516: python-flexmock: FTBFS: /bin/sh: 5: nosetests-3.3: not found

[Lucas Nussbaum]

Source: python-flexmock
Version: 0.9.6-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130509 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»'
> set -ex; \
>   export PYTHONPATH=.; \
>   for py in 2.7 3.2 3.3; do \
>   python$py tests/flexmock_unittest_test.py; \
>   nosetests-$py tests/flexmock_nose_test.py; \
>   py.test-$py tests/flexmock_pytest_test.py; \
>   done
> + export PYTHONPATH=.
> + python2.7 tests/flexmock_unittest_test.py
> ..
> --
> Ran 162 tests in 0.050s
> 
> OK
> + nosetests-2.7 tests/flexmock_nose_test.py
> .
> --
> Ran 325 tests in 0.124s
> 
> OK
> + py.test-2.7 tests/flexmock_pytest_test.py
> = test session starts 
> ==
> platform linux2 -- Python 2.7.3 -- pytest-2.2.4
> collecting ... collected 319 items
> 
> tests/flexmock_pytest_test.py 
> ...
> 
> == 319 passed in 0.75 seconds 
> ==
> + python3.2 tests/flexmock_unittest_test.py
> ..
> --
> Ran 162 tests in 0.057s
> 
> OK
> + nosetests-3.2 tests/flexmock_nose_test.py
> .
> --
> Ran 325 tests in 0.134s
> 
> OK
> + py.test-3.2 tests/flexmock_pytest_test.py
> = test session starts 
> ==
> platform linux2 -- Python 3.2.3 -- pytest-2.2.4
> collecting ... collected 319 items
> 
> tests/flexmock_pytest_test.py 
> ...
> 
> == 319 passed in 0.79 seconds 
> ==
> + python3.3 tests/flexmock_unittest_test.py
> ..
> --
> Ran 162 tests in 0.069s
> 
> OK
> + nosetests-3.3 tests/flexmock_nose_test.py
> /bin/sh: 5: nosetests-3.3: not found
> make[1]: *** [override_dh_auto_test] Error 127

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2013/05/09/python-flexmock_0.9.6-1_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#707425: cairosvg: FTBFS: ImportError: No module named 'cairo._cairo'

[Lucas Nussbaum]

Source: cairosvg
Version: 0.4.3-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130509 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»'
> set -e; \
>   for py in python2.7 python3.2 python3.3; do \
>   $py -B setup.py clean; \
>   rm -rf build; \
>   done
> running clean
> running clean
> Traceback (most recent call last):
>   File "setup.py", line 23, in 
> from cairosvg import VERSION
>   File "/«PKGBUILDDIR»/cairosvg/__init__.py", line 27, in 
> from . import surface
>   File "/«PKGBUILDDIR»/cairosvg/surface/__init__.py", line 23, in 
> import cairo
>   File "/usr/lib/python3/dist-packages/cairo/__init__.py", line 18, in 
> 
> from ._cairo import *
> ImportError: No module named 'cairo._cairo'
> make[1]: *** [override_dh_auto_clean] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2013/05/09/cairosvg_0.4.3-1_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#707408: python-notify2: FTBFS: ImportError: No module named '_dbus_bindings'

[Lucas Nussbaum]

Source: python-notify2
Version: 0.3-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130509 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»'
> python3.2 setup.py build
> running build
> running build_py
> creating build
> creating build/lib
> copying notify2.py -> build/lib
> python3.3 setup.py build
> Traceback (most recent call last):
>   File "setup.py", line 2, in 
> import notify2
>   File "/«PKGBUILDDIR»/notify2.py", line 38, in 
> import dbus
>   File "/usr/lib/python3/dist-packages/dbus/__init__.py", line 82, in 
> import dbus.types as types
>   File "/usr/lib/python3/dist-packages/dbus/types.py", line 6, in 
> from _dbus_bindings import (
> ImportError: No module named '_dbus_bindings'
> make[1]: *** [build-python3.3] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2013/05/09/python-notify2_0.3-2_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#707407: python-numpy: FTBFS: _configtest.c:6: undefined reference to `exp'

[Lucas Nussbaum]

Source: python-numpy
Version: 1:1.6.2-1.2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130509 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> gcc -pthread _configtest.o -o _configtest
> _configtest.o: In function `main':
> /«PKGBUILDDIR»/_configtest.c:6: undefined reference to `exp'
> collect2: error: ld returned 1 exit status

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2013/05/09/python-numpy_1.6.2-1.2_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#699251: python-eventlet: FTBFS: build-dependency not installable: python-greenlet (>= 0.3.1-2.1)

[Lucas Nussbaum]

Source: python-eventlet
Version: 0.9.16-3
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130129 qa-ftbfs
Justification: FTBFS in wheezy on amd64

Hi,

During a rebuild of all packages in *wheezy*, your package failed to
build on amd64.

Relevant part:
> ┌──┐
> │ Install python-eventlet build dependencies (apt-based resolver) 
>  │
> └──┘
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> 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:
>  sbuild-build-depends-python-eventlet-dummy : Depends: python-greenlet (>= 
> 0.3.1-2.1) but it is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2013/01/29/python-eventlet_0.9.16-3_wheezy.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#684852: python-eventlet: FTBFS: greenlet.h:8:20: fatal error: Python.h: No such file or directory

[Lucas Nussbaum]

Source: python-eventlet
Version: 0.9.16-2
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120814 qa-ftbfs
Justification: FTBFS in wheezy on amd64

Hi,

During a rebuild of all packages in *wheezy*, your package failed to
build on amd64.

Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»'
> set -e; \
>   for python in python2.7 python2.6; do \
>   $python setup.py test; \
>   done
> running test
> Checking .pth file support in .
> /usr/bin/python2.7 -E -c pass
> Searching for greenlet>=0.3
> Reading http://pypi.python.org/simple/greenlet/
> Reading https://github.com/python-greenlet/greenlet
> Reading http://bitbucket.org/ambroff/greenlet
> Best match: greenlet 0.4.0
> Downloading 
> http://pypi.python.org/packages/source/g/greenlet/greenlet-0.4.0.zip#md5=87887570082caadc08fb1f8671dbed71
> Processing greenlet-0.4.0.zip
> Running greenlet-0.4.0/setup.py -q bdist_egg --dist-dir 
> /tmp/easy_install-6X0OiZ/greenlet-0.4.0/egg-dist-tmp-rsNRcG
> In file included from greenlet.c:5:0:
> greenlet.h:8:20: fatal error: Python.h: No such file or directory
> compilation terminated.
> error: Setup script exited with error: command 'gcc' failed with exit status 1
> make[1]: *** [override_dh_auto_test] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2012/08/14/python-eventlet_0.9.16-2_wheezy.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#684831: pyside: FTBFS: build-dependency not installable: libphonon-dev

[Lucas Nussbaum]

Source: pyside
Version: 1.1.1-3
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120814 qa-ftbfs
Justification: FTBFS in wheezy on amd64

Hi,

During a rebuild of all packages in *wheezy*, your package failed to
build on amd64.

Relevant part:
> ┌──┐
> │ Install pyside build dependencies (apt-based resolver)  
>  │
> └──┘
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> 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:
>  sbuild-build-depends-pyside-dummy : Depends: libphonon-dev but it is not 
> going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://people.debian.org/~lucas/logs/2012/08/14/pyside_1.1.1-3_wheezy.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
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#684821: python-concurrent.futures: FTBFS: failed test

[Lucas Nussbaum]

Source: python-concurrent.futures
Version: 2.1.2-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120814 qa-ftbfs
Justification: FTBFS in wheezy on amd64

Hi,

During a rebuild of all packages in *wheezy*, your package failed to
build on amd64.

Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»'
> set -e ; \
>   for python in python2.7 python2.6; do \
>   # retrive the lib path \
>   LIB=$($python -c "from distutils.command.build import build ; 
> from distutils.core import Distribution ; b = build(Distribution()) ; 
> b.finalize_options() ; print b.build_purelib") ; \
>   PYTHONPATH=$LIB $python ./test_futures.py ; \
>   done
> test_map (__main__.ProcessPoolExecutorTest) ... ERROR
> test_map_exception (__main__.ProcessPoolExecutorTest) ... ERROR
> test_map_timeout (__main__.ProcessPoolExecutorTest) ... ERROR
> test_submit (__main__.ProcessPoolExecutorTest) ... ERROR
> test_submit_keyword (__main__.ProcessPoolExecutorTest) ... ERROR
> test_map (__main__.ThreadPoolExecutorTest) ... ok
> test_map_exception (__main__.ThreadPoolExecutorTest) ... ok
> test_map_timeout (__main__.ThreadPoolExecutorTest) ... ERROR
> test_submit (__main__.ThreadPoolExecutorTest) ... ok
> test_submit_keyword (__main__.ThreadPoolExecutorTest) ... ok
> test_all_completed (__main__.ProcessPoolWaitTests) ... ERROR
> test_all_completed_some_already_completed (__main__.ProcessPoolWaitTests) ... 
> ERROR
> test_first_completed (__main__.ProcessPoolWaitTests) ... ERROR
> test_first_completed_one_already_completed (__main__.ProcessPoolWaitTests) 
> ... ERROR
> test_first_exception (__main__.ProcessPoolWaitTests) ... ERROR
> test_first_exception_one_already_failed (__main__.ProcessPoolWaitTests) ... 
> ERROR
> test_first_exception_some_already_complete (__main__.ProcessPoolWaitTests) 
> ... ERROR
> test_timeout (__main__.ProcessPoolWaitTests) ... ERROR
> test_all_completed (__main__.ThreadPoolWaitTests) ... ERROR
> test_all_completed_some_already_completed (__main__.ThreadPoolWaitTests) ... 
> ERROR
> test_first_completed (__main__.ThreadPoolWaitTests) ... ERROR
> test_first_completed_one_already_completed (__main__.ThreadPoolWaitTests) ... 
> ERROR
> test_first_exception (__main__.ThreadPoolWaitTests) ... ERROR
> test_first_exception_one_already_failed (__main__.ThreadPoolWaitTests) ... 
> ERROR
> test_first_exception_some_already_complete (__main__.ThreadPoolWaitTests) ... 
> ERROR
> test_timeout (__main__.ThreadPoolWaitTests) ... ERROR
> test_no_timeout (__main__.ProcessPoolAsCompletedTests) ... ERROR
> test_zero_timeout (__main__.ProcessPoolAsCompletedTests) ... ERROR
> test_no_timeout (__main__.ThreadPoolAsCompletedTests) ... ERROR
> test_zero_timeout (__main__.ThreadPoolAsCompletedTests) ... ERROR
> test_cancel (__main__.FutureTests) ... ok
> test_cancelled (__main__.FutureTests) ... ok
> test_done (__main__.FutureTests) ... ok
> test_done_callback_already_cancelled (__main__.FutureTests) ... ok
> test_done_callback_already_failed (__main__.FutureTests) ... ok
> test_done_callback_already_successful (__main__.FutureTests) ... ok
> test_done_callback_raises (__main__.FutureTests) ... ok
> test_done_callback_with_cancel (__main__.FutureTests) ... ok
> test_done_callback_with_exception (__main__.FutureTests) ... ok
> test_done_callback_with_result (__main__.FutureTests) ... ok
> test_exception_with_success (__main__.FutureTests) ... ok
> test_exception_with_timeout (__main__.FutureTests) ... ok
> test_repr (__main__.FutureTests) ... ok
> test_result_with_cancel (__main__.FutureTests) ... ok
> test_result_with_success (__main__.FutureTests) ... ok
> test_result_with_timeout (__main__.FutureTests) ... ok
> test_running (__main__.FutureTests) ... ok
> test_context_manager_shutdown (__main__.ProcessPoolShutdownTest) ... ERROR
> test_del_shutdown (__main__.ProcessPoolShutdownTest) ... ERROR
> test_processes_terminate (__main__.ProcessPoolShutdownTest) ... ERROR
> test_run_after_shutdown (__main__.ProcessPoolShutdownTest) ... ERROR
> test_context_manager_shutdown (__main__.ThreadPoolShutdownTest) ... ok
> test_del_shutdown (__main__.ThreadPoolShutdownTest) ... ok
> test_run_after_shutdown (__main__.ThreadPoolShutdownTest) ... ok
> test_threads_terminate (__main__.ThreadPoolShutdownTest) ... ERROR
> 
> ==
> ERROR: test_map (__main__.ProcessPoolExecutorTest)
> --
> Traceback (most recent call last):
>   File "./test_futures.py", line 584, in setUp
> self.executor = futures.ProcessPoolExecutor(max_workers=1)
>   File "/«PKGBUILDDIR»/concurrent/futures/process.py", line 275, in __init__
> EXTRA_QUEUED_CALLS)
>   File "/usr/lib/python2.7/multiprocessing/__init__.py", line 218, in Queue
> return Queue(maxsize)
>   File "/usr/lib/python2.7/multiprocessing/queues.py", line 63, in __init__
> self._rlock = Lock

[Python-modules-team] Bug#680822: pyside: FTBFS: build-dependency not installable: libphonon-dev

[Lucas Nussbaum]

Source: pyside
Version: 1.1.1-3
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120708 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> ┌──┐
> │ Install pyside build dependencies (apt-based resolver)  
>  │
> └──┘
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> 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:
>  sbuild-build-depends-pyside-dummy : Depends: libphonon-dev but it is not 
> going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://people.debian.org/~lucas/logs/2012/07/08/pyside_1.1.1-3_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



___
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#680799: circuits: FTBFS: failed tests

[Lucas Nussbaum]

Source: circuits
Version: 1.6-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120708 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»'
> # Upstream is calling directly py.test inside a Popen so, for now, tests
> # are run only for the default version
> set -e; python setup.py test;
> running test
> running egg_info
> writing circuits.egg-info/PKG-INFO
> writing top-level names to circuits.egg-info/top_level.txt
> writing dependency_links to circuits.egg-info/dependency_links.txt
> writing entry points to circuits.egg-info/entry_points.txt
> writing manifest file 'circuits.egg-info/SOURCES.txt'
> reading manifest file 'circuits.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> writing manifest file 'circuits.egg-info/SOURCES.txt'
> running build_ext
> = test session starts 
> ==
> platform linux2 -- Python 2.7.3 -- pytest-2.2.4
> collecting ... collected 203 items
> 
> tests/app/test_config.py 
> tests/app/test_daemon.py .
> tests/app/test_env.py .
> tests/app/test_logger.py ..
> tests/core/test_all_channels.py .
> tests/core/test_bridge.py .
> tests/core/test_component_repr.py .
> tests/core/test_component_setup.py ...
> tests/core/test_core.py ..
> tests/core/test_debugger.py .
> tests/core/test_dynamic_handlers.py ..
> tests/core/test_errors.py .
> tests/core/test_event.py ...
> tests/core/test_event_serialization.py .
> tests/core/test_feedback.py ...
> tests/core/test_filter_order.py .
> tests/core/test_filters.py .
> tests/core/test_future.py 
> tests/core/test_generator_value.py ..
> tests/core/test_greenlet.py ...
> tests/core/test_inheritence.py ..
> tests/core/test_ipc.py .
> tests/core/test_loader.py .
> tests/core/test_manager_repr.py .
> tests/core/test_pools.py .
> tests/core/test_priority.py .
> tests/core/test_signals.py .
> tests/core/test_timers.py ...
> tests/core/test_utils.py .
> tests/core/test_value.py 
> tests/core/test_value_serialization.py .
> tests/core/test_workers.py .
> tests/io/test_io.py ...
> tests/io/test_notify.py .
> tests/net/test_client.py ...
> tests/net/test_imports.py .
> tests/net/test_pipe.py .
> tests/net/test_poller_reuse.py .
> tests/net/test_tcp.py 
> tests/net/test_udp.py ..
> tests/net/test_unix.py ...
> tests/net/protocols/test_irc.py ..
> tests/net/protocols/test_line.py ..
> tests/tools/test_tools.py 
> tests/web/test_basicauth.py .
> tests/web/test_client.py .
> tests/web/test_conn.py .
> tests/web/test_cookies.py .
> tests/web/test_core.py ..
> tests/web/test_digestauth.py .
> tests/web/test_encodings.py ..
> tests/web/test_exceptions.py ...
> tests/web/test_expires.py ..
> tests/web/test_expose.py .
> tests/web/test_future.py .
> tests/web/test_generator.py .
> tests/web/test_gzip.py .
> tests/web/test_http.py .
> tests/web/test_json.py ..
> tests/web/test_jsonrpc.py .
> tests/web/test_logger.py FFF
> tests/web/test_main.py .
> tests/web/test_multipartformdata.py .
> tests/web/test_null_response.py .
> tests/web/test_request_failure.py .
> tests/web/test_serve_download.py .
> tests/web/test_serve_file.py .
> tests/web/test_servers.py ...
> tests/web/test_sessions.py .
> tests/web/test_static.py .
> tests/web/test_unicode.py .
> tests/web/test_utils.py ..
> tests/web/test_value.py .
> tests/web/test_web_task.py .
> tests/web/test_websockets.py .
> tests/web/test_wsgi_application.py ..
> tests/web/test_wsgi_application_generator.py .
> tests/web/test_wsgi_application_yield.py .
> tests/web/test_wsgi_gateway.py .
> tests/web/test_wsgi_gateway_errors.py .
> tests/web/test_wsgi_gateway_generator.py .
> tests/web/test_wsgi_gateway_yield.py .
> tests/web/test_xmlrpc.py .
> tests/web/test_yield.py .
> 
> === FAILURES 
> ===
> __ test_file 
> ___
> 
> webapp = 
> 
> def test_file(webapp):
> logfile = StringIO()
> logger = Logger(file=logfile)
> logger.register(webapp)
> 
> f = urlopen(webapp.server.base)
> s = f.read()
> assert s == b"Hello World!"
> 
> logfile.seek(0)
> s = logfile.read().strip()
> 
> format = logger.format
> 
> try:
> address = gethostbyname('localhost')
> except gaierror:
> address = "127.0.0.1"
> 
> d = {}
> d["h"] = address
> d["l"] = "-"
> d["u"] = "-"
> d["r"] = "GET / HTTP/1.1"
> d["s"] = "200"
> d["b"] = "12"
> d["f"] = ""
> d["a"] = "Python-urllib/%s" % sys.version[:3]
> 
> keys = list(d.keys())
> 
> for k in keys:
> >   assert d[k] in s
>

[Python-modules-team] Bug#678792: python-scrapy: FTBFS: ImportError: cannot import name uses_query

[Lucas Nussbaum]

Source: python-scrapy
Version: 0.14.1-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120624 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»'
> dh_auto_clean
> Traceback (most recent call last):
>   File "setup.py", line 93, in 
> version = __import__('scrapy').__version__
>   File "/«PKGBUILDDIR»/scrapy/__init__.py", line 18, in 
> from scrapy.xlib import twisted_250_monkeypatches, urlparse_monkeypatches
>   File "/«PKGBUILDDIR»/scrapy/xlib/urlparse_monkeypatches.py", line 1, in 
> 
> from urlparse import urlparse, uses_netloc, uses_query
> ImportError: cannot import name uses_query
> dh_auto_clean: python setup.py clean -a returned exit code 1
> make[1]: *** [override_dh_auto_clean] Error 2

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2012/06/24/python-scrapy_0.14.1-1_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



___
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#678777: sorl-thumbnail: FTBFS: tests failed

[Lucas Nussbaum]

Source: sorl-thumbnail
Version: 11.12-3
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120624 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»'
> mkdir -p tmp-locales
> localedef -i en_US -c -f UTF-8 tmp-locales/en_US.UTF-8
> set -e; \
>   for python in python2.7 python2.6; do \
> for name in pil pgmagick imagemagick graphicsmagick; do \
>   LOCPATH=/«PKGBUILDDIR»/tmp-locales LC_ALL=en_US.UTF-8 
> PYTHONPATH=tests LOCAL_BUILD=1 $python tests/runtests.py 
> --settings=settings.$name ; \
> done; \
>   done
> .ss..
> --
> Ran 37 tests in 1.971s
> 
> OK (skipped=2)
> Running tests for 'settings.pil'
> Creating test database for alias 'default'...
> Destroying test database for alias 'default'...
> .F...ss..
> ==
> FAIL: test_orientation (thumbnail_tests.tests.TemplateTestCaseA)
> --
> Traceback (most recent call last):
>   File "/«PKGBUILDDIR»/tests/thumbnail_tests/tests.py", line 349, in 
> test_orientation
> self.assertEqual(exif.get(0x0112), 1)
> AssertionError: 2 != 1
> 
> --
> Ran 37 tests in 1.242s
> 
> FAILED (failures=1, skipped=2)
> Running tests for 'settings.pgmagick'
> Creating test database for alias 'default'...
> Destroying test database for alias 'default'...
> make[1]: *** [override_dh_auto_test] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2012/06/24/sorl-thumbnail_11.12-3_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



___
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#678754: pyth: FTBFS: tests failed

[Lucas Nussbaum]

Source: pyth
Version: 0.5.6-2
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120624 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»'
> set -e; \
>   for python in python2.6 python2.7; do \
>   $python /usr/bin/nosetests; \
>   done
> .FF...
> ==
> FAIL: Try to read a paragraph containing bold text
> --
> Traceback (most recent call last):
>   File "/«PKGBUILDDIR»/tests/test_readxhtml.py", line 45, in test_bold
> assert text['bold']
> AssertionError
> 
> ==
> FAIL: Try to read a paragraph containing italic text
> --
> Traceback (most recent call last):
>   File "/«PKGBUILDDIR»/tests/test_readxhtml.py", line 54, in test_italic
> assert text['italic']
> AssertionError
> 
> ==
> FAIL: Try to read a simple xhtml document containing tree paragraphs
> --
> Traceback (most recent call last):
>   File "/«PKGBUILDDIR»/tests/test_readxhtml.py", line 29, in test_paragraphs
> self.assert_(len(doc.content) == 3)
> AssertionError
> 
> ==
> FAIL: Try to read a paragraph containing subscript
> --
> Traceback (most recent call last):
>   File "/«PKGBUILDDIR»/tests/test_readxhtml.py", line 63, in test_sub
> assert text['sub']
> AssertionError
> 
> ==
> FAIL: Try to read a paragraph containing supscript
> --
> Traceback (most recent call last):
>   File "/«PKGBUILDDIR»/tests/test_readxhtml.py", line 72, in test_sup
> assert text['super']
> AssertionError
> 
> ==
> FAIL: Try to read a paragraph containing an url
> --
> Traceback (most recent call last):
>   File "/«PKGBUILDDIR»/tests/test_readxhtml.py", line 81, in test_url
> assert text['url'] == "http://google.com";
> AssertionError
> 
> --
> Ran 18 tests in 0.432s
> 
> FAILED (failures=6)
> make[1]: *** [override_dh_auto_test] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2012/06/24/pyth_0.5.6-2_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



___
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#676058: basemap: FTBFS: dh_sphinxdoc: Sphinx documentation not found

[Lucas Nussbaum]

Source: basemap
Version: 1.0.3+dfsg-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[1]: Entering directory `/«BUILDDIR»/basemap-1.0.3+dfsg'
> set -e ; \
>   for python in python2.6 python2.7; do \
>   $python setup.py install --prefix 
> /«BUILDDIR»/basemap-1.0.3+dfsg/debian/python-mpltoolkits.basemap/usr 
> --install-layout=deb; \
>   $python-dbg setup.py install --prefix 
> /«BUILDDIR»/basemap-1.0.3+dfsg/debian/python-mpltoolkits.basemap/usr 
> --install-layout=deb; \
>   done
> In file included from nad2bin.c:7:0:
> src/projects.h:434:1: warning: function declaration isn't a prototype 
> [-Wstrict-prototypes]
> nad2bin.c:46:13: warning: function declaration isn't a prototype 
> [-Wstrict-prototypes]
> In file included from src/pj_malloc.c:5:0:
> src/projects.h:434:1: warning: function declaration isn't a prototype 
> [-Wstrict-prototypes]
> checking for GEOS lib in /sbuild-nonexistent 
> checking for GEOS lib in /usr 
> GEOS lib (version 3.3.3) found in /usr
> running install
> running build
> running config_cc
> unifing config_cc, config, build_clib, build_ext, build commands --compiler 
> options
> running config_fc
> unifing config_fc, config, build_clib, build_ext, build commands --fcompiler 
> options
> running build_src
> build_src
> building extension "mpl_toolkits.basemap._proj" sources
> building extension "_geoslib" sources
> build_src: building npy-pkg config files
> running build_py
> running build_ext
> customize UnixCCompiler
> customize UnixCCompiler using build_ext
> running scons
> running install_lib
> creating /«BUILDDIR»/basemap-1.0.3+dfsg/debian/python-mpltoolkits.basemap/usr
> creating 
> /«BUILDDIR»/basemap-1.0.3+dfsg/debian/python-mpltoolkits.basemap/usr/lib
> creating 
> /«BUILDDIR»/basemap-1.0.3+dfsg/debian/python-mpltoolkits.basemap/usr/lib/python2.6
> creating 
> /«BUILDDIR»/basemap-1.0.3+dfsg/debian/python-mpltoolkits.basemap/usr/lib/python2.6/dist-packages
> copying build/lib.linux-x86_64-2.6/_geoslib.so -> 
> /«BUILDDIR»/basemap-1.0.3+dfsg/debian/python-mpltoolkits.basemap/usr/lib/python2.6/dist-packages
> creating 
> /«BUILDDIR»/basemap-1.0.3+dfsg/debian/python-mpltoolkits.basemap/usr/lib/python2.6/dist-packages/mpl_toolkits
> creating 
> /«BUILDDIR»/basemap-1.0.3+dfsg/debian/python-mpltoolkits.basemap/usr/lib/python2.6/dist-packages/mpl_toolkits/basemap
> copying build/lib.linux-x86_64-2.6/mpl_toolkits/basemap/_proj.so -> 
> /«BUILDDIR»/basemap-1.0.3+dfsg/debian/python-mpltoolkits.basemap/usr/lib/python2.6/dist-packages/mpl_toolkits/basemap
> copying build/lib.linux-x86_64-2.6/mpl_toolkits/basemap/accumulator.py -> 
> /«BUILDDIR»/basemap-1.0.3+dfsg/debian/python-mpltoolkits.basemap/usr/lib/python2.6/dist-packages/mpl_toolkits/basemap
> copying build/lib.linux-x86_64-2.6/mpl_toolkits/basemap/cm.py -> 
> /«BUILDDIR»/basemap-1.0.3+dfsg/debian/python-mpltoolkits.basemap/usr/lib/python2.6/dist-packages/mpl_toolkits/basemap
> copying build/lib.linux-x86_64-2.6/mpl_toolkits/basemap/constants.py -> 
> /«BUILDDIR»/basemap-1.0.3+dfsg/debian/python-mpltoolkits.basemap/usr/lib/python2.6/dist-packages/mpl_toolkits/basemap
> copying build/lib.linux-x86_64-2.6/mpl_toolkits/basemap/geodesic.py -> 
> /«BUILDDIR»/basemap-1.0.3+dfsg/debian/python-mpltoolkits.basemap/usr/lib/python2.6/dist-packages/mpl_toolkits/basemap
> copying build/lib.linux-x86_64-2.6/mpl_toolkits/basemap/geodesiccapability.py 
> -> 
> /«BUILDDIR»/basemap-1.0.3+dfsg/debian/python-mpltoolkits.basemap/usr/lib/python2.6/dist-packages/mpl_toolkits/basemap
> copying build/lib.linux-x86_64-2.6/mpl_toolkits/basemap/geodesicline.py -> 
> /«BUILDDIR»/basemap-1.0.3+dfsg/debian/python-mpltoolkits.basemap/usr/lib/python2.6/dist-packages/mpl_toolkits/basemap
> copying build/lib.linux-x86_64-2.6/mpl_toolkits/basemap/geomath.py -> 
> /«BUILDDIR»/basemap-1.0.3+dfsg/debian/python-mpltoolkits.basemap/usr/lib/python2.6/dist-packages/mpl_toolkits/basemap
> copying build/lib.linux-x86_64-2.6/mpl_toolkits/basemap/polygonarea.py -> 
> /«BUILDDIR»/basemap-1.0.3+dfsg/debian/python-mpltoolkits.basemap/usr/lib/python2.6/dist-packages/mpl_toolkits/basemap
> copying build/lib.linux-x86_64-2.6/mpl_toolkits/basemap/proj.py -> 
> /«BUILDDIR»/basemap-1.0.3+dfsg/debian/python-mpltoolkits.basemap/usr/lib/python2.6/dist-packages/mpl_toolkits/basemap
> copying build/lib.linux-x86_64-2.6/mpl_toolkits/basemap/shapefile.py -> 
> /«BUILDDIR»/basemap-1.0.3+dfsg/debian/python-mpltoolkits.basemap/usr/lib/python2.6/dist-packages/mpl_toolkits/basemap
> copying build/lib.linux-x86_64-2.6/mpl_toolkits/basemap/solar.py -> 
> /«BUILDDIR»/basemap-1.0.3+dfsg/debian/python-mpltoolkits.basemap/usr/lib/python2.6/dist-packages/mpl_toolkits/basemap
> copying build/lib.linux-x86_64-2.6/mpl_toolkits/basemap/test.py -> 
> /«BUILDDIR»/basemap-1.0

[Python-modules-team] Bug#674351: python-notify2: FTBFS: test failed

[Lucas Nussbaum]

Source: python-notify2
Version: 0.3-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120524 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»'
> PYTHONS="2.6 2.7 3.2" xvfb-run -a debian/runtests.sh
> E
> ==
> ERROR: test_get_server_caps (__main__.ModuleTests)
> --
> Traceback (most recent call last):
>   File "test_notify2.py", line 17, in setUp
> notify2.init("notify2 test suite")
>   File "/«PKGBUILDDIR»/notify2.py", line 93, in init
> bus = dbus.SessionBus(mainloop=mainloop)
>   File "/usr/lib/python2.6/dist-packages/dbus/_dbus.py", line 211, in __new__
> mainloop=mainloop)
>   File "/usr/lib/python2.6/dist-packages/dbus/_dbus.py", line 100, in __new__
> bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
>   File "/usr/lib/python2.6/dist-packages/dbus/bus.py", line 122, in __new__
> bus = cls._new_for_bus(address_or_type, mainloop=mainloop)
> DBusException: org.freedesktop.DBus.Error.NoServer: Failed to connect to 
> socket /tmp/dbus-3P8u71Q8XL: Connection refused
> 
> ==
> ERROR: test_get_server_info (__main__.ModuleTests)
> --
> Traceback (most recent call last):
>   File "test_notify2.py", line 17, in setUp
> notify2.init("notify2 test suite")
>   File "/«PKGBUILDDIR»/notify2.py", line 93, in init
> bus = dbus.SessionBus(mainloop=mainloop)
>   File "/usr/lib/python2.6/dist-packages/dbus/_dbus.py", line 211, in __new__
> mainloop=mainloop)
>   File "/usr/lib/python2.6/dist-packages/dbus/_dbus.py", line 100, in __new__
> bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
>   File "/usr/lib/python2.6/dist-packages/dbus/bus.py", line 122, in __new__
> bus = cls._new_for_bus(address_or_type, mainloop=mainloop)
> DBusException: org.freedesktop.DBus.Error.NoServer: Failed to connect to 
> socket /tmp/dbus-3P8u71Q8XL: Connection refused
> 
> ==
> ERROR: test_init_uninit (__main__.ModuleTests)
> --
> Traceback (most recent call last):
>   File "test_notify2.py", line 17, in setUp
> notify2.init("notify2 test suite")
>   File "/«PKGBUILDDIR»/notify2.py", line 93, in init
> bus = dbus.SessionBus(mainloop=mainloop)
>   File "/usr/lib/python2.6/dist-packages/dbus/_dbus.py", line 211, in __new__
> mainloop=mainloop)
>   File "/usr/lib/python2.6/dist-packages/dbus/_dbus.py", line 100, in __new__
> bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
>   File "/usr/lib/python2.6/dist-packages/dbus/bus.py", line 122, in __new__
> bus = cls._new_for_bus(address_or_type, mainloop=mainloop)
> DBusException: org.freedesktop.DBus.Error.NoServer: Failed to connect to 
> socket /tmp/dbus-3P8u71Q8XL: Connection refused
> 
> ==
> ERROR: test_basic (__main__.NotificationTests)
> --
> Traceback (most recent call last):
>   File "test_notify2.py", line 38, in setUp
> notify2.init("notify2 test suite")
>   File "/«PKGBUILDDIR»/notify2.py", line 93, in init
> bus = dbus.SessionBus(mainloop=mainloop)
>   File "/usr/lib/python2.6/dist-packages/dbus/_dbus.py", line 211, in __new__
> mainloop=mainloop)
>   File "/usr/lib/python2.6/dist-packages/dbus/_dbus.py", line 100, in __new__
> bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
>   File "/usr/lib/python2.6/dist-packages/dbus/bus.py", line 122, in __new__
> bus = cls._new_for_bus(address_or_type, mainloop=mainloop)
> DBusException: org.freedesktop.DBus.Error.NoServer: Failed to connect to 
> socket /tmp/dbus-3P8u71Q8XL: Connection refused
> 
> ==
> ERROR: test_category (__main__.NotificationTests)
> --
> Traceback (most recent call last):
>   File "test_notify2.py", line 38, in setUp
> notify2.init("notify2 test suite")
>   File "/«PKGBUILDDIR»/notify2.py", line 93, in init
> bus = dbus.SessionBus(mainloop=mainloop)
>   File "/usr/lib/python2.6/dist-packages/dbus/_dbus.py", line 211, in __new__
> mainloop=mainloop)
>   File "/usr/lib/python2.6/dist-packages/dbus/_dbus.py", line 100, in __new__
> bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
>   File "/usr/lib/python2.6/dist-packages/dbus/bus.py", line 122, in __new__
> bus = cls._new_for_bus(addre

[Python-modules-team] Bug#674307: python-enable: FTBFS: numpy.distutils.system_info.X11NotFoundError: X11 libraries not found.

[Lucas Nussbaum]

Source: python-enable
Version: 4.1.0-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120524 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  debian/rules build
> test -x debian/rules
> mkdir -p "."
> /usr/share/cdbs/1/rules/buildcore.mk:109: WARNING:  DEB_COMPRESS_EXCLUDE is a 
> deprecated variable
> mkdir -p debian/python-module-stampdir
> set -e; for buildver in 2.7 2.6; do \
>   cd /«PKGBUILDDIR» && cd . && \
>   python$buildver setup.py build \
>   --build-base="/«PKGBUILDDIR»/./build"; \
>   done
> /usr/lib/pymodules/python2.7/numpy/distutils/system_info.py:538: UserWarning: 
> Specified path /usr/local/include/python2.7 is invalid.
>   warnings.warn('Specified path %s is invalid.' % d)
> /usr/lib/pymodules/python2.7/numpy/distutils/system_info.py:538: UserWarning: 
> Specified path  is invalid.
>   warnings.warn('Specified path %s is invalid.' % d)
> /usr/lib/pymodules/python2.7/numpy/distutils/system_info.py:538: UserWarning: 
> Specified path /usr/X11R6/lib64 is invalid.
>   warnings.warn('Specified path %s is invalid.' % d)
> /usr/lib/pymodules/python2.7/numpy/distutils/system_info.py:538: UserWarning: 
> Specified path /usr/X11R6/lib is invalid.
>   warnings.warn('Specified path %s is invalid.' % d)
> /usr/lib/pymodules/python2.7/numpy/distutils/system_info.py:538: UserWarning: 
> Specified path /usr/X11/lib64 is invalid.
>   warnings.warn('Specified path %s is invalid.' % d)
> /usr/lib/pymodules/python2.7/numpy/distutils/system_info.py:538: UserWarning: 
> Specified path /usr/X11/lib is invalid.
>   warnings.warn('Specified path %s is invalid.' % d)
> /usr/lib/pymodules/python2.7/numpy/distutils/system_info.py:538: UserWarning: 
> Specified path /usr/lib64 is invalid.
>   warnings.warn('Specified path %s is invalid.' % d)
> /usr/lib/pymodules/python2.7/numpy/distutils/system_info.py:538: UserWarning: 
> Specified path /usr/X11R6/include is invalid.
>   warnings.warn('Specified path %s is invalid.' % d)
> /usr/lib/pymodules/python2.7/numpy/distutils/system_info.py:538: UserWarning: 
> Specified path /usr/X11/include is invalid.
>   warnings.warn('Specified path %s is invalid.' % d)
> Traceback (most recent call last):
>   File "setup.py", line 56, in 
> config = configuration().todict()
>   File "setup.py", line 48, in configuration
> config.add_subpackage('kiva')
>   File "/usr/lib/pymodules/python2.7/numpy/distutils/misc_util.py", line 
> 1002, in add_subpackage
> caller_level = 2)
>   File "/usr/lib/pymodules/python2.7/numpy/distutils/misc_util.py", line 971, 
> in get_subpackage
> caller_level = caller_level + 1)
>   File "/usr/lib/pymodules/python2.7/numpy/distutils/misc_util.py", line 908, 
> in _get_configuration_from_setup_py
> config = setup_module.configuration(*args)
>   File "kiva/setup.py", line 27, in configuration
> config.add_subpackage('agg')
>   File "/usr/lib/pymodules/python2.7/numpy/distutils/misc_util.py", line 
> 1002, in add_subpackage
> caller_level = 2)
>   File "/usr/lib/pymodules/python2.7/numpy/distutils/misc_util.py", line 971, 
> in get_subpackage
> caller_level = caller_level + 1)
>   File "/usr/lib/pymodules/python2.7/numpy/distutils/misc_util.py", line 908, 
> in _get_configuration_from_setup_py
> config = setup_module.configuration(*args)
>   File "kiva/agg/setup.py", line 148, in configuration
> x11_info = get_info('x11', notfound_action=2)
>   File "/usr/lib/pymodules/python2.7/numpy/distutils/system_info.py", line 
> 321, in get_info
> return cl().get_info(notfound_action)
>   File "/usr/lib/pymodules/python2.7/numpy/distutils/system_info.py", line 
> 472, in get_info
> raise self.notfounderror(self.notfounderror.__doc__)
> numpy.distutils.system_info.X11NotFoundError: X11 libraries not found.
> make: *** [debian/python-module-stampdir/python-enable] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2012/05/24/python-enable_4.1.0-1_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.



___
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#669549: matplotlib: FTBFS: cp: cannot stat `doc/build/latex/Matplotlib.pdf': No such file or directory

[Lucas Nussbaum]

Source: matplotlib
Version: 1.1.1~rc1-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120419 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  fakeroot debian/rules binary
> dh_testdir -i
> dh_testroot -i
> dh_prep
> dh_install -p python-matplotlib-data
> rm -fr 
> /«PKGBUILDDIR»/debian/python-matplotlib-data/usr/share/matplotlib/mpl-data/fonts/ttf/Vera*.ttf
> rm -fr 
> /«PKGBUILDDIR»/debian/python-matplotlib-data/usr/share/matplotlib/mpl-data/fonts/ttf/*.TXT
> rm -fr 
> /«PKGBUILDDIR»/debian/python-matplotlib-data/usr/share/matplotlib/mpl-data/fonts/ttf/local.conf
> rm -fr 
> /«PKGBUILDDIR»/debian/python-matplotlib-data/usr/share/matplotlib/mpl-data/fonts/pdfcorefonts/readme.txt
> chmod 644 
> /«PKGBUILDDIR»/debian/python-matplotlib-data/usr/share/matplotlib/mpl-data/images/*.svg
> # link to fonts in ttf-lyx
> ln -sf /usr/share/fonts/truetype/ttf-lyx/cmex10.ttf 
> /«PKGBUILDDIR»/debian/python-matplotlib-data/usr/share/matplotlib/mpl-data/fonts/ttf/cmex10.ttf
> ln -sf /usr/share/fonts/truetype/ttf-lyx/cmmi10.ttf 
> /«PKGBUILDDIR»/debian/python-matplotlib-data/usr/share/matplotlib/mpl-data/fonts/ttf/cmmi10.ttf
> ln -sf /usr/share/fonts/truetype/ttf-lyx/cmr10.ttf 
> /«PKGBUILDDIR»/debian/python-matplotlib-data/usr/share/matplotlib/mpl-data/fonts/ttf/cmr10.ttf
> ln -sf /usr/share/fonts/truetype/ttf-lyx/cmsy10.ttf 
> /«PKGBUILDDIR»/debian/python-matplotlib-data/usr/share/matplotlib/mpl-data/fonts/ttf/cmsy10.ttf
> dh_testdir -i
> dh_testroot -i
> dh_installchangelogs -i CHANGELOG
> dh_installdocs -ppython-matplotlib-doc -i doc/build/html/ 
> doc/build/latex/Matplotlib.pdf
> cp: cannot stat `doc/build/latex/Matplotlib.pdf': No such file or directory
> dh_installdocs: cp -a doc/build/latex/Matplotlib.pdf 
> debian/python-matplotlib-doc/usr/share/doc/python-matplotlib-doc returned 
> exit code 1
> make: *** [binary-indep] Error 2

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2012/04/19/matplotlib_1.1.1~rc1-1_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.



___
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#669493: django-picklefield: FTBFS: django.core.exceptions.ImproperlyConfigured: settings.DATABASES is improperly configured. Please supply the ENGINE value. Check settings do

[Lucas Nussbaum]

Source: django-picklefield
Version: 0.2.0-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120419 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»'
> django-admin startproject testproject
> echo 'DATABASE_ENGINE = "sqlite3"' > testproject/settings.py
> echo 'INSTALLED_APPS = ["picklefield"]' >> testproject/settings.py
> set -e; \
>   for python in python2.7 python2.6; do \
> PYTHONPATH=".:src" $python testproject/manage.py test 
> --settings=testproject.settings; \
>   done
> Creating test database for alias 'default'...
> Traceback (most recent call last):
>   File "testproject/manage.py", line 10, in 
> execute_from_command_line(sys.argv)
>   File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", 
> line 443, in execute_from_command_line
> utility.execute()
>   File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", 
> line 382, in execute
> self.fetch_command(subcommand).run_from_argv(self.argv)
>   File 
> "/usr/lib/python2.7/dist-packages/django/core/management/commands/test.py", 
> line 49, in run_from_argv
> super(Command, self).run_from_argv(argv)
>   File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", 
> line 196, in run_from_argv
> self.execute(*args, **options.__dict__)
>   File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", 
> line 232, in execute
> output = self.handle(*args, **options)
>   File 
> "/usr/lib/python2.7/dist-packages/django/core/management/commands/test.py", 
> line 72, in handle
> failures = test_runner.run_tests(test_labels)
>   File "/usr/lib/python2.7/dist-packages/django/test/simple.py", line 381, in 
> run_tests
> old_config = self.setup_databases()
>   File "/usr/lib/python2.7/dist-packages/django/test/simple.py", line 317, in 
> setup_databases
> self.verbosity, autoclobber=not self.interactive)
>   File "/usr/lib/python2.7/dist-packages/django/db/backends/creation.py", 
> line 256, in create_test_db
> self._create_test_db(verbosity, autoclobber)
>   File "/usr/lib/python2.7/dist-packages/django/db/backends/creation.py", 
> line 321, in _create_test_db
> cursor = self.connection.cursor()
>   File "/usr/lib/python2.7/dist-packages/django/db/backends/dummy/base.py", 
> line 15, in complain
> raise ImproperlyConfigured("settings.DATABASES is improperly configured. "
> django.core.exceptions.ImproperlyConfigured: settings.DATABASES is improperly 
> configured. Please supply the ENGINE value. Check settings documentation for 
> more details.
> make[1]: *** [override_dh_auto_test] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2012/04/19/django-picklefield_0.2.0-1_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team