Bug#746088: scilab-metanet: FTBFS: cp: cannot stat 'debian/tmp/loader.sce': No such file or directory

[David Suárez]

Source: scilab-metanet
Version: 0.6-1-2
Severity: serious
Tags: jessie sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20140426 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):  
>  fakeroot debian/rules binary
> test -x debian/rules
> dh_testroot
> dh_prep 
> dh_installdirs -A 
> mkdir -p "."
> Adding cdbs dependencies to debian/scilab-metanet.substvars
> dh_installdirs -pscilab-metanet 
> mkdir -p /«PKGBUILDDIR»/debian/scilab-metanet/usr/lib/scilab-metanet/
> mkdir -p /«PKGBUILDDIR»/debian/scilab-metanet/usr/share/scilab/contrib/
> cd /«PKGBUILDDIR»/debian/scilab-metanet/usr/share/scilab/contrib/; \
> 		rm -f scilab-metanet; \
> 		ln -s ../../../lib/scilab-metanet/ metanet
> dh_installdocs -pscilab-metanet 
> dh_installexamples -pscilab-metanet 
> dh_installman -pscilab-metanet  
> dh_installinfo -pscilab-metanet  
> dh_installmenu -pscilab-metanet 
> dh_installcron -pscilab-metanet 
> dh_installinit -pscilab-metanet  
> dh_installdebconf -pscilab-metanet 
> dh_installemacsen -pscilab-metanet   
> dh_installcatalogs -pscilab-metanet 
> dh_installpam -pscilab-metanet 
> dh_installlogrotate -pscilab-metanet 
> dh_installlogcheck -pscilab-metanet 
> dh_installchangelogs -pscilab-metanet  
> dh_installudev -pscilab-metanet 
> dh_lintian -pscilab-metanet 
> dh_bugfiles -pscilab-metanet 
> dh_install -pscilab-metanet  
> cp: cannot stat 'debian/tmp/loader.sce': No such file or directory
> dh_install: cp -a debian/tmp/loader.sce debian/scilab-metanet/usr/lib/scilab-metanet/ returned exit code 1
> make: *** [binary-install/scilab-metanet] Error 2

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/04/26/scilab-metanet_0.6-1-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.