Bug 1492018

Summary: please update rabbitmq-server to a newoer on epel-7 too
Product: [Fedora] Fedora EPEL Reporter: Levente Farkas <lfarkas>
Component: rabbitmq-serverAssignee: Peter Lemenkov <lemenkov>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel7CC: andreas.luik, aurelien, hubert.plociniczak, jal233, jeckersb, lemenkov, rjones, s, trevor.hemsley
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-07-09 02:12:21 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Levente Farkas 2017-09-15 09:38:11 UTC
it seems the epel-7 packages are a few years older then the current fedora or even the latest released rabbitmq-server.
would you build the latest to epel-7 too?
thanks

Comment 1 Richard W.M. Jones 2017-09-15 13:07:32 UTC
EPEL 7 has 3.3.5-34.el7

However I think the problem could be that rabbitmq-server is also
shipped in RHOSP (for OpenStack) and so it shouldn't be in EPEL at
all.  Latest RHOSP package is rabbitmq-server-3.6.3-7.el7ost.

Having said that, I don't see the package in CentOS, so I don't
know why that is.

Comment 2 Levente Farkas 2017-09-15 13:37:02 UTC
yes it is in openstack but it has a lot's of erlang dependencies so it'd be better to include in epel. and because adding openstack repo cause update other packages which i don't really like to do so.

Comment 3 Trevor Hemsley 2017-10-30 16:45:52 UTC
I don't believe that RHOSP is one of the RHEL channels that EPEL track. https://fedoraproject.org/wiki/EPEL/FAQ#Does_EPEL_replace_packages_provided_within_Red_Hat_Enterprise_Linux_or_layered_products.3F

The current version in EPEL is from 2014 and is no longer listed as a current product on the rabbitmq website - the oldest branch there is 3.4 though I do see that the 3.3.5 rpm changelog has fixes listed up until March 2017

Current rabbitmq version is 3.6.12 and there are several security updates listed in the "release" blog on the rabbitmq site dated after the release of 3.3.5. Those may not be applicable to the 3.3.5 version as it doesn't say when the bugs were introduced. The rpm changelog could be informative but unfortunately mostly references fixed bugs only by their bz number and a large number of them are inaccessible to non-redhat.com users.

Comment 4 Aurelien Bompard 2018-10-24 07:38:10 UTC
Hey folks! According to RabbitMQ's changelog [1], version 3.6 was end-of-life'd in June this year.

[1] https://www.rabbitmq.com/changelog.html

Are there plans to update to 3.7? (Rawhide is also at 3.6 by the way)

Comment 5 John Eckersberg 2018-10-24 14:36:37 UTC
I think this work will probably all end up in the new Messaging SIG which is currently being spun up:

https://wiki.centos.org/SpecialInterestGroup/Messaging

The EPEL lifecycle is not so great for something like RabbitMQ.  Rebasing is generally frowned upon, and for RabbitMQ specifically there are edge issues upgrading between different versions (sometimes even between minor revisions, see https://www.rabbitmq.com/upgrade.html#rolling-upgrades-version-limitations).  The Messaging SIG will allow more freedom to maintain multiple series in parallel, so we can have the latest and greatest available, while also maintaining older stable versions with only important fixes.

Comment 6 Troy Dawson 2024-07-09 02:12:21 UTC
EPEL 7 entered end-of-life (EOL) status on 2024-06-30.\n\nEPEL 7 is no longer maintained, which means that it\nwill not receive any further security or bug fix updates.\n As a result we are closing this bug.