We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
(duplicate of #981 ?)
I was building a harmless doc patch, and got this error
tidal > /home/runner/work/Tidal/Tidal/src/Sound/Tidal/Tempo.hs:9:1: error: tidal > Could not find module ‘Sound.Osc.Fd’ tidal > Perhaps you meant Sound.OSC.FD (from hosc-0.18.1)
https://github.com/tidalcycles/Tidal/actions/runs/3817947807/jobs/6494527178#step:6:1006
only for the "stack resolver" job. the other jobs (cabal-* ghc-*) look fine.
indeed I can reproduce this locally, and the WARNING looks suspicious. I don't know that I enable allow-newer (which means -older in this case)
stack test --resolver=lts-20.5 WARNING: Ignoring tidal's bounds on hosc (>=0.20 && <0.21); using hosc-0.18.1. Reason: allow-newer enabled.
Oh - stack.yaml pins the old hosc version. Do we want that?
The text was updated successfully, but these errors were encountered:
Do we want that? - Probably not, since tidal.cabal gives a different version for hosc.
tidal.cabal
Sorry, something went wrong.
But then, a nix build fails.
> Configuring tidal-1.9.3... > > Setup: Encountered missing or private dependencies: > hosc >=0.20 && <0.21
https://github.com/tidalcycles/Tidal/actions/runs/3818126963/jobs/6494827536
I thought this was easy, but perhaps it isn't.
66a6121
Merge pull request #989 from jwaldmann/fix-988
ba97ca5
fix #988
Hopefully the nix build is just lagging a bit with the hosc package and it'll all come out in the wash.
No branches or pull requests
(duplicate of #981 ?)
I was building a harmless doc patch, and got this error
https://github.com/tidalcycles/Tidal/actions/runs/3817947807/jobs/6494527178#step:6:1006
only for the "stack resolver" job. the other jobs (cabal-* ghc-*) look fine.
indeed I can reproduce this locally, and the WARNING looks suspicious. I don't know that I enable allow-newer (which means -older in this case)
Oh - stack.yaml pins the old hosc version. Do we want that?
The text was updated successfully, but these errors were encountered: