-
Notifications
You must be signed in to change notification settings - Fork 7
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
Don't repair install-plans of alex
!
#321
Comments
They cannot be repaired, even you get
The FYI: |
Thanks for the insight, @phadej ! Based on the verdict
Following these results, I revised
Well, I still had So, I am going to undo my revision. Also, in the light of haskell/cabal#7808 I am no longer sure what the FAIL(pkg) verdict of matrix.hackage means. Because the following experiments might have different outcome.
Perhaps matrix.hackage should make the setup of its experiment explicit, so its verdicts can be interpreted more precisely. |
|
I wrote:
So I thought, but looks I went down a one-way street. My attempt to revert the revision is failing with:
Well, extensionally my revision did not make much of a difference..., so this is not a catastrophy.
Yeah, not so auspicious... (More like famous last words...) :-D |
alex
alex
!
alex < 3.2.2
is listed as broken on matrix.hackage.E.g. the build log for https://matrix.hackage.haskell.org/#/package/alex/3.2.1/ghc-8.2.2@1616116046 says:
Maybe the fix is to add
build-tools: happy
.However, this could have been omitted on purpose.
Note that instead the tarball contains preprocessed versions of the lexer (
.x
) and parser (.y
) definitions:So maybe
alex-3.2.1
was relying on the preprocessed versions to be picked up bycabal
?P.S.: How auspicious, getting issue number #321 to repair
alex-3.2.1
. :)The text was updated successfully, but these errors were encountered: