[Bug 282263] net-im/ejabberd: update to 24.X

From: <bugzilla-noreply_at_freebsd.org>
Date: Tue, 22 Oct 2024 11:05:21 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282263

            Bug ID: 282263
           Summary: net-im/ejabberd: update to 24.X
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: ashish@FreeBSD.org
          Reporter: marko.cupac@mimar.rs
          Assignee: ashish@FreeBSD.org
             Flags: maintainer-feedback?(ashish@FreeBSD.org)

Hi,
ejabberd in ports is at 23.10 (from october of 2023), while there have been
multiple 24.x releases in the meantime. Current version is 24.07 (from july of
2024):

https://github.com/processone/ejabberd/releases

FreeBSD's net-im/ejabberd port has been mostly kept up to date with upstream
last few years. Is something blocking the upgrade?

I tried to update the port myself by bumping Makefile's PORTVERSION to 24.07
and *_VER to corresponding values in rebar.lock, as well as fixing patches in
files/ that did not apply cleanly. I managed to generate pkg-plist and start
build in poudriere, but I got errors in cofigure phase, and build finally
failed in build phase (see below). I'm stuck and out of ideas (not that I'm
much of a porter anyway).

Is anyone working on an upgrade? Is there anything I can do to help?

=======================<phase: configure      >============================
(...)
checking for cc option to enable C11 features... none needed
checking for SQLite3 library >= 3.6.19... yes
build tool to use (change using --with-rebar): ./rebar3
configure: creating ./config.status
config.status: creating Makefile
config.status: creating vars.config
configure: unlocking disabled rebar3 dependencies: epam,eredis,esip,p1_pgsql,
===> Newly added dep jiffy is locked at a lower level. If you really want to
unlock it, use 'rebar3 upgrade jiffy'
===> Analyzing applications...
===> Compiling configure_deps
===> Failed to update package rebar3_hex from repo hexpm
===> Errors loading plugin {rebar3_hex,"~> 7.0.8"}. Run rebar3 with DEBUG=1 set
to see errors.
===> Failed to update package provider_asn1 from repo hexpm
===> Errors loading plugin {provider_asn1,"0.2.0"}. Run rebar3 with DEBUG=1 set
to see errors.
===> Failed to update package pc from repo hexpm
===> Errors loading plugin {pc,"~> 1.15.0"}. Run rebar3 with DEBUG=1 set to see
errors.

=======================<phase: build          >============================
(...)
./rebar3 get-deps && :> _build/default/lib/.got
===> Newly added dep jiffy is locked at a lower level. If you really want to
unlock it, use 'rebar3 upgrade jiffy'
===> Analyzing applications...
===> Compiling configure_deps
===> Failed to update package rebar3_hex from repo hexpm
===> Errors loading plugin {rebar3_hex,"~> 7.0.8"}. Run rebar3 with DEBUG=1 set
to see errors.
===> Failed to update package provider_asn1 from repo hexpm
===> Errors loading plugin {provider_asn1,"0.2.0"}. Run rebar3 with DEBUG=1 set
to see errors.
===> Failed to update package pc from repo hexpm
===> Errors loading plugin {pc,"~> 1.15.0"}. Run rebar3 with DEBUG=1 set to see
errors.
===> Failed to update package rebar3_hex from repo hexpm
===> Errors loading plugin {rebar3_hex,"~> 7.0.8"}. Run rebar3 with DEBUG=1 set
to see errors.
===> Failed to update package provider_asn1 from repo hexpm
===> Errors loading plugin {provider_asn1,"0.2.0"}. Run rebar3 with DEBUG=1 set
to see errors.
===> Failed to update package pc from repo hexpm
===> Errors loading plugin {pc,"~> 1.15.0"}. Run rebar3 with DEBUG=1 set to see
errors.
===> Verifying dependencies...
===> Failed to update package cache_tab from repo hexpm
===> Package not found in any repo: cache_tab 1.0.31
gmake: *** [Makefile:212: _build/default/lib/.got] Error 1
===> Compilation failed unexpectedly.
Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to
the maintainer.
*** Error code 1

-- 
You are receiving this mail because:
You are the assignee for the bug.