Created attachment 212924 [details]
also available at https://git.sr.ht/~dch/ports/commit/12b326bbb80dde0a474dcf962cd08333cdee95ae
added + from erlang@
New failure log on 11.3 i386:
New failure log on 11.3 amd64:
thanks Antoine. I was expecting that we'd see more than just a single port failure here, and that we could get an exprun that covers more than just 11.3R, which I can do locally.
What's the normal scope for an exp-run? Can it be done to continue even after first port failure?
(In reply to Dave Cottlehuber from comment #4)
I believe that on 12.1 the new failures were the same as on 11.3
> ** (Mix) You're trying to run :rabbitmqctl on Elixir v1.10.2 but it has declared in its mix.exs file it supports only Elixir >= 1.7.0 and < 1.10.0
Can someone running rabbitmq just patch their port locally to lift this restriction and verify things still work? I suspect this is just rabbitmq being overly cautious.
wrt rabbitmq, see r532229 this was already addressed in 3.8.3 upstream.
I plan to remove the 4 remaining ports as they have not worked in ages:
I personally see little value of having elixir & erlang libraries directly
in the tree, unless they have C dependencies (NIFs) or port drivers. I
know very few people who distribute BEAM applications without a release