[Python-modules-team] Bug#707425: cairosvg: FTBFS: ImportError: No module named 'cairo._cairo'

Lucas Nussbaum lucas at lucas-nussbaum.net
Thu May 9 08:23:39 UTC 2013


Source: cairosvg
Version: 0.4.3-1
Severity: serious
Tags: jessie sid
User: debian-qa at 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 <module>
>     from cairosvg import VERSION
>   File "/«PKGBUILDDIR»/cairosvg/__init__.py", line 27, in <module>
>     from . import surface
>   File "/«PKGBUILDDIR»/cairosvg/surface/__init__.py", line 23, in <module>
>     import cairo
>   File "/usr/lib/python3/dist-packages/cairo/__init__.py", line 18, in <module>
>     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.



More information about the Python-modules-team mailing list