> > > > Sorry. I should have included version info: > > > > $ rpm -qa | grep fail2ban > > > > fail2ban-0.6.2-3.el5 > > > > > > Why don't you upgrade to a later version? I've seen several > > other complaints regarding similar iptables errors with > > fail2ban and it seems an upgrade is what everyone was proposing. > > > > Justin, > > This is the latest version for RHEL5 in the EPEL repository. Is anyone > > at Red Hat actually tracking this package, or is its inclusion in EPEL > > just a convenience? > > I've been told and also read somewhere that the contents of EPEL is on > the sponsors' shoulders. It's existence is for our convenience.
if someone is concerned about the current status of an EPEL (or even RHEL or Fedora) package you have a few routes base on my experience. IMHO the best option is to download the latest SRPM and update it to the latest version of the package, then send an e-mail to the package maintainer(s) offering up the new SRPM for their review. Sometimes there is a good technical reason they haven't updated it, but other times it could just be because they've been busy (it happens to all of us). At the end of it you at least have the updated package for yourself, which if you have space you can host for the others you've found in your position. If upping the package is something you don't feel comfortable with, you can try contacting the packager in a similar manner, asking if they know when it will be updated, or just filing a bug in the appropriate distribution's bugzilla. -greg _______________________________________________ rhelv5-list mailing list rhelv5-list@redhat.com https://www.redhat.com/mailman/listinfo/rhelv5-list
