Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
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
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
|
DetailsDescription:
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
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
I filed an upstream bug on this, since this appears to be an upstream issue with the build system:
https://bugzilla.clamav.net/show_bug.cgi?id=12761