search

erlware / relx

Sane, simple release creation for Erlang
http://erlware.github.io/relx
Apache License 2.0
697 stars 232 forks source link

Relup with rebar3 generation fails for the second time #550

Closed marjaimate closed 7 years ago

marjaimate commented 7 years ago

Hi there,

I've bumped into an issue described here in rebar3. I've been using relflow, with rebar3 and it works for the first upgrade running:

But the next upgrade - going from 2 to 3 - gives me "relup not found" error:

$ rebar3 as prod release relup -u "2" -o /usr/local/app/
===> Verifying dependencies...
===> Compiling app
===> Running erlydtl...
===> Starting relx build process ...
===> Resolving OTP Applications from directories:
          /home/work/app/_build/prod/lib
          /home/work/app/ebin
          /usr/local/lib/erlang/lib
          /usr/local/app
===> Resolving available OTP Releases from directories:
          /home/work/app/_build/prod/lib
          /usr/local/app
===> Resolved app-2
===> Including Erts from /usr/local/lib/erlang
===> release successfully created!
===> Upfrom release version (2) for relup not found

Could you give me some pointers on what I'm doing wrong here?

(Note: versions and name are masked)

lrascao commented 7 years ago

Do you have a public repo where this is happening?

marjaimate commented 7 years ago

@lrascao no, it's a private repo and I can't share it unfortunately... but it's fairly simple OTP app, using webmachine as its main dependency.

lrascao commented 7 years ago

any chance of narrowing the problem down to a simple release that you could share?

marjaimate commented 7 years ago

I've experimented with the various order of using 'release', 'tar' and 'upgrade' and managed to get it working. I'll dig up the exact order that it worked for me.

Note: there was/is an underlying issue as well, with a dependency's config that only manifested on relups. I think after I got that resolved, this was fixed as well. I'll double check next week to confirm.

On 5 Jan 2017 00:22, "Luis Rascão" notifications@github.com wrote:

any chance of narrowing the problem down to a simple release that you could share?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/erlware/relx/issues/550#issuecomment-270526702, or mute the thread https://github.com/notifications/unsubscribe-auth/ABNs4wsVz1cVBSE8J1oOCxxomhiLPnpGks5rPDfWgaJpZM4LFh0R .

marjaimate commented 7 years ago

I think we can close this. The upgrade works, when I'm running the rebar3 command in the order of:

$ rebar3 as prod release tar relup -u 'SOME_VERSION'

One of my dependencies (webmachine) is not behaving well on upgrade, but that's not relevant for this. I think this issue can be closed.