[Messaging] RabbitMQ for EPEL 9

[Robby Callicotte]

Hello all,

I recently stumbled onto this bugzilla issue[1].  It has gone a couple of 
months without a response from the assignee.  I know that the stalled package 
request procedures can be started now, but I also see that RabbitMQ was built 
by the Messaging SIG in the past.  So... Where should this get routed?  Is the 
messaging SIG still active?  I see some info[2] saying that it is, but the 
lack of response leads me to think that it may not be.


Thanks!


[1]  https://bugzilla.redhat.com/show_bug.cgi?id=2105791
[2] https://wiki.centos.org/SpecialInterestGroup/Messaging

-- 
Robby Callicotte
He/Him/His
Timezone: America/Chicago
IRC: c4t3l | Twitter: @robbycl2v

[Richard Shaw]

On Sat, Sep 3, 2022 at 1:32 PM Robby Callicotte via epel-devel <
epel-devel(a)lists.fedoraproject.org&gt; wrote:

>  Hello all,
>
>  I recently stumbled onto this bugzilla issue[1].  It has gone a couple of
>  months without a response from the assignee.  I know that the stalled
>  package
>  request procedures can be started now, but I also see that RabbitMQ was
>  built
>  by the Messaging SIG in the past.  So... Where should this get routed?  Is
>  the
>  messaging SIG still active?  I see some info[2] saying that it is, but the
>  lack of response leads me to think that it may not be.
>  
Have you tried building the package yourself yet? When asking for someone
to support an EPEL branch it's not always straightforward. I tried building
the rawhide branch for EPEL 9 and ran into the following:

No matching package to install: 'elixir'
No matching package to install: 'erlang >= 23'

I haven't dug any further so this may be easy to fix but maybe not...

Thanks,
Richard

[Robby Callicotte]

On Saturday, September 3, 2022 1:39:41 PM CDT Richard Shaw wrote:
>  Have you tried building the package yourself yet? When asking for
> someone
>  to support an EPEL branch it's not always straightforward. I tried building
>  the rawhide branch for EPEL 9 and ran into the following:
>  
>  No matching package to install: 'elixir'
>  No matching package to install: 'erlang >= 23'
>  
>  I haven't dug any further so this may be easy to fix but maybe not... 
Yes I tried building the package and ran into the same issue you did.  I am 
tracking down the deps.  I was just confused as to where the request should 
go.  I am absolutely willing to help out whether that's in the Messaging SIG 
or as an EPEL build.

-- 
Robby Callicotte
He/Him/His
Timezone: America/Chicago
IRC: c4t3l | Twitter: @robbycl2v

[Davide Cavalca]

On Sat, 2022-09-03 at 13:39 -0500, Richard Shaw wrote:
>  Have you tried building the package yourself yet? When asking for
>  someone to support an EPEL branch it's not always straightforward. I
>  tried building the rawhide branch for EPEL 9 and ran into the
>  following:
>  
>  No matching package to install: 'elixir'
>  No matching package to install: 'erlang >= 23'
>  
I breifly looked into this a couple of months ago as someone asked me
about it at work. From what I recall, erlang is mostly doable, but
elixir is a problem because it pulls in a bunch of other stuff and
seems to have a bit of a bootstrapping problem. I'm sure someone
familiar with this ecosystem could get it sorted out, but that's not me
so I ended up leaving it alone.

Cheers
Davide

[Matthias Runge]

On 03/09/2022 20:32, Robby Callicotte via epel-devel wrote:
>  Hello all,
>  
>  I recently stumbled onto this bugzilla issue[1].  It has gone a couple of
>  months without a response from the assignee.  I know that the stalled package
>  request procedures can be started now, but I also see that RabbitMQ was built
>  by the Messaging SIG in the past.  So... Where should this get routed?  Is the
>  messaging SIG still active?  I see some info[2] saying that it is, but the
>  lack of response leads me to think that it may not be.
>  
>  
>  Thanks!
>  
>  
>  [1]  https://bugzilla.redhat.com/show_bug.cgi?id=2105791
>  [2] https://wiki.centos.org/SpecialInterestGroup/Messaging
>   
Hi,

good question, and sorry to keep you waiting for this long time without 
an answer. I changed roles in my job, leading to less and less time to 
contribute. The messaging SIG did not attract the contributors I hoped 
it would. I am looking for volunteers! Otherwise we should admit the 
failure here and just close the SIG.

Matthias