Opened 7 years ago

Closed 7 years ago

#21622 closed defect (fixed)

Ejabberd 2.0.5 is incompatible with Erlang/OTP R13.

Reported by: jonasnockert@… Owned by: simon@…
Priority: Normal Milestone:
Component: ports Version: 1.8.0
Keywords: Cc: smbmacportstrac@…, ryandesign (Ryan Schmidt)
Port: ejabberd

Description

The current port for Erlang/OTP is R13B01 and the current port for Ejabberd is 2.0.5. However, Ejabberd 2.0.5 only works with Erlang/OTP R12.

The upcoming Ejabberd 2.1 (RC) will support R13.

Attachments (3)

Portfile (2.6 KB) - added by smbmacportstrac@… 7 years ago.
ejabberd 2.0.5_1 Portfile
portfile.diff (679 bytes) - added by smbmacportstrac@… 7 years ago.
Differences from current 2.0.5_0 Portfile
dynamic_compile_loglevel.patch (28.9 KB) - added by smbmacportstrac@… 7 years ago.
Thanks to Geoff Cant, #EJAB-919

Download all attachments as: .zip

Change History (7)

comment:1 Changed 7 years ago by jmroot (Joshua Root)

  • Keywords ejabberd erlang removed
  • Owner changed from macports-tickets@… to simon@…
  • Port ejabberd added

comment:2 Changed 7 years ago by smbmacportstrac@…

Hi. I'd like to contribute a fix for this. I can't revert to erlang R12 and I can't wait for ejabberd 2.1. So, I took the patch provided by Geoff Cant and modified it to work with MacPorts. https://support.process-one.net/browse/EJAB-919 https://support.process-one.net/secure/attachment/14195/dynamic_compile_loglevel.patch It's very important that the $Id$ not be rewritten when checked in to subversion. Attachments coming next...

--Steve

Changed 7 years ago by smbmacportstrac@…

ejabberd 2.0.5_1 Portfile

Changed 7 years ago by smbmacportstrac@…

Differences from current 2.0.5_0 Portfile

Changed 7 years ago by smbmacportstrac@…

Thanks to Geoff Cant, #EJAB-919

comment:3 Changed 7 years ago by smbmacportstrac@…

  • Cc smbmacportstrac@… added

Cc Me!

comment:4 Changed 7 years ago by ryandesign (Ryan Schmidt)

  • Cc ryandesign@… added
  • Resolution set to fixed
  • Status changed from new to closed

ejabberd was updated to 2.1.1 in r63002 and 2.1.3 in r65388 so I assume this is now resolved.

Note: See TracTickets for help on using tickets.