Summary: | net-im/ejabberd-24.02 - .beam files not installed | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Daniel Kenzelmann <gentoo> |
Component: | Current packages | Assignee: | ejabberd Project <ejabberd> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | bertrand, flow, gentoo, phils |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Daniel Kenzelmann
2024-03-12 07:29:13 UTC
net-im/ejabberd-24.02::gentoo USE="captcha ldap postgres zlib -debug -full-xml -mssql -mysql -odbc -pam -redis -roster-gw (-selinux) -sip -sqlite -stun" it seems that not only are the files in ebin not installed but everything is installed under /usr/lib64/ejabberd/ instead of /usr/lib64/ejabberd-24.02/ moving the files to the right directory and manually copying the beam files (ebin folder) from the work directory seems to make it work,.. (In reply to Daniel Kenzelmann from comment #2) > it seems that not only are the files in ebin not installed but everything is > installed under /usr/lib64/ejabberd/ instead of /usr/lib64/ejabberd-24.02/ > > moving the files to the right directory and manually copying the beam files > (ebin folder) from the work directory seems to make it work,.. I didn't have any opportunity to investigate deeply but did also encounter ejabberd failing to start because ejabberd_ctl could not be found. If all of the beam files were incorrectly installed ot not installed, that would likely create the observed symptoms, but at the time, lacking the time for a proper investigation, I just rolled back to 23.10. Additional comment here: I additionally faced an issue where as it seems that conversations did somehow "half-connect" to 24.02? and thus had issues connecting later on to older versions of ejabberd (SASL downgrade protection etc), that forced me to go to 24.02. Thus I would suggest that this should be fixed asap otherwise people will have clients that are no longer able to connect even if you downgrade again.. The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f38ed16bd83f84025945271f3a6d660ab0438bfa commit f38ed16bd83f84025945271f3a6d660ab0438bfa Author: Florian Schmaus <flow@gentoo.org> AuthorDate: 2024-03-12 19:26:57 +0000 Commit: Florian Schmaus <flow@gentoo.org> CommitDate: 2024-03-12 19:31:17 +0000 net-im/ejabberd: pass --with-rebar=rebar to use rebar 2 ejabberd 24.02 started to use rebar 3 as default build system. This broke the ebuild, since rebar.eclass sill uses rebar 2. Passing --with-rebar=rebar switches this back to rebar 2. Thanks to Holger Weiß for pointing this out. Closes: https://bugs.gentoo.org/926799 Signed-off-by: Florian Schmaus <flow@gentoo.org> net-im/ejabberd/{ejabberd-24.02.ebuild => ejabberd-24.02-r1.ebuild} | 1 + 1 file changed, 1 insertion(+) |