I believe I've fixed the Windows issue by release a new network (2.4.2.3) and the Haddock issue by reverting a botched merge commit. The latter means that `cabal exec` is currently out of this release unless someone can successfully merge the commit to the 1.20 branch. Currently this causes a bunch of conflicts. On Thu, Apr 17, 2014 at 8:28 PM, Carter Schonwald < carter.schonwald@gmail.com> wrote:

also bizzarely, the haddocks for cabal 1.20 aren't showing up in my haddocks index or anywhere!

On Thu, Apr 17, 2014 at 1:32 PM, Carter Schonwald < carter.schonwald@gmail.com> wrote:

...

I'm trying to use the new haddock flags

haddock -- keep-temp-files: False -- hoogle: False -- html: False -- html-location: -- executables: False -- tests: False -- benchmarks: False -- all: -- internal: False internal: True -- css: -- hyperlink-source: False hyperlink-source: True

and it looks like hyperlink-source isn't quite working! What am i doing wrong?

On Thu, Apr 17, 2014 at 3:06 AM, Johan Tibell wrote:

...

Hi all,

The second, and hopefully last, release candidate for Cabal and cabal-install 1.20 is ready. If no issues are discovered, I plan to release this on Sunday, April 20th.

You can help test by installing the release candidate and use it for your day-to-day work:

cabal install http://johantibell.com/files/Cabal-1.20.0.0-rc2.tar.gz http://johantibell.com/files/cabal-install-1.20.0.0-rc2.tar.gz

Please report any issues at https://github.com/haskell/cabal/issues

-- Johan

_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe