I already had amavis & f-prot emerged. On 5Jun03, after rsyncing that morning, I did an emerge -u world. This upgraded amavis, which also made clam antivirus installed. However, I already had f-prot installed, providing virtual/antivirus. Not a big deal, since I was able to uninstall clam antivirus, and reconfigure it to f-prot, but it is a pain to have to do that (especially since clam av didn't work right off the bat, and so I had to reconfigure in order to have a working smtp antivirus filtering). Reproducible: Always Steps to Reproduce: 1. have amavis & f-prot installed 2. emerge -u world 3. now amavis is configured for clam av instead. Actual Results: /usr/sbin/amavis was no longer configured to use f-prot, and was now configured to use clamd. Expected Results: I expected the ugpraded amavis to continue working with f-prot.
Have you re-merged f-prot since the virtual/antivirus came into effect (ie. since amavis 0.3.12 (non -pre8) was put into portage? If not, the system would not have realised that the virtual has been satisfied (ie. there would not be an entry in /var/cache/edb/virtuals for virtual/antivirus). Since it did not know the virtual was satisfied, the default to satisfy this virtual is clamav. You should be able to resolve this problem by unmerging clamav and re-merging f-prot, and then re-merging amavis. Please let me know how this works out.
I have added PROVIDE="virtual/antivirus" to the f-prot-4.1.2.ebuild
closing.
