-
Notifications
You must be signed in to change notification settings - Fork 12
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
Doesn't seem to work #1
Comments
I've updated the buildpack since the download url has changed.
I guess we have to distinguish between older and newer CF versions when fetching Erlang. |
You have to use the cflinixfs2 stack on IBM bluemix e.g.
|
Hi there, has the download url changed again? I see the same error message when trying the default erlang version along with 18 and 18.1.5: Staging...
-----> Checking Erlang and Elixir versions
WARNING: elixir_buildpack.config wasn't found in the app
Using default config from Elixir buildpack
Will use the following versions:
* Erlang 17.5
* Elixir 1.0.5
* MIX_ENV=prod
-----> Fetching Erlang 17.5
-----> Installing Erlang 17.5 (changed)
gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error is not recoverable: exiting now
/tmp/buildpacks/5f6b97ace968c8585f5c3ae25fb316da/lib/erlang_funcs.sh: line 38: /tmp/cache/erlang/Install: No such file or directory
-----> Fetching Elixir v1.0.5
-----> Installing Elixir v1.0.5 (changed)
-----> Installing Hex
/tmp/app/.platform_tools/elixir/bin/elixir: 100: exec: erl: not found
-----> Installing rebar
/tmp/app/.platform_tools/elixir/bin/elixir: 100: exec: erl: not found
-----> Fetching app dependencies with mix
/tmp/app/.platform_tools/elixir/bin/elixir: 100: exec: erl: not found
Failed to compile droplet
Exit status 223
Staging failed: Exited with status 223 |
Mmmh, I'll check |
Thanks! For more info, I was trying to deploy a starter app (the result of |
I've fixed the erlang download link. |
I'm having the same problem now with erlang 18 and elixir 1.2:
|
Please retry and report any errors. |
Using IBM Bluemix, I get this error
The text was updated successfully, but these errors were encountered: