During the installation the package tests a lot of scanners for the configuration of the big perl script 'qmail-scanner-queue.pl'. The kaspersky 5.0.4.0 opens during the (test-)scan some logfiles and that will break the sandbox: --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/tmp/sandbox-mail-filter_-_qmail-scanner-1.25-23779.log" unlink: /var/log/kav/kavscan.log open_wr: /var/log/kav/kavscan.log open_wr: /var/log/kav/kavscan.log open_wr: /var/log/kav/kavscan.log open_wr: /var/log/kav/kavscan.log You found this test scan in the 'configure' file of the source. The script tries to start the 'kavscanner' (with a temporary directory for scanning) and parses the output. Instead of starting the scanner I decide to grep the binary for the test string and evaluate the result in the same way the original source did. Apply the attachement and everything is fine. B-)
Created attachment 53545 [details, diff] patch for the ebuild Apply this patch *after* the other patch from the ebuild
no, don't do it that way. use addpredict in the ebuild instead!
Oh... I don't know about this command. Then forget about the patch. This should be easy for the maintainer to do it for himself. B-)
Added addpredict.
