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.

Sign up for GitHub

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

Jump to bottom

Version of Cabal being used has changed #42

Closed
rehno-lindeque opened this issue Apr 13, 2014 · 3 comments
Closed

Version of Cabal being used has changed #42

rehno-lindeque opened this issue Apr 13, 2014 · 3 comments

Comments

@rehno-lindeque
Copy link
Contributor

I very often get this error:

cabal: You need to re-run the 'configure' command. The version of Cabal being
used has changed (was Cabal-1.18.1.2, now Cabal-1.18.1).

...when rebuilding from scratch. I'm not quite sure why!
@rehno-lindeque
Copy link
Contributor Author

Changing the Procfile from

web: cabal run -- Staging -p $PORT

to

web: ./dist/build/myapp/myapp Staging -p $PORT

seems like it might fix the issue.

rehno-lindeque added a commit to rehno-lindeque/heroku-buildpack-ghc that referenced this issue Apr 13, 2014
@rehno-lindeque
Cabal run sometimes breaks
4a5d0c8 
As I've mentioned in begriffs#42 I sometimes get this error when running `cabal run`

    cabal: You need to re-run the 'configure' command. The version of Cabal being
    used has changed (was Cabal-1.18.1.2, now Cabal-1.18.1).

I'm not sure if this is the best fix to be honest, but since the app should already be built in the buildpack, it should be ok to simply run it directly. (I think that perhaps `cabal run` detects changes in the file's timestamps and tries to rebuild them unnecessarily.)
rehno-lindeque added a commit to rehno-lindeque/heroku-buildpack-ghc that referenced this issue Apr 13, 2014
@rehno-lindeque
Cabal run sometimes breaks
5095d02 
As I've mentioned in begriffs#42 I sometimes get this error when running `cabal run`

    cabal: You need to re-run the 'configure' command. The version of Cabal being
    used has changed (was Cabal-1.18.1.2, now Cabal-1.18.1).

I'm not sure if this is the best fix to be honest, but since the app should already be built in the buildpack, it should be ok to simply run it directly. (I think that perhaps `cabal run` detects changes in the file's timestamps and tries to rebuild them unnecessarily.)
rehno-lindeque added a commit to rehno-lindeque/heroku-buildpack-ghc that referenced this issue Apr 13, 2014
@rehno-lindeque
Cabal run sometimes breaks
a03a88e 
As I've mentioned in begriffs#42 I sometimes get this error when running `cabal run`

    cabal: You need to re-run the 'configure' command. The version of Cabal being
    used has changed (was Cabal-1.18.1.2, now Cabal-1.18.1).

I'm not sure if this is the best fix to be honest, but since the app should already be built in the buildpack, it should be ok to simply run it directly. (I think that perhaps `cabal run` detects changes in the file's timestamps and tries to rebuild them unnecessarily.)
@rehno-lindeque rehno-lindeque mentioned this issue Apr 13, 2014
Closed
@begriffs begriffs mentioned this issue Apr 23, 2014
Merged
@rehno-lindeque
Copy link
Contributor Author

I think we can close this for now - it seems to have been resolved by either/both reusing the anvil cache when doing a git push heroku and also by not using cabal run. I actually think that using cabal run might work now , but it seems to me that it's an unnecessary step so I suggest we keep it the way it is now unless there's a compelling reason to use cabal run. If that makes sense, then let's close it!

@rehno-lindeque
Copy link
Contributor Author

Oh sorry, I forgot about this #43 (comment)

I think it's fine now, I'm closing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rehno-lindeque