Rebar3 release/upgrade problems: ERROR: release_handler:install_release failed: {enoent

[vances]

I’ve raised the question about the generation of relup specifications as a Day 1 or Day 2 operation in this thread:

Release upgrade specifications: day 1 or day 2?

We ship software in releases. When we ship a new release it may be installed as a fresh system or applied to one which is already in production. The sasl application provides tools for runtime release handling. We can use release_handler:install_release/1 to upgrade a running system, which leverages the power of hot code loading. The release package has to have first been unpacked with release_handler:unpack_release/1. A release package may be prepared for shipping using systools:make_tar/1,2. …

As part of the solution to the Day 1 approach I submitted pull request #8973 which includes all available appup specifications in a release package.