-
-
Notifications
You must be signed in to change notification settings - Fork 14.5k
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
Nix fails when Cabal 2.4 wildcard paths feature is used #64173
Comments
I took a look at this, but I am having trouble getting the branch you linked to working with just plain At the end of the nix-build for Haskell packages, nixpkgs/pkgs/development/haskell-modules/generic-builder.nix Lines 409 to 413 in f3282c8
This is what is failing. However, I couldn't figure out why this would be failing, so I tried to reproduce it with just Each of these commands appears to fail as well. First, the setup for running $ git clone ...
$ cd ormolu/
$ nix-shell Now try with
Try with
Try with
The cabal documentation suggests that the https://cabal.readthedocs.io/en/latest/developing-packages.html#pkg-field-data-files |
The corresponding Cabal issue appears to be fixed now. |
Issue description
Nix fails when Cabal 2.4 wildcard paths feature is used. The feature allows us to use
**
in paths when we specify collections of e.g. data files. Instead of respecting that, current nixpgks creates a directory literally called**
and so install phase fails because of that.Steps to reproduce
Clone this branch of Ormolu:
tweag/ormolu#149
where I try to make use of the feature.
Then just do
nix-build
.The failure is also visible in respective Circle CI logs here:
https://circleci.com/gh/tweag/ormolu/535?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-checks-link
Technical details
"x86_64-linux"
Linux 4.19.34, NixOS, 19.03.git.f52505f (Koi)
yes
yes
nix-env (Nix) 2.3pre6631_e58a7144
"nixos-18.09.2337.5d972dd2c94"
/home/mark/nixpkgs
(I don't believe the info has any significance in this case.)
The text was updated successfully, but these errors were encountered: