[pkg-curry-maintainers] Bug#871194: pakcs: FTBFS: mv: cannot stat 'swi.state': No such file or directory

[Lucas Nussbaum]

Source: pakcs
Version: 1.14.2-1
Severity: serious
Tags: buster sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20170805 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):
> make[5]: Entering directory '/<<PKGBUILDDIR>>/curry2prolog'
> echo "compile(c2p). c2p('/<<PKGBUILDDIR>>/lib/Prelude'), compile('/<<PKGBUILDDIR>>/lib/.curry/pakcs/Prelude'),loader:loadAndCompile('/<<PKGBUILDDIR>>/lib/.curry/pakcs/Prelude.pl',[],create). saveprog_entry('swi.state',user:pakcsMain)." | "/<<PKGBUILDDIR>>/bin/swiprolog" --traditional -q -L0 -G0 -T0 -O
> 
> Warning: /<<PKGBUILDDIR>>/curry2prolog/compiler.pl:2421:
> 	Singleton variable in branch: Arity
> true.
> 
> 
> true.
> 
> ERROR: /usr/lib/swi-prolog/library/qsave.pl:459:7: Syntax error: Operator expected
> ERROR: /usr/lib/swi-prolog/library/shell.pl:342:18: Syntax error: Operator expected
> ERROR: Type error: `text' expected, found `[126,119,61]' (a list)
> ERROR: In:
> ERROR:   [11] atomics_to_string([[126|...],...|...],_108028)
> ERROR:   [10] qsave:save_options(429300,runtime,[init_file(none),...]) at /usr/lib/swi-prolog/library/qsave.pl:213
> ERROR:    [9] qsave:qsave_program('swi.state',prologbasics:[...]) at /usr/lib/swi-prolog/library/qsave.pl:103
> ERROR:    [8] prologbasics:saveprog_entry('swi.state',user:pakcsMain) at /<<PKGBUILDDIR>>/curry2prolog/prologbasics.pl:534
> ERROR:    [7] <user>
> 
> make[5]: Leaving directory '/<<PKGBUILDDIR>>/curry2prolog'
> mv -f swi.state c2p.state
> mv: cannot stat 'swi.state': No such file or directory
> Makefile:50: recipe for target 'swi' failed
> make[4]: *** [swi] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2017/08/05/pakcs_1.14.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.