-
Notifications
You must be signed in to change notification settings - Fork 701
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
add-source deps are not reinstalled when LBI can't be loaded #3136
Labels
Milestone
Comments
23Skidoo
added a commit
to 23Skidoo/cabal
that referenced
this issue
Feb 12, 2016
But only if it happens due to version mismatch. Fixes haskell#3136.
23Skidoo
added a commit
to 23Skidoo/cabal
that referenced
this issue
Feb 12, 2016
But only if it happens due to version mismatch. Fixes haskell#3136.
23Skidoo
added a commit
to 23Skidoo/cabal
that referenced
this issue
Feb 13, 2016
But only if it happens due to version mismatch. Fixes haskell#3136.
23Skidoo
added a commit
to 23Skidoo/cabal
that referenced
this issue
Feb 18, 2016
But only if it happens due to version mismatch. Fixes haskell#3136.
23Skidoo
added a commit
to 23Skidoo/cabal
that referenced
this issue
Feb 20, 2016
But only if it happens due to version mismatch. Fixes haskell#3136.
23Skidoo
added a commit
to 23Skidoo/cabal
that referenced
this issue
Feb 20, 2016
But only if it happens due to version mismatch. Fixes haskell#3136.
23Skidoo
added a commit
to 23Skidoo/cabal
that referenced
this issue
Feb 21, 2016
But only if it happens due to version mismatch. Fixes haskell#3136.
sandbox functionality is removed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reinstallation of add-source deps is done in
reconfigure
, and that function silently ignores bad version errors and returns when loading LBI fails. This can happen when a package is usingbuild-type: Custom
and the setup script is built against a different version of Cabal thancabal-install
. So changes in add-source deps are ignored in this case.The text was updated successfully, but these errors were encountered: