-
-
Notifications
You must be signed in to change notification settings - Fork 156
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
Improve error message when given NoHackageTarballFound
#530
Comments
Probably best to implement |
A less invasive fix might be to just catch |
Thanks again. I'd like to try to create a pull request with the less invasive fix (it'll be helpful for me even though the PR is rejected in the end for the more invasive approach). Where should the exception be caught, in your opinion? Trying to follow the exception:
|
I'd be tempted to put it at the highest level, that way it's most resilient to future code reorganizations. If, going forward, there's any other useful information to attach to exceptions then it can all take place in one top-level function. |
I'm working on giving it a shot, but am stuck at the moment. Will try more later. What I've got:
Edit: It seems to me that I can't use Edit2: I think that this would work:
but I'm having problems importing Edit3: I'm stuck at the problem that I'm not able to import the module that has the exception type. |
@stianlagstad That package has no explicit export list so everything in it should be exported. Also it’s listed as an exported module. Have you inserted an |
Thanks @maralorn ! I was indeed having problems importing it. I think that this is something that would work:
|
I ran into this issue today, and found this: #423. The solution, as stated in that thread, was to run
cabal update
. Could that be a hint that's given along with theNoHackageTarballFound
error? To save others from googling in the future.(I wasn't sure whether to create this issue here or in https://github.com/NixOS/hackage-db.)
The text was updated successfully, but these errors were encountered: