Re: net/ejabberd remove or update?
On Sun, Mar 15, 2020 at 10:03:04PM +0100, Solene Rapenne wrote: > On Fri, Feb 14, 2020 at 01:45:53PM +0100, Jasper Lievisse Adriaanse wrote: > > > > > > > On 16 Oct 2019, at 16:58, Stuart Henderson wrote: > > > > > > On 2019/10/16 13:53, Solene Rapenne wrote: > > >> anyone willing to work on it? > > >> I see no reason to keep it otherwise. > > >> > > > > > > When you asked, there were some people using it, so maybe? > > > > How about now? I think we’d be doing people a favour by preventing them > > from using an xmpp server that’s almost 7 years old. > > If someone really wants to keep using it, it can be revived from the attic > > and updated to the latest version. > > > > Also, currently it’s the last port still using Erlang 16 — I’d like to > > remove both. > > time to remove it before 6.7 > > ok someone? go ahead :(
Re: net/ejabberd remove or update?
> On 15 Mar 2020, at 22:03, Solene Rapenne wrote: > > On Fri, Feb 14, 2020 at 01:45:53PM +0100, Jasper Lievisse Adriaanse wrote: >> >> >>> On 16 Oct 2019, at 16:58, Stuart Henderson wrote: >>> >>> On 2019/10/16 13:53, Solene Rapenne wrote: anyone willing to work on it? I see no reason to keep it otherwise. >>> >>> When you asked, there were some people using it, so maybe? >> >> How about now? I think we’d be doing people a favour by preventing them from >> using an xmpp server that’s almost 7 years old. >> If someone really wants to keep using it, it can be revived from the attic >> and updated to the latest version. >> >> Also, currently it’s the last port still using Erlang 16 — I’d like to >> remove both. > > time to remove it before 6.7 > > ok someone? Ok with me.
Re: net/ejabberd remove or update?
On Sun, Mar 15 2020, Solene Rapenne wrote: > On Fri, Feb 14, 2020 at 01:45:53PM +0100, Jasper Lievisse Adriaanse wrote: >> >> >> > On 16 Oct 2019, at 16:58, Stuart Henderson wrote: >> > >> > On 2019/10/16 13:53, Solene Rapenne wrote: >> >> anyone willing to work on it? >> >> I see no reason to keep it otherwise. >> >> >> > >> > When you asked, there were some people using it, so maybe? >> >> How about now? I think we’d be doing people a favour by preventing them from >> using an xmpp server that’s almost 7 years old. >> If someone really wants to keep using it, it can be revived from the attic >> and updated to the latest version. >> >> Also, currently it’s the last port still using Erlang 16 — I’d like to >> remove both. > > time to remove it before 6.7 > > ok someone? ok jca@ -- jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
Re: net/ejabberd remove or update?
On Fri, Feb 14, 2020 at 01:45:53PM +0100, Jasper Lievisse Adriaanse wrote: > > > > On 16 Oct 2019, at 16:58, Stuart Henderson wrote: > > > > On 2019/10/16 13:53, Solene Rapenne wrote: > >> anyone willing to work on it? > >> I see no reason to keep it otherwise. > >> > > > > When you asked, there were some people using it, so maybe? > > How about now? I think we’d be doing people a favour by preventing them from > using an xmpp server that’s almost 7 years old. > If someone really wants to keep using it, it can be revived from the attic > and updated to the latest version. > > Also, currently it’s the last port still using Erlang 16 — I’d like to remove > both. time to remove it before 6.7 ok someone?
Re: net/ejabberd remove or update?
On Sat, 15 Feb 2020 at 03:12:50 +0200, Paul Irofti wrote: > On Fri, Feb 14, 2020 at 04:02:40PM +0100, Paco Esteban wrote: > > On Fri, 14 Feb 2020, Solene Rapenne wrote: > > > > > On Fri, Feb 14, 2020 at 01:44:08PM +, Lucas wrote: > > > > Solene Rapenne wrote: > > > > > Do we have a xmpp server in ports which is up to date? > > > > > > > > There is net/profanity, made in Lua, which is almost up-to-date and I > > > > was planning to update it this weekend. Current version works without > > > > issues. > > > > > > > > -Lucas > > > > > > in net/profanity I read COMMENT= console based XMPP client > > > > > > I don't think it is a XMPP server, if it is, we need to fix the COMMENT > > > > As Lucas said: > > > > prosody-0.11.2p1communications server for Jabber/XMPP written in Lua > > > > We're only a couple of minors behind. I've been using it for about > > a year now (not much traffic to be honest), and works great. > > Is there a way to migrate from one server to another? From ejabberd to > prosody? > Prosody has a number of migrators: https://hg.prosody.im/trunk/file/tip/tools/ -- PGP: 0x1F81112D62A9ADCE / 3586 3350 BFEA C101 DB1A 4AF0 1F81 112D 62A9 ADCE
Re: net/ejabberd remove or update?
On Fri, Feb 14, 2020 at 04:02:40PM +0100, Paco Esteban wrote: > On Fri, 14 Feb 2020, Solene Rapenne wrote: > > > On Fri, Feb 14, 2020 at 01:44:08PM +, Lucas wrote: > > > Solene Rapenne wrote: > > > > Do we have a xmpp server in ports which is up to date? > > > > > > There is net/profanity, made in Lua, which is almost up-to-date and I > > > was planning to update it this weekend. Current version works without > > > issues. > > > > > > -Lucas > > > > in net/profanity I read COMMENT= console based XMPP client > > > > I don't think it is a XMPP server, if it is, we need to fix the COMMENT > > As Lucas said: > > prosody-0.11.2p1communications server for Jabber/XMPP written in Lua > > We're only a couple of minors behind. I've been using it for about > a year now (not much traffic to be honest), and works great. Is there a way to migrate from one server to another? From ejabberd to prosody?
Re: net/ejabberd remove or update?
On Fri, 14 Feb 2020, Solene Rapenne wrote: > On Fri, Feb 14, 2020 at 01:44:08PM +, Lucas wrote: > > Solene Rapenne wrote: > > > Do we have a xmpp server in ports which is up to date? > > > > There is net/profanity, made in Lua, which is almost up-to-date and I > > was planning to update it this weekend. Current version works without > > issues. > > > > -Lucas > > in net/profanity I read COMMENT= console based XMPP client > > I don't think it is a XMPP server, if it is, we need to fix the COMMENT As Lucas said: prosody-0.11.2p1communications server for Jabber/XMPP written in Lua We're only a couple of minors behind. I've been using it for about a year now (not much traffic to be honest), and works great. Cheers, -- Paco Esteban. 5818130B8A6DBC03
Re: net/ejabberd remove or update?
Lucas wrote: > There is net/profanity, made in Lua, which is almost up-to-date and I > was planning to update it this weekend. Current version works without > issues. s/profanity/prosody/
Re: net/ejabberd remove or update?
On Fri, Feb 14, 2020 at 01:44:08PM GMT, Lucas wrote: > Solene Rapenne wrote: > > Do we have a xmpp server in ports which is up to date? > > There is net/profanity, made in Lua, which is almost up-to-date and I > was planning to update it this weekend. Current version works without > issues. > > -Lucas > Hi Lucas, Profanity is an XMPP *client*, not a *server*. It isn't written in Lua either. Have you confused it with another port? Regards, Raf
Re: net/ejabberd remove or update?
On Fri, Feb 14, 2020 at 01:44:08PM +, Lucas wrote: > Solene Rapenne wrote: > > Do we have a xmpp server in ports which is up to date? > > There is net/profanity, made in Lua, which is almost up-to-date and I > was planning to update it this weekend. Current version works without > issues. > > -Lucas in net/profanity I read COMMENT= console based XMPP client I don't think it is a XMPP server, if it is, we need to fix the COMMENT
Re: net/ejabberd remove or update?
Solene Rapenne wrote: > Do we have a xmpp server in ports which is up to date? There is net/profanity, made in Lua, which is almost up-to-date and I was planning to update it this weekend. Current version works without issues. -Lucas
Re: net/ejabberd remove or update?
On Fri, Feb 14, 2020 at 01:45:53PM +0100, Jasper Lievisse Adriaanse wrote: > > > > On 16 Oct 2019, at 16:58, Stuart Henderson wrote: > > > > On 2019/10/16 13:53, Solene Rapenne wrote: > >> anyone willing to work on it? > >> I see no reason to keep it otherwise. > >> > > > > When you asked, there were some people using it, so maybe? > > How about now? I think we’d be doing people a favour by preventing them from > using an xmpp server that’s almost 7 years old. > If someone really wants to keep using it, it can be revived from the attic > and updated to the latest version. > > Also, currently it’s the last port still using Erlang 16 — I’d like to remove > both. I really think we should remove this. Do we have a xmpp server in ports which is up to date?
Re: net/ejabberd remove or update?
On 2019/10/16 13:53, Solene Rapenne wrote: > anyone willing to work on it? > I see no reason to keep it otherwise. > When you asked, there were some people using it, so maybe?
Re: net/ejabberd remove or update?
On Thu, Oct 03, 2019 at 12:11:56PM +0200, Solene Rapenne wrote:
> On Wed, Oct 02, 2019 at 12:24:45PM +0200, Solene Rapenne wrote:
> > Hi,
> >
> > our net/ejabberd port use v2.1.12 released in 02/2013
> > https://github.com/processone/ejabberd/releases/tag/v2.1.12
> >
> > I think we should remove it because it's an outdated network daemon
> > which, per github, received 4780 commits since our version.
> > I can not find any CVE that apply for version >= 2.1.12 though.
> >
> > I'm not using it and there is no MAINTAINER, so I have no idea if
> > running this very old version is safe or not.
> >
> > so I propose to remove it from ports, except/until someone wants
> > to take care of updating it?
> >
>
> I starting working on it but it's become boring and I don't want to go
> further. With this diff, ejabberd starts building with erlang21 and
> autoconf.
>
> Remove all patches in patches/ folder before trying to run make
>
>
> Index: Makefile
> ===
> RCS file: /data/cvs/ports/net/ejabberd/Makefile,v
> retrieving revision 1.48
> diff -u -p -r1.48 Makefile
> --- Makefile 12 Jul 2019 20:48:25 - 1.48
> +++ Makefile 3 Oct 2019 10:09:00 -
> @@ -2,9 +2,9 @@
>
> COMMENT= jabber server written in Erlang
>
> -V= 2.1.12
> -DISTNAME=ejabberd-$V
> -REVISION=12
> +GH_ACCOUNT= processone
> +GH_PROJECT= ejabberd
> +GH_TAGNAME= 19.09
>
> CATEGORIES= net
>
> @@ -15,9 +15,7 @@ PERMIT_PACKAGE= Yes
>
> WANTLIB= crypto expat iconv ssl z
>
> -MASTER_SITES=
> http://www.process-one.net/downloads/ejabberd/$V/
> -EXTRACT_SUFX=.tgz
> -
> +MODERL_VERSION= 21
> MODULES= lang/erlang
>
> LIB_DEPENDS= converters/libiconv
> @@ -31,7 +29,11 @@ FAKE_FLAGS+= EJABBERDDIR=${WRKINST}/${P
> ETCDIR=${WRKINST}/${PREFIX}/share/examples/ejabberd \
> SPOOLDIR=${WRKINST}/${EJDBDIR}
>
> -CONFIGURE_STYLE= gnu
> +AUTOCONF_VERSION= 2.69
> +AUTOMAKE_VERSION= 1.15
> +AUTORECONF= ./autogen.sh
> +
> +CONFIGURE_STYLE= autoreconf
> CONFIGURE_ARGS+= --disable-pam \
> --enable-mod_pubsub \
> --enable-mod_irc \
> @@ -52,8 +54,6 @@ JABBERDUSER=_ejabberd
> JABBERDGROUP= _ejabberd
> EJDBDIR= /var/db/ejabberd
> EJLOGDIR=/var/log/ejabberd
> -
> -WRKSRC= ${WRKDIST}/src
>
> NO_TEST= Yes
>
> Index: distinfo
> ===
> RCS file: /data/cvs/ports/net/ejabberd/distinfo,v
> retrieving revision 1.13
> diff -u -p -r1.13 distinfo
> --- distinfo 5 May 2013 16:17:19 - 1.13
> +++ distinfo 3 Oct 2019 09:48:43 -
> @@ -1,2 +1,2 @@
> -SHA256 (ejabberd-2.1.12.tgz) = OPCCU0Z3PADIWmazNYbHXy0ZHR6w7Yrgn6FzaNbd/Rk=
> -SIZE (ejabberd-2.1.12.tgz) = 1999224
> +SHA256 (ejabberd-19.09.tar.gz) = 5GBV2Ix/wZQ7P+at5xn060gpwtviAIC8PZy9kJqfTes=
> +SIZE (ejabberd-19.09.tar.gz) = 1845562
>
>
> Then, it will fail downloading a git repository, maybe there are more, I
> don't know. I don't want to work on it.
>
>
> t480 /usr/ports/net/ejabberd $ make
> ===> ejabberd-19.09 depends on: erlang->=21v0,<22v0 -> erlang-21.2p2v0
> ===> ejabberd-19.09 depends on: metaauto-* -> metaauto-1.0p3
> ===> ejabberd-19.09 depends on: autoconf-2.69 -> autoconf-2.69p2
> ===> ejabberd-19.09 depends on: automake->=1.15,<1.16 -> automake-1.15.1
> ===> ejabberd-19.09 depends on: libtool-* -> libtool-2.4.2p0
> ===> ejabberd-19.09 depends on: gmake-* -> gmake-4.2.1p4
> ===> ejabberd-19.09 depends on: libiconv-* -> libiconv-1.16p0
> ===> Verifying specs: crypto expat iconv ssl z
> ===> found crypto.45.5 expat.12.0 iconv.7.0 ssl.47.6 z.5.0
> ===> Checking files for ejabberd-19.09
> `/usr/ports/distfiles/ejabberd-19.09.tar.gz' is up to date.
> >> (SHA256) ejabberd-19.09.tar.gz: OK
> ===> Extracting for ejabberd-19.09
> ===> Patching for ejabberd-19.09
> ===> Compiler link: clang -> /usr/bin/clang
> ===> Compiler link: clang++ -> /usr/bin/clang++
> ===> Compiler link: cc -> /usr/bin/cc
> ===> Compiler link: c++ -> /usr/bin/c++
> ===> Generating configure for ejabberd-19.09
> Running autoreconf-2.69 in /usr/ports/pobj/ejabberd-19.09/ejabberd-19.09
> ===> Configuring for ejabberd-19.09
> Using /usr/ports/pobj/ejabberd-19.09/config.site (generated)
> configure: WARNING: unrecognized options: --enable-mod_pubsub,
> --enable-mod_irc, --enable-mod_muc, --enable-eldap, --enable-web,
> --enable-tls, --enable-ejabberd_zlib, --disable-silent-rules,
> --disable-gtk-doc
> configure: loading site script /usr/ports/pobj/ejabberd-19.09/config.site
> checking whether gmake sets $(MAKE)... yes
> checking for a BSD-compatible install...
> /usr/ports/pobj/ejabberd-19.09/bin/install -c
> checking fo
Re: net/ejabberd remove or update?
On Wed, Oct 02, 2019 at 12:24:45PM +0200, Solene Rapenne wrote:
> Hi,
>
> our net/ejabberd port use v2.1.12 released in 02/2013
> https://github.com/processone/ejabberd/releases/tag/v2.1.12
>
> I think we should remove it because it's an outdated network daemon
> which, per github, received 4780 commits since our version.
> I can not find any CVE that apply for version >= 2.1.12 though.
>
> I'm not using it and there is no MAINTAINER, so I have no idea if
> running this very old version is safe or not.
>
> so I propose to remove it from ports, except/until someone wants
> to take care of updating it?
>
I starting working on it but it's become boring and I don't want to go
further. With this diff, ejabberd starts building with erlang21 and
autoconf.
Remove all patches in patches/ folder before trying to run make
Index: Makefile
===
RCS file: /data/cvs/ports/net/ejabberd/Makefile,v
retrieving revision 1.48
diff -u -p -r1.48 Makefile
--- Makefile12 Jul 2019 20:48:25 - 1.48
+++ Makefile3 Oct 2019 10:09:00 -
@@ -2,9 +2,9 @@
COMMENT= jabber server written in Erlang
-V= 2.1.12
-DISTNAME= ejabberd-$V
-REVISION= 12
+GH_ACCOUNT=processone
+GH_PROJECT=ejabberd
+GH_TAGNAME=19.09
CATEGORIES=net
@@ -15,9 +15,7 @@ PERMIT_PACKAGE= Yes
WANTLIB= crypto expat iconv ssl z
-MASTER_SITES= http://www.process-one.net/downloads/ejabberd/$V/
-EXTRACT_SUFX= .tgz
-
+MODERL_VERSION=21
MODULES= lang/erlang
LIB_DEPENDS= converters/libiconv
@@ -31,7 +29,11 @@ FAKE_FLAGS+= EJABBERDDIR=${WRKINST}/${P
ETCDIR=${WRKINST}/${PREFIX}/share/examples/ejabberd \
SPOOLDIR=${WRKINST}/${EJDBDIR}
-CONFIGURE_STYLE= gnu
+AUTOCONF_VERSION= 2.69
+AUTOMAKE_VERSION= 1.15
+AUTORECONF=./autogen.sh
+
+CONFIGURE_STYLE= autoreconf
CONFIGURE_ARGS+= --disable-pam \
--enable-mod_pubsub \
--enable-mod_irc \
@@ -52,8 +54,6 @@ JABBERDUSER=_ejabberd
JABBERDGROUP= _ejabberd
EJDBDIR= /var/db/ejabberd
EJLOGDIR= /var/log/ejabberd
-
-WRKSRC=${WRKDIST}/src
NO_TEST= Yes
Index: distinfo
===
RCS file: /data/cvs/ports/net/ejabberd/distinfo,v
retrieving revision 1.13
diff -u -p -r1.13 distinfo
--- distinfo5 May 2013 16:17:19 - 1.13
+++ distinfo3 Oct 2019 09:48:43 -
@@ -1,2 +1,2 @@
-SHA256 (ejabberd-2.1.12.tgz) = OPCCU0Z3PADIWmazNYbHXy0ZHR6w7Yrgn6FzaNbd/Rk=
-SIZE (ejabberd-2.1.12.tgz) = 1999224
+SHA256 (ejabberd-19.09.tar.gz) = 5GBV2Ix/wZQ7P+at5xn060gpwtviAIC8PZy9kJqfTes=
+SIZE (ejabberd-19.09.tar.gz) = 1845562
Then, it will fail downloading a git repository, maybe there are more, I
don't know. I don't want to work on it.
t480 /usr/ports/net/ejabberd $ make
===> ejabberd-19.09 depends on: erlang->=21v0,<22v0 -> erlang-21.2p2v0
===> ejabberd-19.09 depends on: metaauto-* -> metaauto-1.0p3
===> ejabberd-19.09 depends on: autoconf-2.69 -> autoconf-2.69p2
===> ejabberd-19.09 depends on: automake->=1.15,<1.16 -> automake-1.15.1
===> ejabberd-19.09 depends on: libtool-* -> libtool-2.4.2p0
===> ejabberd-19.09 depends on: gmake-* -> gmake-4.2.1p4
===> ejabberd-19.09 depends on: libiconv-* -> libiconv-1.16p0
===> Verifying specs: crypto expat iconv ssl z
===> found crypto.45.5 expat.12.0 iconv.7.0 ssl.47.6 z.5.0
===> Checking files for ejabberd-19.09
`/usr/ports/distfiles/ejabberd-19.09.tar.gz' is up to date.
>> (SHA256) ejabberd-19.09.tar.gz: OK
===> Extracting for ejabberd-19.09
===> Patching for ejabberd-19.09
===> Compiler link: clang -> /usr/bin/clang
===> Compiler link: clang++ -> /usr/bin/clang++
===> Compiler link: cc -> /usr/bin/cc
===> Compiler link: c++ -> /usr/bin/c++
===> Generating configure for ejabberd-19.09
Running autoreconf-2.69 in /usr/ports/pobj/ejabberd-19.09/ejabberd-19.09
===> Configuring for ejabberd-19.09
Using /usr/ports/pobj/ejabberd-19.09/config.site (generated)
configure: WARNING: unrecognized options: --enable-mod_pubsub,
--enable-mod_irc, --enable-mod_muc, --enable-eldap, --enable-web, --enable-tls,
--enable-ejabberd_zlib, --disable-silent-rules, --disable-gtk-doc
configure: loading site script /usr/ports/pobj/ejabberd-19.09/config.site
checking whether gmake sets $(MAKE)... yes
checking for a BSD-compatible install...
/usr/ports/pobj/ejabberd-19.09/bin/install -c
checking for a sed that does not truncate output... (cached) /usr/bin/sed
checking for erl... /usr/local/bin/erl21
checking for erlc... /usr/local/bin/erlc21
checking for epmd... no
checking for erl... /usr/local/bin/erl21
checking for erlc... /usr/local/bin/erlc21
checking Erlang/OTP version
net/ejabberd remove or update?
Hi, our net/ejabberd port use v2.1.12 released in 02/2013 https://github.com/processone/ejabberd/releases/tag/v2.1.12 I think we should remove it because it's an outdated network daemon which, per github, received 4780 commits since our version. I can not find any CVE that apply for version >= 2.1.12 though. I'm not using it and there is no MAINTAINER, so I have no idea if running this very old version is safe or not. so I propose to remove it from ports, except/until someone wants to take care of updating it?
