Source: dff
Version: 1.2.0+dfsg.1-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120724 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[4]: Entering directory `/«BUILDDIR»/dff-1.2.0+dfsg.1/build-2.7'
> cd /«BUILDDIR»/dff-1.2.0+dfsg.1/build-2.7 && /usr/bin/cmake -E cmake_depends 
> "Unix Makefiles" /«BUILDDIR»/dff-1.2.0+dfsg.1 
> /«BUILDDIR»/dff-1.2.0+dfsg.1/ui/gui/resources 
> /«BUILDDIR»/dff-1.2.0+dfsg.1/build-2.7 
> /«BUILDDIR»/dff-1.2.0+dfsg.1/build-2.7/ui/gui/resources 
> /«BUILDDIR»/dff-1.2.0+dfsg.1/build-2.7/ui/gui/resources/CMakeFiles/ui_resources.about.ui.dir/DependInfo.cmake
>  --color=
> Scanning dependencies of target ui_resources.about.ui
> make[4]: Leaving directory `/«BUILDDIR»/dff-1.2.0+dfsg.1/build-2.7'
> make -f ui/gui/resources/CMakeFiles/ui_resources.about.ui.dir/build.make 
> ui/gui/resources/CMakeFiles/ui_resources.about.ui.dir/build
> make[4]: Entering directory `/«BUILDDIR»/dff-1.2.0+dfsg.1/build-2.7'
> cd /«BUILDDIR»/dff-1.2.0+dfsg.1/build-2.7/ui/gui/resources && /usr/bin/pyuic4 
> -o /«BUILDDIR»/dff-1.2.0+dfsg.1/build-2.7/ui/gui/resources/ui_about.py 
> /«BUILDDIR»/dff-1.2.0+dfsg.1/ui/gui/resources/about.ui
> /bin/sh: 1: /usr/bin/pyuic4: not found
> make[4]: *** [ui/gui/resources/CMakeFiles/ui_resources.about.ui] Error 127

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2012/07/24/dff_1.2.0+dfsg.1-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.


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to