A few hours ago integer-gmp-1.0.1.0 was uploaded to Hackage. The new package's cabal file's build-depends field uses the new ^>= syntax for version specification. The stable release (v1.5.1) doesn't use Cabal 2, so if you're working with a fresh index stack (any operation but stack update, it seems) will fail with Unable to parse cabal file for integer-gmp-1.0.1.0: NoParse "build-depends" 58. This seems to occur in all of my stack projects, no matter which snapshot is selected.
To reproduce (in some stack project's directory):
some/stack/project $ cp -r ~/.stack ~/.stack_known_good some/stack/project $ rm -r ~/.stack some/stack/project $ stack build Downloaded nightly-2017-11-24 build plan. Selected mirror https://s3.amazonaws.com/hackage.fpcomplete.com/ Downloading root Selected mirror https://s3.amazonaws.com/hackage.fpcomplete.com/ Downloading timestamp Downloading snapshot Downloading mirrors Cannot update index (no local copy) Downloading index Updated package list downloaded Populated index cache. Unable to parse cabal file for integer-gmp-1.0.1.0: NoParse "build-depends" 58
I'll note that all of the stack projects I've tried this with have non-empty extra-deps fields; perhaps stack functions correctly without checking the Hackage index if there are no extra-deps specified? Seems this happens even without any extra-deps.
If I've got something wrong here or if someone is aware of a workaround that isn't copying another machine's index, please do share.
AndrewRademacher, simonmichael, tfausak, ip1981, steshaw and 3 more
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4