You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am creating an issue here so that users find it if they experience an issue with stack 2.1.1, but this is not a bug in hawk, it is a bug in stack 2.1.1 which is fixed in stack at commit 61edf6b824ac53ea9d20bd21c3e0d6a385f29ea1. For some reason, at the time of writing, using stack upgrade --git obtains a version of stack which does not include that bugfix, I don't know why.
stack 2.x now creates an environment file controlling which packages are visible to test suites. That environment file is supposed to list all the dependencies listed in the .cabal file for that test suite, but the bug in stack 2.1.1 is that it doesn't include the library provided by that same .cabal file even if it is listed. Since hawk needs to load modules from the haskell-awk library, the test suite fails.
I am creating an issue here so that users find it if they experience an issue with stack 2.1.1, but this is not a bug in hawk, it is a bug in stack 2.1.1 which is fixed in stack at commit 61edf6b824ac53ea9d20bd21c3e0d6a385f29ea1. For some reason, at the time of writing, using
stack upgrade --git
obtains a version of stack which does not include that bugfix, I don't know why.stack 2.x now creates an environment file controlling which packages are visible to test suites. That environment file is supposed to list all the dependencies listed in the
.cabal
file for that test suite, but the bug in stack 2.1.1 is that it doesn't include the library provided by that same.cabal
file even if it is listed. Sincehawk
needs to load modules from thehaskell-awk
library, the test suite fails.See commercialhaskell/stack#4896 and commercialhaskell/stack#4921 for details.
The text was updated successfully, but these errors were encountered: