Source: turbomail
Version: 2.1-2
Severity: serious
User: [email protected]
Usertags: qa-ftbfs-20091210 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 
> `/build/user-turbomail_2.1-2-amd64-3Rr1KO/turbomail-2.1'
> make[1]: Nothing to be done for `update-config'.
> make[1]: Leaving directory 
> `/build/user-turbomail_2.1-2-amd64-3Rr1KO/turbomail-2.1'
> cd . && python setup.py build 
> --build-base="/build/user-turbomail_2.1-2-amd64-3Rr1KO/turbomail-2.1/./build"
> Traceback (most recent call last):
>   File "setup.py", line 6, in <module>
>     from turbogears.finddata import find_package_data
>   File "/usr/lib/pymodules/python2.5/turbogears/__init__.py", line 6, in 
> <module>
>     from turbogears.controllers import (absolute_url, expose, flash, validate,
>   File "/usr/lib/pymodules/python2.5/turbogears/controllers.py", line 18, in 
> <module>
>     from turbogears import view, database, errorhandling, config
>   File "/usr/lib/pymodules/python2.5/turbogears/view/__init__.py", line 1, in 
> <module>
>     from turbogears.view import base
>   File "/usr/lib/pymodules/python2.5/turbogears/view/base.py", line 22, in 
> <module>
>     import genshi
> ImportError: No module named genshi
> make: *** [debian/python-module-stampdir/python-turbomail] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2009/12/10/turbomail_2.1-2_lsid64.buildlog

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.

-- 
| Lucas Nussbaum
| [email protected]   http://www.lucas-nussbaum.net/ |
| jabber: [email protected]             GPG: 1024D/023B3F4F |



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to