-
Notifications
You must be signed in to change notification settings - Fork 109
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
bootstrap.hs doesn't work with stack 2.3.1 (Cannot complete repo information for a non SHA1 commit due to non-reproducibility) #391
Comments
The error message is related to this: commercialhaskell/stack#4882 |
Latest stack doesn't seem to support named commits such as 'master'. Get the commit sha from `git rev-parse` and append it to the yaml file. This doesn't fix google#391 but goes one step further. We still get an error like: $ stack runghc -- bootstrap.hs Cloning 0bef8c2 from https://github.com/google/proto-lens Unsupported tarball from /tmp/with-repo-archive189930/foo.tar: Symbolic link dest not found from proto-lens/proto-lens-imports/google to ../../google/protobuf/src/google, looking for proto-lens/../google/protobuf/src/google. This may indicate that the source is a git archive which uses git-annex. See commercialhaskell/stack#4579 for further information. bootstrap.hs: readCreateProcess: stack "--stack-yaml=stack-bootstrap.yaml" "path" "--local-install-root" (exit 1): failed
After #392, we go one step further and get this error:
Apparently related to commercialhaskell/stack#4579. |
I tried various things but couldn't figure out how to fix this symbolic link error. The new stack doesn't seem to give an escape hatch for ignoring it. @judah any idea? |
Oof, sorry, I forgot about this problem. I encountered it a while ago here: Previously I just used stack-1.* when bootstrapping, but that won't work anymore due to the changes to proto-lens-runtime's reexport-modules. I suppose one fairly manual approach would be:
That might be worth trying to unblock the release. I'll see if I can think of something better. |
Actually, currently we're in a good place because we're not making any backwards-incompatible changes to the API. So I was able to regenerate it by removing the git-related logic altogether and using the in-tree packages for bootstrapping. It's not a great long-term solution, but it should work for the upcoming release:
|
The text was updated successfully, but these errors were encountered: