[Pkg-samba-maint] samba build failure on raspbian stretch rm: cannot remove '/«BUILDDIR»/samba-4.1.17+dfsg/debian/tmp/usr/share/man/man1/vfstest.1': No such file or directory

[peter green]

On 04/05/15 02:34, Jelmer Vernooij wrote:
>> * Though while dealing with build-dependency issues I did update tdb
>>    to the sid version.
>>      
> How are you building the package exactly?
>    
We pull the source packages and arch all packages from Debian stretch 
(and occasionally I manually pull something from sid before Debian 
jessie has it, usually because of a build-depency issue*) into the 
stretch-staging suite in our repository. We then use 
wanna-build/buildd/sbuild to do the actual building. Once all the 
binaries are in sync and some depency checks pass the package will move 
to our main stretch suite.

A full log log of the build is at 
http://buildd.raspbian.org/status/fetch.php?pkg=samba&arch=armhf&ver=2%3A4.1.17%2Bdfsg-4&stamp=1430696792

The buildd hardware for this autobuild was a wandboard quad. build 
chroots are using btrfs snapshots. The kernel is a custom build based on 
Debian 3.19.1-1~exp1 with a slight config tweak to reenable a udev 
related feature.
> You're very likely encountering bug 750593, see
> http://bugs.debian.org/750593
>    
Searching the log for "bus error" didn't seem to turn anything up.

>> For now in raspbian I added -f to the rm command so it will succeed
>> regardless of whether the file exists or not.
>>      
Upon doing a manual build (on an odriod u2 in a plain chroot, more 
information on the configuration of said machine can be provided if 
wanted) with the -f added I got another failure.

# use upstream version of smb.conf.5 if there is no built version
# this is a temporary workaround for #750593 in xsltproc
[ -e /usr/share/man/man5/smb.conf.5 ] || \
cp docs/manpages/smb.conf.5 
/samba-4.1.17+dfsg/debian/tmp/usr/share/man/man5/smb.conf.5
cp: cannot create regular file 
‘/samba-4.1.17+dfsg/debian/tmp/usr/share/man/man5/smb.conf.5’: No such 
file or directory

So I added a mkdir -p, that build is now running.

* Unfortunately britney doesn't check build-depends, so packages in 
Debian testing are not gauranteed to be buildable in a testing environment.