fsnotify conflicts hinotify version? about stackage

[snoyberg]

Did you run stackage init at some point by any chance?

[juhp]

I think I did - thought that might have been why. Ok, will try again
tomorrow from scratch... So one can't run build after init?

Would it be better to list "build" before in --help?

[snoyberg]

Actually, I think I did something a little better: b9a7065

It was a mistake in my documentation to imply it should be run.

[juhp]

Ok, I might have answered yes - I'll have to try again anyway.

[snoyberg]

That message was a recent change, and running stackage init was part of the instructions previously, so it's not surprising. Sorry for the confusion.

[ekmett]

@snoyberg FYI the README.markdown instructions still say to stackage init.

[snoyberg]

Not any more ;).

Not sure why I thought I'd removed it...

[juhp]

Ok I tried again.
This is using the latest Fedora packages with a base of haskell-platform-2012.4.
Below are my steps which I hope might work - but tell where I am falling off the proper path. :)

$ sudo yum install ghc-7.4.2 cabal-install cabal-dev git
::
$ cabal update
$ git clone https://github.com/fpco/stackage
$ cd stackage
$ git submodule update --init
$ cabal install # is this a no-no?
$ ~/.cabal/bin/stackage build
Creating a build plan
Printing build plan to build-plan.log
Wiping out old sandbox folder
cabal: Could not resolve dependencies:
trying: ansi-terminal-0.5.5.1 (user goal)
next goal: hspec (user goal)
rejecting: hspec-1.4.2.2 (conflict: ansi-terminal==0.5.5.1, hspec =>
ansi-terminal==0.5.5)
rejecting: hspec-1.4.2.1, 1.4.2, 1.4.1.1, 1.4.1, 1.4.0.1, 1.4.0, 1.3.0.2,
1.3.0.1, 1.3.0, 1.2.0.1, 1.2.0, 1.1.3, 1.1.2, 1.1.1, 1.1.0, 1.0.0.1, 1.0.0,
0.9.2.2, 0.9.2.1, 0.9.2, 0.9.1.1, 0.9.1, 0.9.0, 0.8.1, 0.8, 0.6.1, 0.6.0,
0.5.0, 0.4.3, 0.3.0, 0.2.0 (global constraint requires ==1.4.2.2)
Resolving dependencies...
cabal returned a bad result, exiting

Actually I get the same if I run "runghc app/stackage.hs build".

I also tried cabal installing Cabal-1.16.0.3 once I noticed it in the README.
So is the assumption that we should be testing with ghc-7.6?

[snoyberg]

That's a separate error: hspec/hspec#114

The reason for Cabal 1.16 is because there are some bugs in 1.14 which affect sandboxing, especially with dynamic linking. But I'm still doing all of my testing on GHC 7.4.2.

[juhp]

Ah ok I see thanks - then probably this can be closed.

Couldn't stackage try ansi-terminal-0.5.5 in this case though (maybe with a warning) instead of just giving up?

[snoyberg]

It could, but (IMO) that's detrimental. Part of the goal here is to make sure that all packages compile with the newest versions of all their dependencies. We could add a special rule to Stackage.Config that we should specifically use ansi-terminal 0.5.5, but it's better if hspec is just updated.

[juhp]

Ok, I hardcorded ansi-terminal locally with:

 addRange "hackage" "ansi-terminal" "== 0.5.5"

and now build gets me to:

Found the following mismtaches
OnlySimpleList "tar-0.4.0.1"

I looked briefly at CheckPlan.hs but no sure exactly what this means?
(I can also move this discussion elsewhere if there is a better place:)

[juhp]

Ah after unregistering user tar lib then:

No mismatches, starting the sandboxed build.
stackage: Unsupported Cabal version: 1.14.0

ok...

[snoyberg]

The issue is that you have tar installed in your global package database (or so I'm guessing). As a result, cabal-install doesn't want to install it, but stackage still wants to. As a result, you get a mismatch (or mismtach, as I prefer to call it).

[snoyberg]

Hmm... the tar lib was installed in the user database? That shouldn't be causing trouble, as the command we pass to cabal-install tells it to ignore user databases.

As for Cabal: which version of cabal-install are you using?

[juhp]

Yes in user (pulled in by "cabal install stackage" - guess I should use cabal-dev).

This is cabal-install-0.14.0 from HP 2012.4.

[snoyberg]

I can't explain the tar issue, but stackage requires cabal-install and Cabal to be 1.16 to avoid some sandboxing bugs in 1.14.

[juhp]

Ok I see - yeah stackage is building now for me with cabal-install-1.16.x.