First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 85365
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Qmail Team <qmail-bugs@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Erik Wasser <erik.wasser@iquer.net>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
configure-kav-sandbox.patch patch for the ebuild patch Erik Wasser 2005-03-15 09:13 0000 792 bytes Details | Diff
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 85365 depends on: Show dependency tree
Show dependency graph
Bug 85365 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)







View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2005-03-15 09:11 0000 
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-)

------- Comment #1 From Erik Wasser 2005-03-15 09:13:27 0000 ------- 
Created an attachment (id=53545) [edit]
patch for the ebuild

Apply this patch *after* the other patch from the ebuild

------- Comment #2 From Robin Johnson 2005-04-04 21:59:33 0000 ------- 
no, don't do it that way.
use addpredict in the ebuild instead!

------- Comment #3 From Erik Wasser 2005-04-05 01:07:37 0000 ------- 
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-)

------- Comment #4 From Lim Swee Tat (RETIRED) 2005-04-05 01:26:12 0000 ------- 
Added addpredict.
First Last Prev Next    No search results available      Search page      Enter new bug