![](https://seccdn.libravatar.org/avatar/b767d4c5c20a94b6e2ec9d675178f650.jpg?s=120&d=mm&r=g)
On 2019-11-24 11:11, Per Jessen wrote:
Frans de Boer wrote:
On 2019-11-23 22:31, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 23/11/2019 21.58, Frans de Boer wrote:
On 2019-11-23 21:40, Carlos E. R. wrote: On 23/11/2019 21.16, Frans de Boer wrote:
> On 2019-11-23 14:33, Per Jessen wrote: ...
> Building goes ok, I have mentioned that "check_clamav" failed > under Leap 15.1. Same system, only now using Tumbleweed, and > all is well. What is "check_clamav"? One of the tests clamav can run. As it is not distributed, most of us do not know what it involves.
- -- Cheers / Saludos,
Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE-----
iF0EARECAB0WIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXdmlLwAKCRC1MxgcbY1H 1bwJAJ42+XlLtSDYuIhRtxyfjfhY3SlyhQCeJn8IOYt+/G7dmivfv+X1F3ZVntk= =anC1 -----END PGP SIGNATURE-----
clamav not distributed? Look again. check_clamav is not generally distributed to openSUSE users, I'm sure that is what Carlos meant.
FWIW, I ran a "make quick-check" - check_clamav was skipped,
SKIP: check_clamav PASS: check_freshclam.sh PASS: check_sigtool.sh SKIP: check_unit_vg.sh PASS: check1_clamscan.sh PASS: check2_clamd.sh PASS: check3_clamd.sh PASS: check4_clamd.sh SKIP: check5_clamd_vg.sh SKIP: check6_clamd_vg.sh SKIP: check7_clamd_hg.sh SKIP: check8_clamd_hg.sh SKIP: check9_clamscan_vg.sh ============================================================================ Testsuite summary for ClamAV 0.102.1 ============================================================================ # TOTAL: 13 # PASS: 6 # SKIP: 7 # XFAIL: 0 # FAIL: 0 # XPASS: 0 # ERROR: 0
It is skipped because you told me that you did not build with clamonacc, because of libcurl. Also, I hate it when someone enters the discussion, and as usually without any understanding of the subject - not being you Per. The FAIL: check_clamav I get always suggests that the environment variable T should be increased. From the clamav community I have been told that increasing the T variable does not work correctly. But beside that, it is the same hardware and why should Leap 15.1 not work and Tumbleweed has no problem? I am now closing this thread - for me - because it is a Leap 15.1 environment problem, which will not be solved. Beside that, there are more issues with the 0.102.x series which are not dependent on the environment, so I revert back to the 0.101.x series. Regards, Frans. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org