-
Notifications
You must be signed in to change notification settings - Fork 71
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
New-style build fails during "sdist" #81
Comments
@peti you should remove Could you submit a PR? |
Thank you for the suggestion! The changed removed the error. Unfortunately, now a new error just popped up (https://travis-ci.org/peti/hsyslog/jobs/235778854) which I believe to be unrelated to the travis-ci build instructions, though. |
@peti, are you sure you use: https://github.com/phadej/cabal-doctest/blob/master/example/Setup.hs like |
Man, this has been a long journey. :-/ Now the tests succeed with GHC 8.x, but none of the other compilers can build the project, apparently because the latest |
@peti you don't need to put The situation is a bit tricky:
|
….*, too If `dist/` is deleted but .ghc.environment.* is not, then the repository is in a state that's going to confuse Cabal. Fixes #81.
OK, I see. I took the https://travis-ci.org/peti/hsyslog/jobs/235963325 Any idea how |
@peti I'm not sure yet (still looking), this seems to occur only with Cabal-1.22, but setting EDIT: Now I see it; this is the infamous |
Okay, thank you very much for looking at the issue. I've moved the
instead. When I add the |
Your package most likely lacks a |
Phew, https://travis-ci.org/peti/hsyslog/builds/237107742 now succeeds on all platforms. Thank you very much for taking the time to walk me through this process, gentlemen. |
I have a strange build failure at https://travis-ci.org/peti/hsyslog/jobs/234171806:
That .travis.yml file was generated with the current version (3e1b384) of make_travis_yml_2.hs and that error makes no sense to me. When I run
cabal dist
locally, it works just fine. Any idea what I could do to fix this issue?The text was updated successfully, but these errors were encountered: