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.
I'm sorry to contradict you but in the rabbitmq-server side of the SIG we have contributors taking care of updating rabbitmq server:
You can simply:
# sudo dnf install -y centos-release-rabbitmq-38
#sudo dnf install -y rabbitmq-server
Best regards,
Alfredo
Matthias
_______________________________________________
CentOS-devel mailing list
CentOS-devel@centos.org
https://lists.centos.org/mailman/listinfo/centos-devel