Source: python-paver
Version: 1.0.2-1
Severity: serious
Tags: squeeze sid
User: [email protected]
Usertags: qa-ftbfs-20100624 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-python-paver_1.0.2-1-amd64-7S0dBm/python-paver-1.0.2'
> dh_installchangelogs docs/source/changelog.rst
> make[1]: Leaving directory 
> `/build/user-python-paver_1.0.2-1-amd64-7S0dBm/python-paver-1.0.2'
>    dh_installexamples
>    dh_installman
>    dh_installcatalogs
>    dh_installcron
>    dh_installdebconf
>    dh_installemacsen
>    dh_installifupdown
>    dh_installinfo
>    dh_pysupport
>    dh_installinit
>    dh_installmenu
>    dh_installmime
>    dh_installmodules
>    dh_installlogcheck
>    dh_installlogrotate
>    dh_installpam
>    dh_installppp
>    dh_installudev
>    dh_installwm
>    dh_installxfonts
>    dh_bugfiles
>    dh_lintian
>    dh_gconf
>    dh_icons
>    dh_perl
>    dh_usrlocal
> dh_usrlocal: debian/python-paver/usr/local/bin/paver is not a directory
> rmdir: failed to remove `debian/python-paver/usr/local/bin': Directory not 
> empty
> dh_usrlocal: rmdir debian/python-paver/usr/local/bin returned exit code 1
> make: *** [binary] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2010/06/24/python-paver_1.0.2-1_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 |



_______________________________________________
Python-modules-team mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team

Reply via email to