Bug#763259: yade: FTBFS: I can't find file `Yade.tex'

[David Suárez]

Source: yade
Version: 1.11.1-3
Severity: serious
Tags: jessie sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20140926 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): 
> copying static files... done
> copying extra files... done
> dumping search index... done
> dumping object inventory... done
> build succeeded, 9 warnings.
> This is XeTeX, Version 3.14159265-2.6-0.99991 (TeX Live 2014/Debian) (preloaded format=xelatex)
>  restricted \write18 enabled.
> entering extended mode
> ! I can't find file `Yade.tex'.
> <*> Yade.tex
>             
> (Press Enter to retry, or Control-D to exit)
> Please type another input file name: 
> ! Emergency stop.
> <*> Yade.tex
>             
> No pages of output.
> Transcript written on texput.log.
> This is XeTeX, Version 3.14159265-2.6-0.99991 (TeX Live 2014/Debian) (preloaded format=xelatex)
>  restricted \write18 enabled.
> entering extended mode
> ! I can't find file `Yade.tex'.
> <*> Yade.tex
>             
> (Press Enter to retry, or Control-D to exit)
> Please type another input file name: 
> ! Emergency stop.
> <*> Yade.tex
>             
> No pages of output.
> Transcript written on texput.log.
> This is XeTeX, Version 3.14159265-2.6-0.99991 (TeX Live 2014/Debian) (preloaded format=xelatex)
>  restricted \write18 enabled.
> entering extended mode
> ! I can't find file `Yade.tex'.
> <*> Yade.tex
>             
> (Press Enter to retry, or Control-D to exit)
> Please type another input file name: 
> ! Emergency stop.
> <*> Yade.tex
>             
> No pages of output.
> Transcript written on texput.log.
> make[1]: *** [override_dh_auto_install] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/09/26/yade_1.11.1-3_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.