Bug#728646: libfilesys-smbclient-perl: FTBFS: libsmbclient.h: No such file or directory

[David Suárez]

Source: libfilesys-smbclient-perl
Version: 3.2-1
Severity: serious
Tags: jessie sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20131103 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Debian now contains samba 4, which has header files in a special directory:
/usr/include/samba-4.0/libsmbclient.h

Relevant part (hopefully):
> cc -c  -I/usr/include -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fstack-protector -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2   -DVERSION=\"3.2\" -DXS_VERSION=\"3.2\" -fPIC "-I/usr/lib/perl/5.18/CORE"   SmbClient.c
> SmbClient.xs:20:26: fatal error: libsmbclient.h: No such file or directory
>  #include "libsmbclient.h"
>                           ^
> compilation terminated.
> make[1]: *** [SmbClient.o] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/11/03/libfilesys-smbclient-perl_3.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.