Re: ejabberd regression Q3->Q4

[Greg Troxel <gdt%lexort.com@localhost>]

You may wish to move to head; it's at 26.01.  If you want to build new
ejabberd in a 2025Q4 context, you should be able to cvs up -A in
erlang, all erlang-foo, and ejabberd.

is%netbsd.org@localhost writes:

> 1/1] installing ejabberd-25.07...

I'm puzzled.  The update history is
  2025-08-08: 25.07
  2026-02-08: 25.08, 25.10, 26.01
so Q3 and Q4 both have 25.07.

I have been running ejabberd, and had no problems when on Q3/Q4.  That's
not a claim that it is bug-free.

> ejabberd-25.07: /usr/pkg/etc/ejabberd/ejabberd.yml already exists
> ejabberd-25.07: /usr/pkg/etc/ejabberd/ejabberdctl.cfg already exists
> ejabberd-25.07: /usr/pkg/etc/ejabberd/inetrc already exists
> ejabberd-25.07: setting permissions on /usr/pkg/sbin/ejabberdctl (o=root, g=ejabberd, m=0750)

In general one has to check/merge configs to the new package version.  I
have no idea what's in your config files.

Also, ejabberdctl has been pesky for a long time, needing a patch to
remediate linuxy assumptions about su(1).  This has changed in head as an
upstream patch that I helped with has made it to 26.01.

To avoid the su issue, become the ejabberd user and start from that.

You didn't say what erlang version, but pkgsrc was at 27.01.  If your
pkgsrc tree isn't generally up to date, you're outside of how I
tested. It may be that some deps are admitted by the patterns but not
actually ok; I avoid this by having everything up to date.
>
> I might have more time for a better and formal bug report tomorrow.

Sure, feel free to send to just me or here.  I have no idea if there are
others using ejabberd.