hpack-convert
hpack-convert copied to clipboard
yamadapc
hpack-convert: Convert Cabal manifests into hpack's package.yamls
``` $ stack install hpack-convert Using latest snapshot resolver: lts-11.4 ``` /private/var/folders/30/9xrf_jtx7618zqb1pyd1wyh40000gp/T/stack40077/hpack-convert-1.0.1/src/Hpack/Util.hs:106:21: error: • Couldn't match type ‘[[FilePath]]’ with ‘([[FilePath]], b0)’ Expected type: IO ([[FilePath]], b0) Actual type: IO [[FilePath]]...
Getting this response using the very instructions given to upload a valid cabal file. I don't know if that means it's down or just broken...
Is `hpack-convert` supposed to _just work_ when used on a project? Example: [Initial commit](https://github.com/theindigamer/sixten/tree/b4968e81d8179b95c19dfe4d76f24585f1fe3567) -- has `sixten.cabal` and no `package.yaml` -- compiles fine with just `stack build`. [Next commit](https://github.com/theindigamer/sixten/commit/18fb6f7cc026c1cb0d83b96cad477b213ca612c2) --...
I have a stack.yaml with two executable and the cabal file does not include the hs-course-dirs for the second executable. The problem was that I misspelled `source_dirs` (underbar in stead...
I use lts 16.0 everywhere and this installs hpack-convert-1.0.1 unfortunately it does not compile but produces the error: ``` • Couldn't match type ‘[[FilePath]]’ with ‘([[FilePath]], b0)’ hpack-convert > Expected...
* Advance stack snapshot version. * Fix the breakage caused by changes in Cabal. * Bump minor version. This still leaves many warnings to be addressed. Only erroneous faults were...
Building executable 'hpack-convert' for hpack-convert-1.0.1.. on the commandline: error: [-Werror] -fcontext-stack=100 is deprecated: use -freduction-depth=100 instead -- While building package hpack-convert-1.0.1 using: /Users/williamrusnack/.stack/setup-exe-cache/x86_64-osx/Cabal-simple_mPHDZzAJ_3.0.1.0_ghc-8.8.2 --builddir=.stack-work/dist/x86_64-osx/Cabal-3.0.1.0 build lib:hpack-convert exe:hpack-convert --ghc-options " -fdiagnostics-color=always"...
When using stack install, the library field is causing this error Error while parsing $.library.dependencies - expected Array, Object, or String, encountered Null
