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
Custom tasks fail with Erlang/OTP 21 (nonexistent no_dot_erlang.boot
file)
#426
Comments
Here it is erlang/otp@11fcc4b#diff-ca4358fbed781931ba20cdecd94e3ac0R258 Seems that default boot script was changed |
How would this be handled to support both OTP21 and older? |
We just need to be explicit about the boot script we are targeting when executing commands. |
I'm planning to cut a new release on Monday, FYI |
Awesome, thanks @bitwalker. Everything else is working fine, so will test that release to check commands work and let you know 👍. |
In relx we just always create the |
@bitwalker Any news on this? Any way I can help? |
This is fixed in 1.5.3 (on Hex) and in master for the 2.x work |
Can confirm that 1.5.3 works as it did before, thank you so much! 🎉 |
All working. Thank you so much! ✨ |
use erlang version >= 21.1.1 |
Steps to reproduce
After building a release with the new Elixir 1.6.6 and Erlang/OTP 21, I'm unable to run custom release tasks.
N.B: this didn't happened with the previous Erlang/OTP 20.1. The application still runs OK (e.g.
console
,foreground
, etc.)I get the following error:
This is the
bin
folder content:If I copy the
start_clean.boot
tono_dot_erlang.boot
, everything works as expected.Maybe Erlang/OTP 21 changed the name of the
.boot
file it generates?Verbose Logs
Description of issue
What are the expected results?
I should be able to run my custom task.
What OS, Erlang/Elixir versions are you seeing this issue on?
Linux (Debian container), Elixir 1.6.6, Erlang/OTP 21.
If possible, also provide your
rel/config.exs
, as it is oftenmy first troubleshooting question, and you'll save us both time :)
The text was updated successfully, but these errors were encountered: