Mojave port install p5.26-mail-clamav fails

[Ryan Schmidt]

On Oct 28, 2018, at 19:18, Bill Cole wrote:

> On 27 Oct 2018, at 8:27, Steve Wardle wrote:
> 
>> # port list clamav
>> clamav                         @0.100.2        sysutils/clamav
> 
> Not relevant, because 'port list' shows the only *available* version, not the version you have installed. To show what version(s) you have installed 'port installed' and to see the one which is active, 'port active'.  If you're installing a port for the first time, neither of those will show anything.

There's no "port active". "active" is a pseudoport, not a command. You can use pseudoports with any command, for example you could use "port installed active" to run the "installed" command (to show information about installed ports) restricted to the set of ports that are active.


> However, that isn't in question because your log shows:
> 
> :debug:main clamav 0.100.2_0 exists in the ports tree
> :debug:main clamav 0.100.2_0  is the latest installed
> :debug:main clamav 0.100.2_0  is active
> 
> The message about clamav being too old is coming from running the Makefile.PL script of the Mail::ClamAV module in the MacPorts 'configure' phase, which sets up the actual Makefile for the build phase, where the actually fatal error occurs. Makefile.PL uses 'clamav-config --version' to get the version of the current ClamAV installation, so there is something wrong with what that command is returning. If this is a machine that has a history (i.e. pre-Mojave) it is possible that you have another antique installation of ClamAV somewhere and a PATH environment variable that puts the old clamav-config ahead of the MacPorts version. Try this:
> 
> which -a clamav-config
> 
> That should return '/opt/local/bin/clamav-config' and nothing else.

It's already been fixed. Mail::ClamAV had a bug correctly identifying versions of ClamAV greater than 0.100.