Skip to content
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

Stackage nightly build failure for 4.9.6.0 #544

Closed
decentral1se opened this issue Jun 10, 2017 · 7 comments
Closed

Stackage nightly build failure for 4.9.6.0 #544

decentral1se opened this issue Jun 10, 2017 · 7 comments

Comments

@decentral1se
Copy link

src/Hakyll/Main.hs:73:19: error:
    • Variable not in scope:
        (<>) :: InfoMod a28 -> InfoMod a27 -> InfoMod Options
    • Perhaps you meant one of these:
        ‘<$>’ (imported from Options.Applicative),
        ‘<|>’ (imported from Options.Applicative),
        ‘<*>’ (imported from Options.Applicative)

src/Hakyll/Main.hs:113:44: error:
    • Variable not in scope: (<>) :: Mod f12 a26 -> Mod f11 a25 -> t2
    • Perhaps you meant one of these:
        ‘<$>’ (imported from Options.Applicative),
        ‘<|>’ (imported from Options.Applicative),
        ‘<*>’ (imported from Options.Applicative)

src/Hakyll/Main.hs:113:57: error:
    • Variable not in scope:
        (<>) :: t2 -> Mod f10 a24 -> Mod FlagFields Bool
    • Perhaps you meant one of these:
        ‘<$>’ (imported from Options.Applicative),
        ‘<|>’ (imported from Options.Applicative),
        ‘<*>’ (imported from Options.Applicative)

src/Hakyll/Main.hs:117:41: error:
    • Variable not in scope:
        (<>)
          :: Mod CommandFields Command
             -> Mod CommandFields Command -> Mod CommandFields Command
    • Perhaps you meant one of these:
        ‘<$>’ (imported from Options.Applicative),
        ‘<|>’ (imported from Options.Applicative),
        ‘<*>’ (imported from Options.Applicative)
(etc.)
decentral1se added a commit to commercialhaskell/stackage that referenced this issue Jun 10, 2017
@23Skidoo
Copy link
Contributor

Just bumped into this.

@23Skidoo
Copy link
Contributor

A workaround I've found is to constrain optparse-applicative to < 0.13.

@jaspervdj
Copy link
Owner

Thanks for reporting, seems like an easy fix. Looking at it now

@23Skidoo
Copy link
Contributor

So it looks like efa148c in combination with https://github.com/pcapriotti/optparse-applicative/blob/master/CHANGELOG.md#version-01300-15-aug-2016 is the culprit. Apparently @aesadde tested his change with optparse-applicative 0.12.

@jaspervdj
Copy link
Owner

I've changed the import to a qualified one which is more robust in 85d9ccd

@mihaimaruseac
Copy link
Contributor

This can be closed too, afaik.

@decentral1se
Copy link
Author

Nice one folks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants