Ticket #5315 (closed task: fixed)

Opened 7 years ago

Last modified 7 years ago

test collaboration with newer Ejabberd

Reported by: daf Owned by: robot101
Priority: normal Milestone: Update.1
Component: telepathy-other Version:
Keywords: Cc: jg, kimquirk, wad
Action Needed: Verified: no
Deployments affected: Blocked By:


Ejabberd 1.3, which we're using on jabber.laptop.org isn't very reliably currently (see #5313). We should try upgrading to the latest development version (2.0 series) and see if that works any better. This will also let us discover any future compatibility problems early.

Change History

Changed 7 years ago by robot101

  • status changed from new to assigned

Upstream seem to think it's worth spending a day or two debugging the configuration we've got (see #5313), in case it's a trivial fix, rather than exposing ourselves to the uncertainty of the current development version, so I'll work on that with them first.

Changed 7 years ago by robot101

  • cc jg, kimquirk added

jabber.laptop.org is now running SVN revision 1027 of what I understand soon to be released as ejabberd 2.0 beta, in the hope it helps with #5313. For the purposes of school server, it should be noted I've made Fedora 7 RPMs of this on jabber.laptop.org with the one remaining patch we need.

Changed 7 years ago by robot101

  • cc wad added

CCing wad so he knows I've made RPMs (jabber.l.o has RPMs on it for the 1.1.x+patches version too), I will put them somewhere more useful tomorrow.

Changed 7 years ago by daf

We've been running the Ejabberd 2.0 candidate for a few days now. Is it fair to say that it doesn't seem to work any worse than 1.3? Of course, #5313 still applies.

The purpose of filing this ticket was ascertaining whether Ejabberd 2.0 is suitable for our purposes. Do we need to do more testing, or can we close this ticket?

Changed 7 years ago by robot101

  • status changed from assigned to closed
  • resolution set to fixed

I guess we should close this ticket, we tried, it didn't seem to make things noticably better or worse.

Note: See TracTickets for help on using tickets.