Source: liblastfm
Version: 0.4.0~git20090710-1
Severity: serious
Tags: wheezy sid
User: [email protected]
Usertags: qa-ftbfs-20120604 qa-ftbfs
User: [email protected]
Usertags: default19
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  debian/rules build
> dh_testdir
> ./configure --release --prefix /usr --no-strip
> ==> Configuring liblastfm-0.4.0... 
> Using /usr/bin/qmake
> ==> Determining installation prefix 
> Will install to: /usr
> ==> Generating Build System 
> ==> Generating .qmake.env 
> ==> Running qpp... 
> /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load 
> such file -- admin/findsrc (LoadError)
>       from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>       from admin/qpp:7:in `<main>'
> /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load 
> such file -- admin/findsrc (LoadError)
>       from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>       from admin/qpp:7:in `<main>'
> ==> Configuring qmake... 
> ==> Generating Makefile... 
> /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load 
> such file -- admin/platform.rb (LoadError)
>       from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>       from admin/Makefile.rb:9:in `<main>'
> 
> Good, your configure is finished! Now type: make
> touch config-stamp
> dh_testdir
> # Add here commands to compile the package.
> /usr/bin/make headers __src __fingerprint
> make[1]: Entering directory `/«PKGBUILDDIR»'
> make[1]: *** No rule to make target `headers'.  Stop.
> make[1]: Leaving directory `/«PKGBUILDDIR»'
> make: *** [build-stamp] Error 2

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2012/06/04/liblastfm_0.4.0~git20090710-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 [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to