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 2.2 fails on package descriptions that earlier versions of Cabal were able to parse #5513
Comments
Well, a package description consisting merely of
was never truly legitimate to begin with. In the past, the validation for the The problem is that you used
|
+1 on making that warning an error. |
@hvr thanks for pointing that out. I indeed tried What I still don't get is why this is reported as a warning first and then only later on parsing fails? But I assume you guys can point out that this is yet an other user error. |
Btw, if you use
|
Apparently here is the offending code
Still a bug by my book, but hey try to convince me otherwise. |
To elaborate on that, from what I understand is happening here:
|
While looking into this I was surprised that my code changes are not picked up by |
Sorry, @sol, but you are not in a position to tell me how to do software or particularly To my defense (though I don't think I need to defend myself at all) that particular change was done very close to If those are the thanks for that work, than I'm just speechless. |
Steps to reproduce:
Create a file
foo.cabal
and in
ghci
observeApparently
version
is now required to make this parse. At the very least I would hope for a better error message. I meanFailed parsing "foo.cabal".
? Come on guys, seriously?The text was updated successfully, but these errors were encountered: