Control: reassign -1 libsigrok-dev 0.2.0-2 Control: affects -1 + sigrok-cli Control: retitle -1 libsigrok-dev: missing dependency on libasound2-dev
On Sun, Sep 22, 2013 at 17:48:19 +0200, David Suárez wrote: > Source: sigrok-cli > Version: 0.4.0-2 > Severity: serious > Tags: jessie sid > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20130922 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): > > checking pkg-config is at least version 0.22... yes > > checking for pkg-config... (cached) /usr/bin/pkg-config > > checking pkg-config is at least version 0.16... yes > > checking for GLIB - version >= 2.28.0... yes (version 2.36.4) > > checking for libsigrok... no > > configure: error: Package requirements (libsigrok >= 0.2.0) were not met > > > > Package alsa was not found in the pkg-config search path. > > Perhaps you should add the directory containing `alsa.pc' > > to the PKG_CONFIG_PATH environment variable > > Package 'alsa', required by 'libsigrok', not found > > > > Consider adjusting the PKG_CONFIG_PATH environment variable if you > > installed software in a non-standard prefix. > > > > Alternatively, you may set the environment variables libsigrok_CFLAGS > > and libsigrok_LIBS to avoid the need to call pkg-config. > > See the pkg-config man page for more details. > > The full build log is available from: > > http://aws-logs.debian.net/ftbfs-logs/2013/09/22/sigrok-cli_0.4.0-2_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.
signature.asc
Description: Digital signature
