-
Notifications
You must be signed in to change notification settings - Fork 691
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
cabal install is producing rather useless error messages #1914
Comments
I tried to reproduce this, but |
Maybe the download failed, so the log file was never created. |
Indeed. Disable or disconnect the network before running the command. Compare cabal's message with those produced by other tools under the same conditions:
|
Yes, this should be fixed. |
A different issue but somewhat related, is that truncated error log (10 last lines) are completely useless. Specially with ghc being on the verbose side, it's very often that the line number is not even displayed if there's an error. Is there a reason that the error log are reported truncated in the first place ? and would it make sense to have a bigger default value (50 ? 100 ?) ? |
This is fixed in master, we print the full error log now. |
@23Skidoo: awesome, thanks. I'll update my versions. |
I think I just got the same behavior:
So ghc-paths failed to install, then immediately installed without complaint. |
I encountered this issue; the cause was that packages in the repo-cache were owned by root and not readable by the user account. Deleting the package from the repo-cache resolved the issue Improved error reporting would help a great deal. |
So I managed to trigger (a variant of) this error in a simple way — just set a non-existent proxy (I use
|
Closing in favor of more "synthetic" #3073. |
Consider this example, and now go figure out what the actual problem is:
The text was updated successfully, but these errors were encountered: