-
Notifications
You must be signed in to change notification settings - Fork 696
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
configure incorrectly reports package as broken #1185
Comments
The top-down solver fails too, but in a different way:
It says |
@kosmikus Do you mind taking a look. You can reproduce this using GHC 7.6.1, and empty user package DB, and the latest HEAD of unordered-containers from https://github.com/tibbe/unordered-containers. You will have to run:
Before trying the above command, to make sure you have the right dependencies. The reason you have to install criterion and hashmap separately, is due to a circular dependency (cabal treats the whole package as one unit, where it ought to consider the benchmark section separately). |
@tibbe Sorry for not replying earlier. I have apparently configured my mail system such that github notifications ended up in some unimportant folder. I will try to take a look. |
@tibbe Ok, I know why this is happening, at least: the code in
The final argument is a list of package ids (in this situation, containing the
and
The TODO has been left by @dcoutts a long time ago, but I think it is accurate. Deleting stuff from the index is evil. It subsequently makes the modular solver think that the reverse dependencies of the deleted package are broken (including At the moment, I'm not quite sure how much work that would be, and whether there's a risk that something else breaks once this is done. |
Thinking about this somewhat more, I do not think that fixing this particular issue would help in any substantial way: while |
Is this still an issue? |
I was working with the new sandboxing support (which uses a package DB in
.cabal-sandbox/ghc-<version>-packages.conf.d
instead of the user package DB) when I ran into this curious error.First, Cabal claims that
aeson
is broken:However, ghc-pkg disagrees:
The text was updated successfully, but these errors were encountered: