-
-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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
cabal-install can't link pandoc-types #189336
Comments
Is it possible you're running into some sort of problem like #169332 (comment) ? |
I did |
Also, other programs I've written in Haskell (that don't use pandoc) are compiling without problems, so this doesn't seem to be a global issue. |
Huh, that's interesting. I just copied your files locally, did: $ nix-shell -p "haskellPackages.ghcWithPackages (p: [p.pandoc p.pandoc-types])" -p cabal-install And then from the shell did: $ cabal build
Warning: The package list for 'hackage.haskell.org' is 47 days old.
Run 'cabal update' to get the latest list of available packages.
Resolving dependencies...
Build profile: -w ghc-9.0.2 -O1
In order, the following will be built (use -v for more details):
- cabal-pandoc-issue-0.1.0.0 (exe:cabal-pandoc-issue) (first run)
Configuring executable 'cabal-pandoc-issue' for cabal-pandoc-issue-0.1.0.0..
Preprocessing executable 'cabal-pandoc-issue' for cabal-pandoc-issue-0.1.0.0..
Building executable 'cabal-pandoc-issue' for cabal-pandoc-issue-0.1.0.0..
[1 of 1] Compiling Main ( Main.hs, /home/illabout/temp/pandoc-types-test/dist-newstyle/build/x86_64-linux/ghc-9.0.2/cabal-pandoc-issue-0.1.0.0/x/cabal-pandoc-issue/build/cabal-pan
doc-issue/cabal-pandoc-issue-tmp/Main.o )
Linking /home/illabout/temp/pandoc-types-test/dist-newstyle/build/x86_64-linux/ghc-9.0.2/cabal-pandoc-issue-0.1.0.0/x/cabal-pandoc-issue/build/cabal-pandoc-issue/cabal-pandoc-issue ...
$ As you can see, everything appears to be working correctly. This is on 22.05 at c06d5fa on x86_64-linux. I thought maybe it was a problem with $ nix-shell -p "haskellPackages.ghcWithPackages (p: [p.pandoc p.pandoc-types])" -p cabal-install -I nixpkgs=channel:nixos-unstable And then did: $ rm -rf ~/.cabal/{packages,store}
$ cabal update
$ cabal build
Resolving dependencies...
Build profile: -w ghc-9.0.2 -O1
In order, the following will be built (use -v for more details):
- cabal-pandoc-issue-0.1.0.0 (exe:cabal-pandoc-issue) (first run)
Configuring executable 'cabal-pandoc-issue' for cabal-pandoc-issue-0.1.0.0..
Preprocessing executable 'cabal-pandoc-issue' for cabal-pandoc-issue-0.1.0.0..
Building executable 'cabal-pandoc-issue' for cabal-pandoc-issue-0.1.0.0..
[1 of 1] Compiling Main ( Main.hs, /home/illabout/temp/pandoc-types-test/dist-newstyle/build/x86_64-linux/ghc-9.0.2/cabal-pandoc-issue-0.1.0.0/x/cabal-pandoc-issue/build/cabal-pan
doc-issue/cabal-pandoc-issue-tmp/Main.o )
Linking /home/illabout/temp/pandoc-types-test/dist-newstyle/build/x86_64-linux/ghc-9.0.2/cabal-pandoc-issue-0.1.0.0/x/cabal-pandoc-issue/build/cabal-pandoc-issue/cabal-pandoc-issue ... Which also works. This is on 2da64a8. So my best guess is that this is some problem on your system, but if you already tried |
Thank you for trying. I'll experiment a bit and see if I can narrow down the problem any further. In the meantime, just to check my own sanity, here's a test i did just now. As you can see, I removed
|
Curiouser and curiouser! I checked my nix-store, and there seems to be an issue with pandoc-type, among other packages. ❯ nix store verify --all |
Solved! After checking the store for problems with
And now it builds! |
Oh nice, good solve! I definitely wouldn't have thought to check the health of the |
Describe the bug
Today I ran
sudo nixos-rebuild switch --upgrade
, and suddenly none of the pandoc filters that I have developed will build.Steps To Reproduce
Steps to reproduce the behavior:
pandoc-types
.Expected behavior
Cabal-install should be able to link this.
Screenshots
Not applicable.
Additional context
Not applicable.
Notify maintainers
@sternenseemann
Metadata
Please run
nix-shell -p nix-info --run "nix-info -m"
and paste the result.The text was updated successfully, but these errors were encountered: