Bug#713528: tsdecrypt: FTBFS: /bin/sh: 1: cd: can't cd to /«PKGBUILDDIR»/debian/tsdecrypt

[Lucas Nussbaum]

Source: tsdecrypt
Version: 9.0-1
Severity: serious
Tags: jessie sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20130620 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 `/«PKGBUILDDIR»/libtsfuncs'
>   CC	libtsfuncs	log.c
>   CC	libtsfuncs	tsfuncs.c
>   CC	libtsfuncs	crc.c
>   CC	libtsfuncs	misc.c
>   CC	libtsfuncs	time.c
>   CC	libtsfuncs	sections.c
>   CC	libtsfuncs	secdata.c
>   CC	libtsfuncs	descs.c
>   CC	libtsfuncs	pat.c
>   CC	libtsfuncs	pat_desc.c
>   CC	libtsfuncs	cat.c
>   CC	libtsfuncs	pmt.c
>   CC	libtsfuncs	nit.c
>   CC	libtsfuncs	nit_desc.c
>   CC	libtsfuncs	sdt.c
>   CC	libtsfuncs	sdt_desc.c
>   CC	libtsfuncs	eit.c
>   CC	libtsfuncs	eit_desc.c
>   CC	libtsfuncs	tdt.c
>   CC	libtsfuncs	tdt_desc.c
>   CC	libtsfuncs	pes.c
>   CC	libtsfuncs	pes_data.c
>   CC	libtsfuncs	pes_es.c
>   CC	libtsfuncs	privsec.c
>   LINK	libtsfuncs.a
> make[4]: Leaving directory `/«PKGBUILDDIR»/libtsfuncs'
>   CC	tsdecrypt	data.c
>   CC	tsdecrypt	csa.c
>   CC	tsdecrypt	udp.c
>   CC	tsdecrypt	util.c
>   CC	tsdecrypt	filter.c
>   CC	tsdecrypt	camd.c
>   CC	tsdecrypt	camd-cs378x.c
>   CC	tsdecrypt	camd-newcamd.c
>   CC	tsdecrypt	process.c
>   CC	tsdecrypt	tables.c
>   CC	tsdecrypt	notify.c
>   CC	tsdecrypt	tsdecrypt.c
>   LINK	tsdecrypt
> make[3]: Leaving directory `/«PKGBUILDDIR»'
> make[2]: Leaving directory `/«PKGBUILDDIR»'
> mv tsdecrypt tsdecrypt_dvbcsa
> # Install binaries
> cd /«PKGBUILDDIR»/debian/tsdecrypt && mkdir -p usr/bin
> /bin/sh: 1: cd: can't cd to /«PKGBUILDDIR»/debian/tsdecrypt
> make[1]: *** [override_dh_auto_install] Error 2

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/06/20/tsdecrypt_9.0-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.