ghc-prim dependency mismatch

[fauno]

the package description says it requires ghc-prim < 0.5 but the source says ghc-prim 0.4

[hvr]

What do you mean by "the source says ghc-prim 0.4"?

PS: Do you mean http://hackage.haskell.org/package/deepseq-generics-0.1.1.2/revisions/ ? If so, how is this causing problems?

[fauno]

sorry i meant the package description from source says ghc-prim < 0.4

i ran into this issue while building pandoc 1.13.2.1 with ghc 7.10, since ghc provides base > 0.4 the build fails, but cabal didn't notice during source download because its database says ghc-prim requires base < 0.5

hope this is clearer

[hvr]

So this happens if you cabal install deepseq-generics too? Which cabal-install version are you using?

[fauno]

• cabal-install 1.22.2.0
• ghc 7.10.1 which provides ghc-prim 0.4.0.0

cabal install deepseq-generics works correctly (because deepseq-generics.cabal from hackage requires ghc-prim < 0.5), but cabal fetch deepseq-generics and cabal build on the extracted sources fails because deepseq-generics.cabal says ghc-prim < 0.4

[hvr]

Now I see; you should use cabal get deepseq-generics as that one copies the amended .cabal revision into the extracted source folder (and thus overwriting the 0th .cabal revision contained in the tarball).

I'm still wondering; why do you operate manually on the source tarball, rather than using the revision-aware cabal-facilities?

[fauno]

Herbert Valerio Riedel notifications@github.com writes:

Now I see; you should use cabal get deepseq-generics as that ones
overlay the amended cabal revision into the extracted source folder.

cool, thanks!

I'm still wondering; why do you operate manually on the source
tarball, rather than using the revision-aware cabal-facilities?

because in order to distribute a pandoc binary package for parabola0 i
need to provide a source tarball, so i use cabal fetch first, make a
source tarball and then build them using the distro pkgbuild1

http://hackcoop.com.ar

[dcoutts]

@fauno in that case I suggest that you make your tools patch the tarball with the latest .cabal file from the index. For example you could cabal unpack (which by default will update the .cabal file), and then call tar to make an updated tarball.

[fauno]

Duncan Coutts notifications@github.com writes:

@fauno in that case I suggest that you make your tools patch the
tarball with the latest .cabal file from the index. For example you
could cabal unpack (which by default will update the .cabal file), and
then call tar to make an updated tarball.

great! :)

http://hackcoop.com.ar

[fauno]

i solved it with cabal get, thanks!

[mimi1vx]

Isn't good problem solv ... not system ,

for example in rpm distributions is by default used cabal file from tar.gz archive with bad constrains ...

@hvr please release new minor.minor version with updated cabal file .. 0.1.1.3 ..