gtkrsync: FTBFS: gtkrsync.hs:17:17: Not in scope: `catch'

[Andreas Moog]

Imported from Debian bug http://bugs.debian.org/713761:

Source: gtkrsync
Version: 1.0.4+nmu1
Severity: serious
Tags: jessie sid
User: <email address hidden>
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[1]: Entering directory `/«BUILDDIR»/gtkrsync-1.0.4+nmu1'
> ghc -package Cabal Setup.lhs -o setup
> [1 of 1] Compiling Main ( Setup.lhs, Setup.o )
> Linking setup ...
> ./setup configure --prefix=/usr
> Configuring gtkrsync-1.0.4...
> ./setup build
> Building gtkrsync-1.0.4...
> Preprocessing executable 'gtkrsyncp' for gtkrsync-1.0.4...
> [1 of 4] Compiling Paths_gtkrsync ( dist/build/autogen/Paths_gtkrsync.hs, dist/build/gtkrsyncp/gtkrsyncp-tmp/Paths_gtkrsync.o )
> [2 of 4] Compiling RsyncParser ( RsyncParser.hs, dist/build/gtkrsyncp/gtkrsyncp-tmp/RsyncParser.o )
> [3 of 4] Compiling RsyncGUI ( RsyncGUI.hs, dist/build/gtkrsyncp/gtkrsyncp-tmp/RsyncGUI.o )
> [4 of 4] Compiling Main ( gtkrsyncp.hs, dist/build/gtkrsyncp/gtkrsyncp-tmp/Main.o )
> Linking dist/build/gtkrsyncp/gtkrsyncp ...
> Preprocessing executable 'gtkrsync' for gtkrsync-1.0.4...
> [1 of 4] Compiling Paths_gtkrsync ( dist/build/autogen/Paths_gtkrsync.hs, dist/build/gtkrsync/gtkrsync-tmp/Paths_gtkrsync.o )
> [2 of 4] Compiling RsyncParser ( RsyncParser.hs, dist/build/gtkrsync/gtkrsync-tmp/RsyncParser.o )
> [3 of 4] Compiling RsyncGUI ( RsyncGUI.hs, dist/build/gtkrsync/gtkrsync-tmp/RsyncGUI.o )
> [4 of 4] Compiling Main ( gtkrsync.hs, dist/build/gtkrsync/gtkrsync-tmp/Main.o )
>
> gtkrsync.hs:17:17: Not in scope: `catch'
> make[1]: *** [all] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/06/20/gtkrsync_1.0.4+nmu1_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.

[Andreas Moog (ampelbein)]

This package has been removed from the Ubuntu development release, so I am closing all remaining open bug reports.

Sorry that we couldn't fix your problem properly.

For more information, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742376

Thank you for your understanding and please continue to report any bugs you may find.