jabberd-2.1.5 is available. Please update the ebuild. Reproducible: Always
Created attachment 120070 [details] Ebuild for jabberd-2.1.6 jabberd2 has changed a lot in the 2.1 series: - config file changes will be necessary - dropped the ssl useflag, since OpenSSL is now required (docs state otherwise, but are wrong here); updated dependency list - version 2.1.6 jabberd2 supports both cyrus-sasl or gsasl (one of those two is required). Since there are no recent gsasl packages in the portage tree, gsasl is not supported by this ebuild yet.
Created attachment 120071 [details] Slightly modified init-script for jabberd-2.1.6 Dropping the tmpPidHack from the old init script. (Don't think it is necessary.)
jabberd and jabberd2 are different programs. Shouldn't jabberd2 get at least it's own slot or become a new application net-im/jabberd2 ?
The updated ebuild works for me on amd64. But the mysql database schema doesn't seem to include the "status" table that is listed in the upgrade docs. So I had to create it manually.
Version 2.1.6 added to portage. ppc and sparc: please test it and restore ~arch keyword.
Blessed with ~sparc again.
Created attachment 122165 [details] Updated ebuild Just some minor fixes: 1. db-setup-status.mysql is being installed now. This should address the issue above. 2. /etc/pam.d/jabberd is installed. Added warnings concerning the use of pam auth. 3. Depending on virtual/pam instead of sys-libs/pam
Created attachment 122166 [details] Updated init script. Minor changes for better posix compliance.
Created attachment 122168 [details] pam.d file
~ppc'd
(In reply to comment #3) > jabberd and jabberd2 are different programs. Shouldn't jabberd2 get at least > it's own slot or become a new application net-im/jabberd2 ? You're right, see http://jabberd.jabberstudio.org/ "Despite the numbering scheme, the projects are entirely distinct codebases with different development teams, both projects are actively developed, [...]" I think that should really become two separate ebuilds: * jabberd14 * jabberd2 The jabberd-ebuild could depend on one of them (USE-flags to choose?).
jabberd2-2.1.7 and jabberd2-2.1.8 are relased. I think that too, that jabberd14 and jabberd2 should be two different ebuilds.
Created attachment 125548 [details] Ebuild jabberd-2.1.8 The .pamd and .init files stay valid.
2.1.12 is available
any plan yet on when the first jabberd2 release will be declared stable (on x86)?
Created attachment 131511 [details] Revised ebuild for 2.1.15 Version bump to 2.1.15. SASL configuration options at build time have changed. Pool-debug is currently borken.
Created attachment 131513 [details] Revised init script 2.1.15 Fixes issues with running multiple instances of a service.
*** Bug 191925 has been marked as a duplicate of this bug. ***
Created attachment 131578 [details] jabberd2-2.1.15.ebuild By popular demand and suggestion from Marko I'm movin jabberd-2* to net-im/jabberd2. net-im/jabberd and net-im/jabberd2 will block each other. pam.d and init scripts should be renamed from jabberd-... to jabberd2-... Please test this ebuild. Marko: please check also the ebuild to see if I didn't break it ;) and ACK the change.
net-im: we need to synchronize the move to jabberd2, following ebuilds will need to be changed: jit/jit-1.1.6-r3.ebuild:RDEPEND=">=net-im/jabberd-1.4.3-r3" jud/jud-0.5.ebuild:DEPEND=">=net-im/jabberd-1.4.3" msn-transport/msn-transport-20040531-r1.ebuild:DEPEND=">=net-im/jabberd-1.4 msn-transport/msn-transport-20040531.ebuild:DEPEND=">=net-im/jabberd-1.4 ^^^ those ebuilds should have "|| ( net-im/jabberd net-im/jabberd2 )" Following ebuilds have to be changed too: mu-conference/mu-conference-0.6.0-r1.ebuild:DEPEND="=net-im/jabberd-1.4* mu-conference/mu-conference-0.6.0-r2.ebuild:DEPEND="=net-im/jabberd-1.4* yahoo-transport/yahoo-transport-2.3.0-r3.ebuild:DEPEND="=net-im/jabberd-1.4*" yahoo-transport/yahoo-transport-2.3.1-r1.ebuild:DEPEND="=net-im/jabberd-1.4* yahoo-transport/yahoo-transport-2.3.2.ebuild:DEPEND="=net-im/jabberd-1.4* ^^^ those ebuilds should have "net-im/jabberd" instead of =net-im/jabberd-1.4*
Okay, I've tested the ebuild with a number of configurations and it looks good to me. It can go into portage as jabberd2.
Version 2.1.16 relased
jabberd2-2.1.15 in portage as net-im/jabberd sparc, ppc: I've dropped your keywords (I can't test it on ppc or sparc) - please test and restore them or give me a green light to do so.
net-im/jabberd2 is masked until it gets ~sparc and ~ppc. Masked also until I can make a proper blocks in net-im/jabberd.
Any particular reason why you added .15, while upstream already has .17?
(In reply to comment #25) > Any particular reason why you added .15, while upstream already has .17? Yes: 2.1.15 was prepared for the split and as such it was committed. When net-im/jabberd2 goes out of package.mask and ebuilds will have it's deps fixed (see bug #195091) it will be version bumped.
~sparc'ed now
ppc: please keyword (~ppc) net-im/jabberd2-2.1.19
Tested by me and nixnut.
