Date: Wed, 12 Nov 2025 15:19:23 +0000 From: bugzilla-noreply@freebsd.org To: erlang@FreeBSD.org Subject: [Bug 290976] net/eturnal: bump PORTREVISION (preferrably always) after updating lang/erlang Message-ID: <bug-290976-38768@https.bugs.freebsd.org/bugzilla/>
index | next in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=290976 Bug ID: 290976 Summary: net/eturnal: bump PORTREVISION (preferrably always) after updating lang/erlang Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: marko.cupac@mimar.rs CC: erlang@FreeBSD.org, yzrh@noema.org CC: erlang@FreeBSD.org, yzrh@noema.org Created attachment 265363 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=265363&action=edit Bump PORTREVISION after lang/erlang update Hi, this is the third PR with same topic - eturnal does not start after erlang updates. Apparently it needs to be recompiled against every new erlang version, even if it is minor point release such as 26.2.5.15,4 -> 26.2.5.16,4 in this particular case. This time error message was different, eturnal would start when run in foreground with sudo -u eturnal eturnalctl foreground`, but not when starting with `service eturnal start`. Attempting to start it with command from rc script would give the following: # su eturnal -c "env ERL_EPMD_ADDRESS=\"127.0.0.1\" RUNNER_LOG_DIR=\"/var/log/eturnal\" /usr/local/sbin/eturnalctl daemon" Can not run the release. There is no ERTS bundled with the release or found on the system. Bumping PORTREVISION, rebuilding in poudriere and installing new eturnal version by means of pkg resulted eturnal starting and running as expected. I have attached patch to bump PORTREVISION. Who could communicate with lang/erlang maintainers to do it automatically? Regards, -- You are receiving this mail because: You are on the CC list for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-290976-38768>
