Hello, Seems that happstack-util had an artificially low upper bounds. I just uploaded happstack-util 0.5.0.1 which bumps it to parsec < 4. Make sure that your version of the 'network' library is compiled against parsec 3, since happstack-server depends on both network and parsec. Thanks for your report! - jeremy On May 4, 2010, at 5:55 PM, Maciej Piechotka wrote:
I try to configure happstack with parsec 3.1. It seems to fail due to cabal:
3
I installed happstack-util editing happstack-util.cabal by hand: % grep parsec ~/.ghc/x86_64-linux-6.12.2/package.conf.d/happstack- util-0.5.0-6e27d5d3ba1c07f259d463ee3036c92b.conf parsec-3.1.0-5842597f447f82b210228391f371cff1 % cabal install --constraint 'parsec > 3' --dry-run happstack Resolving dependencies... cabal: cannot configure happstack-util-0.5.0. It requires parsec <3 For the dependency on parsec <3 there are these packages: parsec-2.0, parsec-2.1.0.0 and parsec-2.1.0.1. However none of them are available. parsec-2.0 was excluded because of the top level dependency parsec >3 parsec-2.1.0.0 was excluded because of the top level dependency parsec parsec-2.1.0.1 was excluded because of the top level dependency parsec
3 % ghc-pkg list | grep happstack-util happstack-util-0.5.0
Regards _______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe