-
Notifications
You must be signed in to change notification settings - Fork 846
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
Error: directory-1.2.1.0-[...] is shadowed by package directory-1.2.1.0-[...] #1025
Comments
Can you test with stack master? I recently fixed a similar issue. On On Tue, Sep 22, 2015, 2:58 AM Chris Allen notifications@github.com wrote:
|
@snoyberg after a
|
That looks like you have a corrupted global package database. What's the output of:
|
|
Sorry, I meant:
|
Haven't heard back for a while, so closing. Feel free to reopen if this is still an issue. |
@borsboom no problem, sorry, I haven't had time to chase stuff like this down lately. If it resurfaces I'll run through the diagnostic procedure requested and re-open with that. |
Nope still having problems. I tried a Failure:
Diagnostic:
|
This looks like another incarnation of #1110. I've just changed the default on master to the old behavior. Can you test out master and see what happens? |
All good here hoss. Thank you sir :) |
Noooooooooo 😢
ogodwhy.jpg |
Persists after a Nuked Edit: no dice. |
It seems to me that this commit is the problem: Why do you need to override the time library? time is a dependency of Cabal, which is causing all of this wonky behavior. |
A bit more research: this is actually an impossible build for Stack (or anything else) to perform. The ghc package cannot be reinstalled or rebuilt against different installed packages, and depends on time, directory and process. You've told Stack to rebuild time, which triggers a rebuild of both process and directory as well (since they depend on it). Ideally, Stack would like to rebuild ghc as well, but it can't. The result: you end up with a build using the newly compiled time, process, and directory, and ghc package using the original time, process, and directory, resulting in the failure above. I discussed this in more detail in this blog post: https://www.fpcomplete.com/blog/2014/05/lenient-lower-bounds |
Minimal repo: resolver: lts-3.8
packages: []
extra-deps:
- time-1.5.0.1
|
https://github.com/bos/aeson/blob/master/aeson.cabal#L104-L107 I'll try avoiding needing to specify that version of Thank you very much for helping me suss this out. |
https://github.com/bitemyapp/bloodhound/tree/aeson-0.10
Repro:
stack test
stack clean
andrm -rf .stack-work
don't rectify it.Incidentally, this mirrors a problem I was having at work as well on a very different sort of project but for the same upgrade (aeson-0.10).
The text was updated successfully, but these errors were encountered: