Jeffrey Ross wrote:
The upgrade for Clamav that just came out seems to have broken
exim-clamav, more precisely removed exim-clamav.
If I attempt to upgrade clamav and clamd I am told that there are
conflicts:
Problem 1: package exim-clamav-4.92.3-1.fc31.x86_64 requires
clamav-server, but none of the providers can be installed
- cannot install both clamd-0.101.5-7.fc31.x86_64 and
clamd-0.101.4-1.fc31.x86_64
- cannot install both clamd-0.101.4-1.fc31.x86_64 and
clamd-0.101.5-7.fc31.x86_64
- cannot install the best update candidate for package
exim-clamav-4.92.3-1.fc31.x86_64
- cannot install the best update candidate for package
clamd-0.101.4-1.fc31.x86_64
Problem 2: problem with installed package
exim-clamav-4.92.3-1.fc31.x86_64
- package exim-clamav-4.92.3-1.fc31.x86_64 requires clamav-server, but
none of the providers can be installed
- package clamd-0.101.4-1.fc31.x86_64 requires clamav-filesystem =
0.101.4-1.fc31, but none of the providers can be installed
- package clamav-filesystem-0.101.4-1.fc31.noarch conflicts with clamav
> 0.101.4-1.fc31 provided by clamav-0.101.5-7.fc31.x86_64
- cannot install the best update candidate for package
clamav-0.101.4-1.fc31.x86_64
I don't follow the clamav packaging closely, but it looks
like the clamav-server subpackage was renamed to clamd a few
years ago¹. Perhaps that's what exim-clamav should be
requiring?
It certainly seems like something worthy of filing in
bugzilla so that it can be fixed in either the exim or
clamav package (or both).
¹
https://src.fedoraproject.org/rpms/clamav/c/1977bd
--
Todd