Rebar3: annoying message about rebar_vsn_plugin

Questions / Help
1

Hi rebar3 experts,

$ sw_vers
ProductName:		macOS
ProductVersion:		13.6.6
BuildVersion:		22G630

$ rebar3 version
rebar 3.22.0 on Erlang/OTP 26 Erts 14.2.1

$ cat  ~/.config/rebar3/rebar.config
{plugins, [rebar3_auto]}.

$ vi rebar.config
...
{project_plugins, [ rebar3_auto
                  , rebar3_autotest
                  , rebar3_edoc_extensions
                  , rebar3_hank
                  , rebar3_hex
                  , rebar3_proper
                  , rebar3_typer ]}.

$ rebar3 compile
===> Verifying dependencies...
===> Failed to update package rebar_vsn_plugin from repo hexpm
===> Errors loading plugin rebar_vsn_plugin. Run rebar3 with DEBUG=1 set to see errors.
===> Analyzing applications...
[...]

$ DEBUG=1 rebar3 compile
[...]
 <<"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<Error><Code>AccessDenied</Code><Message>Access Denied</Message><RequestId>SBX3WSG1CQWM1K3K</RequestId><HostId>Iew7Q2sjew2ooTmBfy6VCW5DPM91VTtf53VEIPTpV9AJnnh===> Failed to update package rebar_vsn_plugin from repo hexpm
===> Failed to update package rebar_vsn_plugin from repo hexpm
===> throw {error,
                      {rebar_app_utils,
                          {missing_package,<<"rebar_vsn_plugin">>,undefined}}} [{rebar_app_utils,
                                                                                 update_source,
                                                                                 3,
                                                                                 [{file,
                                                                                   "/erlang/libs/rebar3/apps/rebar/src/rebar_app_utils.erl"},

What should I set in rebar.config to get rid of this message?
===> Failed to update package rebar_vsn_plugin from repo hexpm

Thanks

2

rebar_vsn_plugin was a rebar 2.x plugin.

One of your apps or dependencies possibly declares it in its rebar.config file, particularly if it’s an old one—Rebar 2.x and Rebar3 both had {plugins, [...]} config values, but the interpretation is different between them.

Any hex dependency you use is unlikely to be the culprit because a hex dep needs to have all of its own deps also be on hex.

1 Like
3

@MononcQc thanks a lot. Indeed, by deleting the dependency containing rebar_vsn_plugin, all is good.