-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add hls-1.6.0.0 #19
Add hls-1.6.0.0 #19
Conversation
@hasufell ci is happy 😄 |
|
is that a local check? i cant find that in the ci logs, it seems ci only checks own ghcup tarballs |
See https://github.com/haskell/ghcup-metadata#adding-a-new-ghc-version step 7
|
thanks! i inferred it from the ci invocation and it is running now does it take too much time to check it in ci? |
How would you run it? |
hmm adding a step running |
How will that work for the next PR adding a new HLS version or a different GHC version? |
ok reproduced the check error locally but i still am not sure what is going on, i can extract the files succesfully. The unique thing i did locally was rename the file, so ci produced the tarball |
We use lzma to decompress: https://hackage.haskell.org/package/lzma-static It appears to have problem with some feature of the archive, I guess. |
The encoding for |
I am thinking in removing the alpine tarballs, like 1.5.1. At the end those binaries will suffer the same template haskell bug we hit in hls , no? |
In fact all tarballs are |
dlUri: https://github.com/haskell/haskell-language-server/releases/download/1.6.0.0/haskell-language-server-Windows-1.6.0.0.tar.gz | ||
dlHash: 9f1b4ea31602a775a8f5bfedcc6290d3e45dd695f389fd705c9fff96c63c8570 | ||
Linux_Alpine: | ||
unknown_versioning: *hls-1600-64 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If the current linux binaries are dynamic, this will not work.
No description provided.