[Bug 1309523] New: Bump up Erlang version

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1309523

            Bug ID: 1309523
           Summary: Bump up Erlang version
           Product: Fedora EPEL
           Version: epel7
         Component: erlang
          Assignee: rjones(a)redhat.com
          Reporter: gdubreui(a)redhat.com
        QA Contact: extras-qa(a)fedoraproject.org
                CC: erlang(a)lists.fedoraproject.org, jeckersb(a)redhat.com,
                    rjones(a)redhat.com, s(a)shk.io



Erlang RPM for EPEL7 is version 16
Meawhile Erlang 18 is available.
Fedora 23 is using version 17 while Fedora 24 (rawhide has version 18).  

Other projects like Elixir depends on more recent version of Erlang.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 1309523] Bump up Erlang version

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1309523

Peter Lemenkov <plemenko(a)redhat.com&gt; changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |plemenko(a)redhat.com



--- Comment #1 from Peter Lemenkov <plemenko(a)redhat.com&gt; ---
(In reply to Gilles Dubreuil from comment #0)
>  Erlang RPM for EPEL7 is version 16
>  Meawhile Erlang 18 is available.
>  Fedora 23 is using version 17 while Fedora 24 (rawhide has version 18).  
>  
>  Other projects like Elixir depends on more recent version of Erlang. 
That's not simple. Erlang 18 has ABI-incompatibilities with Erlang R16
(NIF/Drivers API, obsolete functions like erlang:now(), different types like
dict vs. dict:dicts, etc). I strongly support that but currently it would
violate EPEL packaging rules too much.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 1309523] Bump up Erlang version

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1309523

Gilles Dubreuil <gdubreui(a)redhat.com&gt; changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Blocks|                            |1309525



--- Comment #2 from Gilles Dubreuil <gdubreui(a)redhat.com&gt; ---
I agree this challenges Fedora/EPEL package updates policy.

One solution mentioned in related BZ#1309525 would be to have Red Hat Software
Collections (SCL) to take care of it. Since Erlang is not part of SCL yet, it'd
have to be added/accepted first.

Some thoughts here:
Programming languages have regular and important updates. EPEL, because of RHEL
long life cycle cannot take advantage of those new releases.

Fedora has only the latest RPM available, which might make sense when targeting
only cutting edge environments. But if EPEL could instead follow RHEL channels
approach and keep all RPM released versions then that would not be an issue
because those who need a previous version (Erlang 16, or Erlang 17) could still
get it and the latest RPM version would be the latest but stable version
(Erlang 18)


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1309525
[Bug 1309525] Bump up Elixir version
-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 1309523] Bump up Erlang version

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1309523

Martin Langhoff <martin(a)laptop.org&gt; changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |martin(a)laptop.org



--- Comment #3 from Martin Langhoff <martin(a)laptop.org&gt; ---
Erlang 17 and Erlang 18 as currently packaged would conflict. We would need
retool Erlang packaging to use 'alternatives', and alternatives isn't
actually
that good (i.e.: systems with two versions of Java have a hard time using both,
if you need them for example to support different programs/daemons running at
the same time).

These issues are exactly why SCL exists... IMO SCL is a saner path, but again
quite a bit of work.

I am happy to lend a hand with an SCL Erlang 18 or a COPR repo. As I mentioned
in  BZ#1309525 I have a very crude repo with Erlang 18 and Elixir 1.2.2 for
EL7.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 1309523] Bump up Erlang version

https://bugzilla.redhat.com/show_bug.cgi?id=1309523

Xavier Bachelot <xavier(a)bachelot.org&gt; changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |xavier(a)bachelot.org



--- Comment #4 from Xavier Bachelot <xavier(a)bachelot.org&gt; ---
(In reply to Peter Lemenkov from comment #1)
>  (In reply to Gilles Dubreuil from comment #0)
>  > Erlang RPM for EPEL7 is version 16
>  > Meawhile Erlang 18 is available.
>  > Fedora 23 is using version 17 while Fedora 24 (rawhide has version 18).  
>  > 
>  > Other projects like Elixir depends on more recent version of Erlang.
>  
>  That's not simple. Erlang 18 has ABI-incompatibilities with Erlang R16
>  (NIF/Drivers API, obsolete functions like erlang:now(), different types like
>  dict vs. dict:dicts, etc). I strongly support that but currently it would
>  violate EPEL packaging rules too much. 
What about erlang 17 ? Does it have ABI incompatibilities too ?

Fwiw, I'm currently struggling with ejabberd for EL7. I have a working cluster,
but I'm stuck with ejabberd 15.07 which is the latest version supporting erlang
16. erlang 17 would allow to get ejabberd 17.04 and probably future versions to
run. I'd be willing to maintain ejabberd in EPEL 7, but I'd rather leave the
erlang stack to more skilled buddies.

-- 
You are receiving this mail because:
You are on the CC list for the bug.