Source: haskelldb-hsql
Version: 0.10-2+b1
Severity: serious

Hi,

There was an error while trying to autobuild your package:

> Automatic build of haskelldb-hsql_0.10-2+b1 on excelsior by sbuild/amd64 98
> Build started at 20090724-2237

[...]

> Build-Depends: debhelper (>= 5), dpatch, dpkg-dev (>= 0.13.19), ghc6 (>= 
> 6.8.2), haskell-devscripts (>= 0.6.0), libghc6-haskelldb-dev, 
> libghc6-hsql-dev (>= 1.7), libghc6-mtl-dev

[...]

> Toolchain package versions: linux-libc-dev_2.6.30-3 libc6-dev_2.9-21 
> g++-4.3_4.3.3-14 gcc-4.3_4.3.3-14 binutils_2.19.51.20090714-1 
> libstdc++6_4.4.0-11 libstdc++6-4.3-dev_4.3.3-14

[...]

>  ****************************************** 
>  CONFIGURING libghc6-haskelldb-hsql-dev FOR ghc6
>  ****************************************** 
> 
> cleaning...
> /build/buildd/haskelldb-hsql-0.10/Database/HaskellDB:
> Configuring haskelldb-hsql-0.10...
> Warning: No 'build-type' specified. If you do not need a custom Setup.hs or
> ./configure script then use 'build-type: Simple'.
> 
>  ****************************************** 
>  BUILDING libghc6-haskelldb-hsql-dev FOR ghc6
>  ****************************************** 
> 
> Preprocessing library haskelldb-hsql-0.10...
> Building haskelldb-hsql-0.10...
> [1 of 1] Compiling Database.HaskellDB.HSQL ( Database/HaskellDB/HSQL.hs, 
> dist/build/Database/HaskellDB/HSQL.o )
> 
> Database/HaskellDB/HSQL.hs:181:54:
>     Ambiguous type variable `e' in the constraint:
>       `GHC.Exception.Exception e'
>         arising from a use of `throwIO'
>                      at Database/HaskellDB/HSQL.hs:181:54-62
>     Probable fix: add a type signature that fixes these type variable(s)
> dh_haskell_build: ./setup returned exit code 1
> make: *** [install-arch] Error 1
> dpkg-buildpackage: error: /usr/bin/fakeroot debian/rules binary-arch gave 
> error exit status 2

A full build log can be found at:
http://buildd.debian.org/build.php?arch=amd64&pkg=haskelldb-hsql&ver=0.10-2+b1


Kurt




-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to