Package: haskell-network
Version: 2.2.1.3-1
Severity: serious
User: [email protected]
Usertags: qa-ftbfs-20090620 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> ** Using build dependencies supplied by package:
> Build-Depends: debhelper (>= 5), haddock (>= 2.4.2), hscolour, 
> haskell-devscripts, ghc6, ghc6-prof, ghc6-doc, libghc6-parsec2-dev (>= 
> 2.1.0.1), libghc6-parsec2-prof, libghc6-parsec2-doc, libghc6-mtl-doc, cdbs
> 
> ┌──────────────────────────────────────────────────────────────────────────────┐
> │ Install build dependencies                                                  
>  │
> └──────────────────────────────────────────────────────────────────────────────┘
> 
> Checking for already installed source dependencies...
> W: Unable to locate package libghc6-parsec2-prof
> W: Unable to locate package libghc6-parsec2-dev
> debhelper: missing
> Using default version 7.2.16
> haddock: missing
> Using default version 2.4.2-1
> hscolour: missing
> haskell-devscripts: missing
> ghc6: missing
> ghc6-prof: missing
> ghc6-doc: missing
> libghc6-parsec2-dev: missing
> libghc6-parsec2-prof: missing
> libghc6-parsec2-doc: missing
> libghc6-mtl-doc: missing
> cdbs: missing
> Checking for source dependency conflicts...
> E: Couldn't find package libghc6-parsec2-dev

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2009/06/20/haskell-network_2.2.1.3-1_lsid64.buildlog

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 about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.

-- 
| Lucas Nussbaum
| [email protected]   http://www.lucas-nussbaum.net/ |
| jabber: [email protected]             GPG: 1024D/023B3F4F |



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

Reply via email to