jgm / gitit

A wiki using HAppS, pandoc, and git
GNU General Public License v2.0
2.15k stars 225 forks source link

Dependency conflict on GHC 8.4.2 #615

Closed Rufflewind closed 5 years ago

Rufflewind commented 6 years ago

gitit == 0.12.2.1 ⇒ pandoc ≤ 1.19.2.4 ⇒ haddock-library ≤ 1.4.5 ⇒ base < 4.11 :(

jgm commented 6 years ago

Try the latest version from git to see if you have better luck. I loosened some dependencies.

Phil Ruffwind notifications@github.com writes:

gitit == 0.12.2.1 ⇒ pandoc ≤ 1.19.2.4 ⇒ haddock-library ≤ 1.4.5 ⇒ base < 4.11 :(

-- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/jgm/gitit/issues/615

Rufflewind commented 6 years ago

Gitit is still stuck on Pandoc 1.19.2.4, so the problem persists.

jgm commented 6 years ago

Can you explain the problem? Yes, gitit is stuck on pandoc 1.19. But it can still build on modern systems. Is the problem that pandoc 1.19 has an upper bound on base that precludes the base version that goes with ghc 8.4.2?

Phil Ruffwind notifications@github.com writes:

Gitit is still stuck on Pandoc 1.19.2.4, so the problem persists.

-- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/jgm/gitit/issues/615#issuecomment-393365911

Rufflewind commented 6 years ago
Rufflewind commented 6 years ago

After playing with this a bit further using gitit HEAD, here's (I think) all of the dependency problems:

jgm commented 6 years ago

I think the best way forward is to support pandoc 2.2.1 on gitit. This will require some significant changes due to changes in the pandoc API.

I've started a new branch pandoc2 for this, but I don't have a lot of time for it now. If you want to work on it, feel free.

Phil Ruffwind notifications@github.com writes:

After playing with this a bit further using gitit HEAD, here's (I think) all of the dependency problems:

  • gitit 0.12.2.1 depends on an older version of happstack (7.4.6.2 or older), which does not compile with base 4.11.1.0. Fortuantely, this is no longer a problem on gitit HEAD.

  • gitit 0.12.2.1 and gitit HEAD both depend on an older version of pandoc (1.19.2.4 or older):

    • pandoc 1.19.2.4 depends on an older version of haddock-library (1.4.5 or older):

      • haddock-library 1.4.5 specifies base < 4.11. This is problem (1). However, it can be overcome through --allow-newer=haddock-library:base. It compiles just fine, so presumably this just needs a version relaxation?
    • pandoc 1.19.2.4 depends on an older version of doctemplates (0.1.0.2 or older)

      • doctemplates 0.1.0.2 does not compile with base 4.11.1.0. This is problem (2). Fortunately, doctemplates 0.2.2.1 does compile (and presumably works correctly?), thus this problem can be worked around via --allow-newer=pandoc:doctemplates.
    • pandoc 1.19.2.4 depends on an older version of pandoc-types (1.17.0.5 or older):

      • pandoc-types 1.17.0.5 does not compile with base 4.11.1.0. This is problem (3). I was unable to find a workaround for this. I tried --allow-newer=gitit:pandoc --allow-newer=gitit:pandoc-types, but gitit does not support the latest pandoc it seems.

-- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/jgm/gitit/issues/615#issuecomment-394223679

Rufflewind commented 5 years ago

Looks like HEAD works fine with the new GHC. Thanks for fixing it! Would you mind making a release?

jgm commented 5 years ago

Done.

Phil Ruffwind notifications@github.com writes:

Looks like HEAD works fine with the new GHC. Thanks fixing it! Would you mind making a release?

-- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/jgm/gitit/issues/615#issuecomment-428089121

Rufflewind commented 5 years ago

Awesome!

nstgc commented 5 years ago

Done. Phil Ruffwind notifications@github.com writes: Looks like HEAD works fine with the new GHC. Thanks fixing it! Would you mind making a release? -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: #615 (comment)

So does this mean it should now compile? I ask because I'm on Arch trying to compile from Rufflewind's AUR PKGBUILD script, but its failing with what appears to be the same errors as earlier in the year.

Rufflewind commented 5 years ago

@nstgc See https://github.com/jgm/gitit/issues/625