-
Notifications
You must be signed in to change notification settings - Fork 844
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 solver doesn't find setup-depends #3044
Comments
The issue is likely that you have an older version of cabal-install installed. Check
In 38f67e8 I've added the following warning to make this clearer:
|
I have
And it doesn't work in current HEAD (after your commit):
To be clear I have the following import Distribution.Simple
import Acme.Missiles
main = defaultMain And the following resolver: lts-8.3 (Although it doesn't work with I get the following during
And the following during
I've just installed the latest
However my
|
Hmm, strange! Re-opening as need repro
Shouldn't be an issue, but I suppose it's worth a shot using just the standard |
Rebuild with stack.yaml:
Still the same problem. How can I help reproduce? Or investigate the problem myself |
Ahah! I think I figured it out. It skips running the solver if all the deps are contained in the snapshot. It was using functions that didn't count setup dependencies as dependencies of the package. The resolution to http://github.com/fpco/stack/issues/3035 fixes this problem as well. It was merged back to master quite recently, after the commit that you're on. So I believe this should now be fixed! |
Works for me too, good job!
BTW stack itself builds just fine with LTS-8.4 |
General summary/comments (optional)
When building a package with setup-depends dependency which is not in the snapshot,
stack solver reports no problems but subsequent builds recommend adding an extra-dep.
Steps to reproduce
acme-missiles-0.3
as anextra-dep
stack solver
.Expected
acme-missiles-0.3 is recommended
Actual
It says stack.yaml is ok
Stack version
Method of installation
The text was updated successfully, but these errors were encountered: