-
Notifications
You must be signed in to change notification settings - Fork 79
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
stack_snapshot pinning: Unsupported archive format #1392
Comments
To work around this issue you can pull |
thanks for the clear answer. I have tried the following (and several other configurations):
but it fails with
and indeed /home/teto/.cache/bazel/_bazel_teto/32070fb26dd3cfe8bd075800f8bb83d1/external/funflow/funflow.cabal does not exist. |
In case of
Indeed, it's a convenience to avoid having to repeat the list of package dependencies. Bazel is able to separate the downloading of |
Makes sense, I thought about it but had not tried my bad. I feel bad for following with yet another question sorry but seems like funflow can't see the hackage builds. stack_snapshot doesn't support default_visibility and
Would it make sense for stack_snapshot to adjust visibility for vendored_packages too ? |
Oh, indeed, sorry I forgot to mention that. In this case you'll need to mention the required packages in
Anything that is listed in |
I actually had to remove funflow from
|
I have a similar issue with haskell-language-server master.
Indeed hls-plugin-api.cabal is too deep |
We want to work around an issue with packages not at the top-level. It looks as though there's some issue in the newer versions of `rules_haskell` for Haskell packages that aren't at the top-level. This comment gives an overview of the problem: tweag/rules_haskell#1392 (comment). To paraphrase, Haskell packages in a sub-directory don't really work with `stack ls dependencies json` at the moment. Since we want to update `rules_haskell` to a newer version, we need to address this. We can make this change now without updating the version so that the version bump of `rules_haskell` has a smaller diff. In all likelihood, this issue will be fixed at some point. Haskell packages in a sub-directory are fairly common. Until that day, we follow most of the workaround laid out in that GitHub issue: pull in the package as a `bazel` `http_archive` rule, point `stack_snapshot` to the package as a `vendored_package`. The part we do a bit differently is not stripping down to the sub-directory. Instead, we treat the whole archive as one thing and locate the files based on where they live from the top-level. We take this approach primarily because we're going to pull in both `purescript-ast` and `purescript-cst`. Since the commit we're using doesn't have a `lib/purescript-cst/purescript-cst.cabal` file, we have to patch it to add that.
We want to work around an issue with packages not at the top-level. This follows the change we made for `purescript-cst` in 8f77f15f5d388b6a17c6a216ea1644caeda609af. I.e. addressing the problem of Haskell packages in a sub-directory not really working with `stack ls dependencies json` at the moment: tweag/rules_haskell#1392 (comment).
We want to work around an issue with packages not at the top-level. It looks as though there's some issue in the newer versions of `rules_haskell` for Haskell packages that aren't at the top-level. This comment gives an overview of the problem: tweag/rules_haskell#1392 (comment). To paraphrase, Haskell packages in a sub-directory don't really work with `stack ls dependencies json` at the moment. Since we want to update `rules_haskell` to a newer version, we need to address this. We can make this change now without updating the version so that the version bump of `rules_haskell` has a smaller diff. In all likelihood, this issue will be fixed at some point. Haskell packages in a sub-directory are fairly common. Until that day, we follow most of the workaround laid out in that GitHub issue: pull in the package as a `bazel` `http_archive` rule, point `stack_snapshot` to the package as a `vendored_package`. The part we do a bit differently is not stripping down to the sub-directory. Instead, we treat the whole archive as one thing and locate the files based on where they live from the top-level. We take this approach primarily because we're going to pull in both `purescript-ast` and `purescript-cst`. Since the commit we're using doesn't have a `lib/purescript-cst/purescript-cst.cabal` file, we have to patch it to add that.
We want to work around an issue with packages not at the top-level. This follows the change we made for `purescript-cst` in 8f77f15f5d388b6a17c6a216ea1644caeda609af. I.e. addressing the problem of Haskell packages in a sub-directory not really working with `stack ls dependencies json` at the moment: tweag/rules_haskell#1392 (comment).
We want to work around an issue with packages not at the top-level. It looks as though there's some issue in the newer versions of `rules_haskell` for Haskell packages that aren't at the top-level. This comment gives an overview of the problem: tweag/rules_haskell#1392 (comment). To paraphrase, Haskell packages in a sub-directory don't really work with `stack ls dependencies json` at the moment. Since we want to update `rules_haskell` to a newer version, we need to address this. We can make this change now without updating the version so that the version bump of `rules_haskell` has a smaller diff. In all likelihood, this issue will be fixed at some point. Haskell packages in a sub-directory are fairly common. Until that day, we follow most of the workaround laid out in that GitHub issue: pull in the package as a `bazel` `http_archive` rule, point `stack_snapshot` to the package as a `vendored_package`. The part we do a bit differently is not stripping down to the sub-directory. Instead, we treat the whole archive as one thing and locate the files based on where they live from the top-level. We take this approach primarily because we're going to pull in both `purescript-ast` and `purescript-cst`. Since the commit we're using doesn't have a `lib/purescript-cst/purescript-cst.cabal` file, we have to patch it to add that.
We want to work around an issue with packages not at the top-level. This follows the change we made for `purescript-cst` in 8f77f15f5d388b6a17c6a216ea1644caeda609af. I.e. addressing the problem of Haskell packages in a sub-directory not really working with `stack ls dependencies json` at the moment: tweag/rules_haskell#1392 (comment).
I have this code that I am trying to pin (I successfully pinned another stack_snapshot call):
but it failed with
Unsupported archive format
:What can I do to fix/work around it ?
The text was updated successfully, but these errors were encountered: