FS#68732 - [clamav] clamav-clamonacc service contains variable that's not replaced during build

Attached to Project: Arch Linux
Opened by Kyle Tirak (hamsterkill) - Tuesday, 24 November 2020, 14:23 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:16 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Levente Polyak (anthraxx)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No



The clamav-clamonacc service contains the the variable "@APP_CONFIG_DIRECTORY@" on the ExceStart line:

ExecStart=/usr/sbin/clamonacc -F --config-file=@APP_CONFIG_DIRECTORY@/clamd.conf --log=/var/log/clamav/clamonacc.log --move=/root/quarantine

It should be replaced during the build process as other variables are, but it seems to make it through to the end user -- preventing the service from starting due to an invalid path for the config file.

Scanning with the service once started also doesn't work, but that appears to be an upstream issue.

Additional info:
* Package: clamav-0.103.0-1
This task depends upon

Closed by  Buggy McBugFace (bugbot)
Saturday, 25 November 2023, 20:16 GMT
Reason for closing:  Moved
Additional comments about closing:  https://gitlab.archlinux.org/archlinux/p ackaging/packages/clamav/issues/3
Comment by Richard Neumann (rne) - Wednesday, 02 June 2021, 15:14 GMT
The problem still persists in clamav 0.103.2-1.
I filed an upstream bug on this, since this appears to be an upstream issue with the build system:
Comment by Buggy McBugFace (bugbot) - Tuesday, 08 August 2023, 19:11 GMT
This is an automated comment as this bug is open for more then 2 years. Please reply if you still experience this bug otherwise this issue will be closed after 1 month.