Source: mypaint Version: 1.1.0-3 Severity: serious Tags: jessie sid User: [email protected] Usertags: qa-ftbfs-20140628 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): > msgfmt po/ru.po -o po/ru/LC_MESSAGES/mypaint.mo > msgfmt po/sl.po -o po/sl/LC_MESSAGES/mypaint.mo > msgfmt po/sv.po -o po/sv/LC_MESSAGES/mypaint.mo > msgfmt po/uk.po -o po/uk/LC_MESSAGES/mypaint.mo > msgfmt po/zh_CN.po -o po/zh_CN/LC_MESSAGES/mypaint.mo > msgfmt po/zh_TW.po -o po/zh_TW/LC_MESSAGES/mypaint.mo > scons: done building targets. > # Max-RSS: ~74000 kbytes > MPLCONFIGDIR=`mktemp -d` python tests/test_mypaintlib.py > Traceback (most recent call last): > File "tests/test_mypaintlib.py", line 2, in <module> > from pylab import * > File "/usr/lib/pymodules/python2.7/pylab.py", line 1, in <module> > from matplotlib.pylab import * > File "/usr/lib/pymodules/python2.7/matplotlib/pylab.py", line 269, in > <module> > from matplotlib.pyplot import * > File "/usr/lib/pymodules/python2.7/matplotlib/pyplot.py", line 98, in > <module> > _backend_mod, new_figure_manager, draw_if_interactive, _show = > pylab_setup() > File "/usr/lib/pymodules/python2.7/matplotlib/backends/__init__.py", line > 28, in pylab_setup > globals(),locals(),[backend_name],0) > File "/usr/lib/pymodules/python2.7/matplotlib/backends/backend_tkagg.py", > line 11, in <module> > import matplotlib.backends.tkagg as tkagg > File "/usr/lib/pymodules/python2.7/matplotlib/backends/tkagg.py", line 2, > in <module> > from matplotlib.backends import _tkagg > ImportError: cannot import name _tkagg > debian/rules:32: recipe for target 'build-stamp' failed > make: *** [build-stamp] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/06/28/mypaint_1.1.0-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. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
