Source: libvpx
Version: 1.3.0-2.1
Severity: serious
Tags: jessie sid
User: [email protected]
Usertags: qa-ftbfs-20140926 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/«PKGBUILDDIR»/builddir'
> mkdir -p vpx-vp8-vp9-nodocs-x86_64-linux-v1.3.0/include/vpx/
> cp -p /«PKGBUILDDIR»/vpx/vp8.h 
> vpx-vp8-vp9-nodocs-x86_64-linux-v1.3.0/include/vpx/vp8.h
> mkdir -p vpx-vp8-vp9-nodocs-x86_64-linux-v1.3.0/include/vpx/
> cp -p /«PKGBUILDDIR»/vpx/vp8cx.h 
> vpx-vp8-vp9-nodocs-x86_64-linux-v1.3.0/include/vpx/vp8cx.h
> mkdir -p vpx-vp8-vp9-nodocs-x86_64-linux-v1.3.0/include/vpx/
> cp -p /«PKGBUILDDIR»/vpx/vp8dx.h 
> vpx-vp8-vp9-nodocs-x86_64-linux-v1.3.0/include/vpx/vp8dx.h
> mkdir -p vpx-vp8-vp9-nodocs-x86_64-linux-v1.3.0/include/vpx/
> cp -p /«PKGBUILDDIR»/vpx/svc_context.h 
> vpx-vp8-vp9-nodocs-x86_64-linux-v1.3.0/include/vpx/svc_context.h
> mkdir -p vpx-vp8-vp9-nodocs-x86_64-linux-v1.3.0/include/vpx/
> cp -p /«PKGBUILDDIR»/vpx/vpx_codec.h 
> vpx-vp8-vp9-nodocs-x86_64-linux-v1.3.0/include/vpx/vpx_codec.h
> mkdir -p vpx-vp8-vp9-nodocs-x86_64-linux-v1.3.0/include/vpx/
> cp -p /«PKGBUILDDIR»/vpx/vpx_image.h 
> vpx-vp8-vp9-nodocs-x86_64-linux-v1.3.0/include/vpx/vpx_image.h
> mkdir -p vpx-vp8-vp9-nodocs-x86_64-linux-v1.3.0/include/vpx/
> cp -p /«PKGBUILDDIR»/vpx/vpx_integer.h 
> vpx-vp8-vp9-nodocs-x86_64-linux-v1.3.0/include/vpx/vpx_integer.h
> mkdir -p vpx-vp8-vp9-nodocs-x86_64-linux-v1.3.0/include/vpx/
> cp -p /«PKGBUILDDIR»/vpx/vpx_decoder.h 
> vpx-vp8-vp9-nodocs-x86_64-linux-v1.3.0/include/vpx/vpx_decoder.h
> mkdir -p vpx-vp8-vp9-nodocs-x86_64-linux-v1.3.0/include/vpx/
> cp -p /«PKGBUILDDIR»/vpx/vpx_encoder.h 
> vpx-vp8-vp9-nodocs-x86_64-linux-v1.3.0/include/vpx/vpx_encoder.h
> mkdir -p vpx-vp8-vp9-nodocs-x86_64-linux-v1.3.0/lib/
> cp -p libvpx.a vpx-vp8-vp9-nodocs-x86_64-linux-v1.3.0/lib/libvpx.a
>     [LN]      libvpx.so.1.3.0 
> vpx-vp8-vp9-nodocs-x86_64-linux-v1.3.0/lib/libvpx.so
> mkdir -p vpx-vp8-vp9-nodocs-x86_64-linux-v1.3.0/lib/
> ln -sf  libvpx.so.1.3.0 vpx-vp8-vp9-nodocs-x86_64-linux-v1.3.0/lib/libvpx.so
>     [LN]      libvpx.so.1.3.0 
> vpx-vp8-vp9-nodocs-x86_64-linux-v1.3.0/lib/libvpx.so.1
> mkdir -p vpx-vp8-vp9-nodocs-x86_64-linux-v1.3.0/lib/
> ln -sf  libvpx.so.1.3.0 vpx-vp8-vp9-nodocs-x86_64-linux-v1.3.0/lib/libvpx.so.1
>     [LN]      libvpx.so.1.3.0 
> vpx-vp8-vp9-nodocs-x86_64-linux-v1.3.0/lib/libvpx.so.1.3
> mkdir -p vpx-vp8-vp9-nodocs-x86_64-linux-v1.3.0/lib/
> ln -sf  libvpx.so.1.3.0 
> vpx-vp8-vp9-nodocs-x86_64-linux-v1.3.0/lib/libvpx.so.1.3
> mkdir -p vpx-vp8-vp9-nodocs-x86_64-linux-v1.3.0/lib/
> cp -p libvpx.so.1.3.0 
> vpx-vp8-vp9-nodocs-x86_64-linux-v1.3.0/lib/libvpx.so.1.3.0
> mkdir -p vpx-vp8-vp9-nodocs-x86_64-linux-v1.3.0/lib/pkgconfig/
> cp -p vpx.pc vpx-vp8-vp9-nodocs-x86_64-linux-v1.3.0/lib/pkgconfig/vpx.pc
> make[2]: Nothing to be done for 'dist'.
> make[2]: Nothing to be done for 'dist'.
>     [MD5SUM] vpx-vp8-vp9-nodocs-x86_64-linux-v1.3.0
> make[1]: Leaving directory '/«PKGBUILDDIR»/builddir'
> # don't use stripped library...
> cp -v /«PKGBUILDDIR»/builddir/libvpx_g.a \
>   /«PKGBUILDDIR»/builddir/vpx-vp8-*/lib/libvpx.a
> '/«PKGBUILDDIR»/builddir/libvpx_g.a' -> 
> '/«PKGBUILDDIR»/builddir/vpx-vp8-vp9-nodocs-x86_64-linux-v1.3.0/lib/libvpx.a'
> dh_testdir
> dh_testroot
> dh_install -i
> dh_install: libvpx-doc missing files (builddir/vpx-vp8-*/docs/html), aborting
> debian/rules:125: recipe for target 'binary-indep' failed
> make: *** [binary-indep] Error 2

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/09/26/libvpx_1.3.0-2.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