As the current FE packager I'm not too convident in the zoo code. This year zoo security alerts showed the original code was not written with the current malware-ridden internet in mind, and no one seems willing to do a full zoo security audit. If feel deploying zoo today in amavisd-new is a mistake (that upstream makes), with the problems in zoo far obsetting the security wins of scanning zoo files (who uses them anymore anyway). I'd like the dep in amavis on zoo dropped, which would allow killing the zoo FE package before someone finds the next problem in it. Doing the change before FC6 is probably the best solution. But there is no emergency
I've removed the zoo dep from 2.4.1-1, which is building right now.
Thanks a lot, that was a lot more fast than this bug deserved ;) As soon as this release hits users I'll start the kill-zoo procedure