[Pkg-haskell-maintainers] Bug#713518: haskell98-report: FTBFS: texinfo errors

[Lucas Nussbaum]

Source: haskell98-report
Version: 20080907-4
Severity: serious
Tags: jessie sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20130620 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> make[3]: Entering directory `/«PKGBUILDDIR»/tools'
> flex -t -8 verbatim.lex > verbatim.c || ( rm -f verbatim.c && exit 1 )
> "verbatim.lex", line 75: warning, rule cannot be matched
> cc -c verbatim.c -o verbatim.o
> cc -o verbatim verbatim.o
> ghc -o run_tex tex.hs -fglasgow-exts -H20m 
> 
> on the commandline: Warning:
>     -fglasgow-exts is deprecated: Use individual extensions instead
> [1 of 1] Compiling Main             ( tex.hs, tex.o )
> 
> tex.hs:218:15:
>     Not in scope: `catch'
>     Perhaps you meant `catchd' (line 155)
> 
> tex.hs:235:15:
>     Not in scope: `catch'
>     Perhaps you meant `catchd' (line 155)
> 
> tex.hs:255:17:
>     Not in scope: `catch'
>     Perhaps you meant `catchd' (line 155)
> 
> tex.hs:284:17:
>     Not in scope: `catch'
>     Perhaps you meant `catchd' (line 155)
> 
> tex.hs:293:17:
>     Not in scope: `catch'
>     Perhaps you meant `catchd' (line 155)
> 
> tex.hs:299:20:
>     Not in scope: `catch'
>     Perhaps you meant `catchd' (line 155)
> 
> tex.hs:400:22:
>     Not in scope: `catch'
>     Perhaps you meant `catchd' (line 155)
> 
> tex.hs:405:27:
>     Not in scope: `catch'
>     Perhaps you meant `catchd' (line 155)
> 
> tex.hs:1257:22:
>     Not in scope: `catch'
>     Perhaps you meant `catchd' (line 155)
> 
> tex.hs:1267:22:
>     Not in scope: `catch'
>     Perhaps you meant `catchd' (line 155)
> make[3]: *** [run_tex] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/06/20/haskell98-report_20080907-4_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.