Bug 1054356 - update mod_cluster epel to 1.2
Summary: update mod_cluster epel to 1.2
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: mod_cluster
Version: el6
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Marek Goldmann
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2014-01-16 16:56 UTC by Andy Rosequist
Modified: 2014-03-21 22:31 UTC (History)
1 user (show)

Fixed In Version: mod_cluster-1.2.6-3.1.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2014-03-21 22:31:05 UTC
Type: Bug

Attachments (Terms of Use)

Description Andy Rosequist 2014-01-16 16:56:38 UTC
Description of problem:
EPEL6 has mod_cluster as version 1.1, but 1.2 has been out and stable for 18 months and counting. 1.2 improves integration with JBoss AS7, which runs great on RHEL6. 

Can the 1.2 version of mod_cluster be built for EPEL6 please?

Comment 1 Marek Goldmann 2014-01-17 08:04:58 UTC
I'm looking into this.

Comment 2 Marek Goldmann 2014-01-17 08:33:28 UTC
Please try this scratch build: http://koji.fedoraproject.org/koji/taskinfo?taskID=6418533

Comment 3 Andy Rosequist 2014-01-17 20:34:23 UTC
Awesome! that rpm works on a test box, which is running:
Red Hat Enterprise Linux Server release 6.4 (Santiago)

Comment 4 Fedora Update System 2014-01-23 11:36:27 UTC
mod_cluster-1.2.6-3.1.el6 has been submitted as an update for Fedora EPEL 6.

Comment 5 Fedora Update System 2014-01-23 20:14:08 UTC
Package mod_cluster-1.2.6-3.1.el6:
* should fix your issue,
* was pushed to the Fedora EPEL 6 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=epel-testing mod_cluster-1.2.6-3.1.el6'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).

Comment 6 Fedora Update System 2014-03-21 22:31:05 UTC
mod_cluster-1.2.6-3.1.el6 has been pushed to the Fedora EPEL 6 stable repository.  If problems still persist, please make note of it in this bug report.

Note You need to log in before you can comment on or make changes to this bug.