-
Notifications
You must be signed in to change notification settings - Fork 842
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
"MulipleResultsBug" #6046
Comments
I solved my own problem by deleting the cache and building again, but this still seems like non-optimal behavior. |
@jgm, thanks for reporting. I see that, at the very least, I need to fix how that bug is reported by Stack. |
I can reproduce this bug locally on Windows by:
|
Some notes for my own use:
Is the problem 'unregistering'? When local |
@jgm, I have proposed a pull request that I believe fixes this. My diagnosis was that something was amiss with the unregistering of a local package for a sub library of a parent package that was itself to be unregistered. |
Great - I can't comment on the pull, as I don't know how stack works, but that seems plausible to me. |
Also adds documentation. Also adds an integration test.
Fix #6046 Unregister local packages for sub libraries
We're running into a stack bug with internal libraries. See commercialhaskell/stack#6046.
We're running into a stack bug with internal libraries. See commercialhaskell/stack#6046.
General summary/comments (optional)
I'm getting a MulipleResultsBug (sic) on stack builds in CI for pandoc.
Steps to reproduce
See https://github.com/jgm/pandoc/actions/runs/4038196626/jobs/6942025643 or any of the recent pandoc CI builds.
Expected
Expected project to build normally.
Actual
pandoc has an internal library xml-light, and it seems that the problem here is that stack is finding two copies, one cached from pandoc 3.0 and one from pandoc 3.0.1.
I would have thought stack would know to use the one from pandoc 3.0.1.
Stack version
2.9.3 installed on GitHub actions Windows 2019 CI VM.
Method of installation
CI
Platform
Windows 2019
The text was updated successfully, but these errors were encountered: