Bug 454442

Summary: New version of amavisd-new available
Product: [Fedora] Fedora Reporter: Johan Kok <johan-fedora>
Component: amavisd-newAssignee: Steven Pritchard <steve>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: rawhideCC: perl-devel
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-10-27 03:28:08 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:
Bug Depends On: 454687    
Bug Blocks:    

Description Johan Kok 2008-07-08 14:56:54 UTC
Description of problem:
On 2008-06-29 amavisd-new 2.6.1 was released. Rawhide has version 2.5.2. Could
you update amavisd-new to the latest release?

Version-Release number of selected component (if applicable):
2.5.2-2

How reproducible:
Always

Comment 1 Jason Tibbitts 2008-10-23 21:48:14 UTC
Unfortunately the review for perl-Mail-ClamAV, which the new amavisd depends on, stalled out after 2.5 months with no response from the submitter.  Unless that ticket is revived or someone else submits the package, I don't know what progress can be made on this ticket.

Comment 2 Johan Kok 2008-10-24 12:15:03 UTC
(In reply to comment #1)
> Unfortunately the review for perl-Mail-ClamAV, which the new amavisd depends
> on, stalled out after 2.5 months with no response from the submitter.  Unless
> that ticket is revived or someone else submits the package, I don't know what
> progress can be made on this ticket.

Thanks for reporting. Maybe I'm missing the obvious here, but why do we need perl-Mail-Clamav for a update of amavisd-new? The RELEASE_NOTES for the new version does not seem to mention something major about Mail::Clamav.

Comment 3 Christopher D. Stover 2008-10-27 03:28:08 UTC

*** This bug has been marked as a duplicate of bug 456144 ***