Bug 249079

AFAIK, we're still missing a bunch of dependencies.

Setting up a test box (or VM) to verify is on my list of things to do.

And yes, I do intend to maintain amavisd-new (and most of the rest of my 
packages) for EPEL, but unravelling all the dependencies to get things 
bootstrapped is difficult.

I see. I'll try to support you where possible. My employer maybe uses RHEL/ 
compatible for the new mail servers running clamav + amavisd-new. If we could 
use EPEL packages, I'm also willing to maintain some. But this isn't fix yet 
at all (whether RHEL or not). Nevertheless it would be an advantage for EPEL.

If you want to help, find me a way to graph all the build and run-time 
dependencies.  :-)

http://home.comcast.net/~prarit/thetango/

Robert already requested EPEL 4 and 5 branches for clamav in bug #249081

I could start with requesting EPEL branches for a few other dependencies, but if a clamav branch is not 
possible, that sounds quite pointless to me.

Clamav is possible and already branched to EPEL but in an older version which 
can't be upgraded, because it breaks EPEL guidelines. IIRC the older clamav has 
the problem, that it can't read newer signatures - that's worse.

(In reply to comment #6)
> Clamav is possible and already branched to EPEL but in an older version 
which 
> can't be upgraded, because it breaks EPEL guidelines. IIRC the older clamav 
has 
> the problem, that it can't read newer signatures - that's worse.

I can't imagine why anyone would want an old, insecure version of clamav in 
EPEL.  We need to use whatever works.

Sorry for the Bugzilla spam. I think, now I filed any missing build and run-
time dependencies into bug reports requesting the packages rebuilt for EPEL.

Steven, the main problem of clamav 0.88.x vs. 0.9x.x IIRC is, that the 
configuration files got incompatible and you can't simply upgrade without 
breaking things. As I got informed, wtogami wanted to look into, but nothing 
happened, yet? Warren? Any status?

I have nothing to do with clamav.

*** Bug 297121 has been marked as a duplicate of this bug. ***

Steven? You imported an old version of amavisd-new into EPEL 5 but none into
EPEL 4 - is this correct and why? And why is an old version in EPEL 5? Latest
version from Fedora Rawhide seems to work for me (on both).

I'll build the latest version on both branches as soon as all of the
dependencies are met.

It's *really* close now.

I discovered two missing dependencies on RHEL 4 and filed bug reports.

Based on the date this bug was created, it appears to have been reported
during the development of Fedora 8. In order to refocus our efforts as
a project we are changing the version of this bug to '8'.

If this bug still exists in rawhide, please change the version back to
rawhide.
(If you're unable to change the bug's version, add a comment to the bug
and someone will change it for you.)

Thanks for your help and we apologize for the interruption.

The process we're following is outlined here:
http://fedoraproject.org/wiki/BugZappers/F9CleanUp

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

Steven, ping?

Let me see where all the dependencies are at and get back to you.

What little Fedora time I have at the moment is being spent on getting things
right for Fedora 9 though, so it might be a couple of weeks or so before I have
an answer for you.

Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Ping?

I'm going to work on updating rawhide to the latest version (see bug 454442), so
while I'm at it, I'll try to figure out what it will take to get that into EL-5
at least.

This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Working against bug zapper once more...Rawhide.

(In reply to comment #19)
> I'm going to work on updating rawhide to the latest version (see bug 454442), so
> while I'm at it, I'll try to figure out what it will take to get that into EL-5
> at least.  

The amavisd-new package in rawhide was updated to version 2.6.2. A local mock rebuild of that SRPM from rawhide completes without a problem for EL-5 and EL-4.

Please let me know if I there is something I can assist with to get amavisd-new updated.

This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Changing version back to rawhide and ping. Steven, how close are we to finishing this one?

This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

All bugs that this one depends on appear to be resolved. Latest f12 release rebuilds fine for EPEL 4 and 5 [1,2]. When will this version be released to EPEL?

[1] https://koji.fedoraproject.org/koji/taskinfo?taskID=2076064
[2] https://koji.fedoraproject.org/koji/taskinfo?taskID=2076025

Changing back version to rawhide. Can I do anything to help resolve this issue?

This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

RHEL4 is unsupported now, so is EPEL4.

EPEL5 still ships 2.4 series, as I'm not familiar with EL5, hope the assignee can give a perfect solution(Or WONTFIX is OK)

I requested update to EPEL6 and got nice results so I think there should only have issue with EPEL5, re-assign to EPEL.

As the initial reporter I am satisfied with the current results (given that I
spend some love from time to time to amavisd-new on Fedora and Fedora EPEL 6).