Bug 444794

Summary:	Ping for update
Product:	[Fedora] Fedora EPEL	Reporter:	Jim Perrin <james.l.perrin>
Component:	mod_security	Assignee:	Michael Fleming <mfleming+rpm>
Status:	CLOSED NEXTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	low
Version:	el5
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-05-05 10:03:32 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jim Perrin 2008-04-30 16:43:37 UTC

Description of problem:
Just a simple ping for update. 

Version-Release number of selected component (if applicable):
Current in Epel is 2.1.3. Current for mod_security is either 2.1.7, or 2.5.3
depending on upgrade desires.

How reproducible:
always

Steps to Reproduce:
1. check version on website
2. check version in epel
3.
  
Actual results:
2.1.3

Expected results:
2.5.3

Additional info:

Comment 1 Michael Fleming 2008-05-01 01:24:46 UTC

Well, this is EPEL so I'm loathe to make *too* radical a change just yet - I'll
put together a 2.1.7 release which I'll test, commit and release shortly.

Comment 2 Jim Perrin 2008-05-01 02:22:24 UTC

This works for me. The only reason I was thinking about 2.5.3 was for the
auto-rule update script in place, and the speed improvements/caching
functionality. 2.1.7 works just fine though, so thanks for the update!

Comment 3 Michael Fleming 2008-05-05 10:03:32 UTC

It's my pleasure - I'm assuming you've seen the package go into -testing then.
:-) Let me know if there's any issues.