[erlang-questions] erlpass issue

Fred Hebert mononcqc@REDACTED
Mon Nov 30 21:28:55 CET 2015


If you're still on rebar2, use the prior-to-last tagged version. I 
recently bumped it to rebar3 and that broke rebar2 support 
inadvertently.

If using rebar2, you should *never* rely on the master branch because 
the tool itself does not support automatically converting that to a 
stable reference. Rebar3 would instead generate a lock file that ensures 
you keep using the proper version, though.

Let me know if that helps.

Regard,
Fred.

On 11/30, lloyd@REDACTED wrote:
>Hi Fred,
>
>Hope all is well and life is giving you many grins. Sorry to bother you, but I've run into the following mystery with erlpass:
>
>I've configured erlpass as a dependency in different two Nitrogen apps--- wgb and wgc.
>
>Here, respectively, are the two rebar configurations:
>
>wgb---
>
>    {erlpass,          "",    {git, "git://github.com/ferd/erlpass",                    {branch, master}}},
>
>wgc---
>
>    {erlpass,          "",    {git, "git://github.com/ferd/erlpass",                    {branch, master}}},
>
>To my eye they look to be the same. But, when I execute make, wgb compiles:
>
>make[1]: Leaving directory `/home/lloyd/wgb/lib/bcrypt/c_src'
>==> erlpass (compile)
>==> nitrogen_tinymce (compile)
>
>But wgc doesn't:
>
>==> erlpass (compile)
>ERROR: compile failed while processing /home/lloyd/wgc/lib/erlpass: {'EXIT',{badarg,[{io,format,
>                     [<0.24.0>,"Dependency not available: ~p-~s (~p)\n",
>                      [bcrypt,
>                       {git,"https://github.com/opscode/erlang-bcrypt.git",
>                            {branch,"master"}},
>                       undefined]],
>                     []},
>                 {lists,foreach,2,[{file,"lists.erl"},{line,1337}]},
>                 {rebar_deps,do_check_deps,1,[]},
>                 {rebar_deps,compile,2,[]},
>                 {rebar_core,run_modules,4,[]},
>                 {rebar_core,execute,6,[]},
>                 {rebar_core,maybe_execute,8,[]},
>                 {rebar_core,process_dir1,7,[]}]}}
>make: *** [compile] Error 1
>
>And I'm stuck. Any thoughts on how  clear up this strange state of affairs?
>
>All the best,
>
>Lloyd
>
>
>



More information about the erlang-questions mailing list