-
Notifications
You must be signed in to change notification settings - Fork 711
--exact-conf
complains about unspecified flags, even when they're default and/or explicitly given
#4769
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
Comments
I've started bisecting the problem from 84e41e4 (good). |
|
No, it's actually 69e496a. |
/cc @phadej |
I am just seeing this in the Agda repo with
When trying to install
The |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
With the c480f69 version of cabal-install:
It doesn't actually make any difference here whether I add the
--flags="semigroups tagged"
, the error is the same without that. (Which isn't completely surprising because the flags should anyway be on by default, what's surprising is that, allegedly, they aren't on.)Verbose version:
This originally happened when I (for the first time) tried to
new-build
one of my packages instead of old-styleinstall
ing it, namely free-vector-spaces. This attempt can't have broken any global configuration that now causes the issue even with standardinstall
fordistributive
andbytes
, can it?At least I reckon it was the
new-build
that turned on--exact-conf
, but what that really means I don't understand.The text was updated successfully, but these errors were encountered: