Source: python-csa
Version: 0.0.4-1.1
Severity: serious
Tags: wheezy sid
User: [email protected]
Usertags: qa-ftbfs-20120321 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 clean
> dh clean
> dh_testdir
> dh_auto_clean
> Traceback (most recent call last):
> File "setup.py", line 4, in <module>
> from csa.version import __version__
> File "/«PKGBUILDDIR»/csa/__init__.py", line 25, in <module>
> from plot import *
> File "/«PKGBUILDDIR»/csa/plot.py", line 20, in <module>
> import matplotlib
> File "/usr/lib/pymodules/python2.6/matplotlib/__init__.py", line 767, in
> <module>
> rcParams = rc_params()
> File "/usr/lib/pymodules/python2.6/matplotlib/__init__.py", line 685, in
> rc_params
> fname = matplotlib_fname()
> File "/usr/lib/pymodules/python2.6/matplotlib/__init__.py", line 597, in
> matplotlib_fname
> fname = os.path.join(get_configdir(), 'matplotlibrc')
> File "/usr/lib/pymodules/python2.6/matplotlib/__init__.py", line 246, in
> wrapper
> ret = func(*args, **kwargs)
> File "/usr/lib/pymodules/python2.6/matplotlib/__init__.py", line 471, in
> _get_configdir
> raise RuntimeError("Failed to create %s/.matplotlib; consider setting
> MPLCONFIGDIR to a writable directory for matplotlib configuration data"%h)
> RuntimeError: Failed to create /sbuild-nonexistent/.matplotlib; consider
> setting MPLCONFIGDIR to a writable directory for matplotlib configuration data
> dh_auto_clean: python2.6 setup.py clean -a returned exit code 1
> make: *** [clean] Error 1
The full build log is available from:
http://people.debian.org/~lucas/logs/2012/03/21/python-csa_0.0.4-1.1.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.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]