[opensuse] Fwd: Re: [clamav-users] clamav-0.102.1 error - Update
LS, Just want to give some inside because of the outdated software in openSUSE 15.1. Just fear that 15.2 will not be much better as to up-to-date software. I hope there will be a hybrid someday between the cutting edge (sort off) Tumbleweed and the stable distributions based on very old software. Frans
I get the next report (all systems): /configure: line 30094: auto=yes: command not found
Also, check_clamav failed on 2 different systems (openSUSE 15.1). It did not failed on openSUSE Tumbleweed.
--- Frans.
On all my systems using openSUSE Tumbleweed, all tests work as expected. Alas, under openSUSE 15.1 - with it's mostly antiquated software -, which is their newest "recent" stable distribution, does the test "check_clamav" fails. This applies both to clamav-0.102.0 and .1. The clamav-0.101.x series have no such problem. Regards, Frans. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, 22 Nov 2019 20:22:19 +0100 Frans de Boer <frans@fransdb.nl> wrote:
LS, Just want to give some inside because of the outdated software in openSUSE 15.1. Just fear that 15.2 will not be much better as to up-to-date software.
I hope there will be a hybrid someday between the cutting edge (sort off) Tumbleweed and the stable distributions based on very old software.
Frans
I get the next report (all systems): /configure: line 30094: auto=yes: command not found
Also, check_clamav failed on 2 different systems (openSUSE 15.1). It did not failed on openSUSE Tumbleweed.
--- Frans.
On all my systems using openSUSE Tumbleweed, all tests work as expected. Alas, under openSUSE 15.1 - with it's mostly antiquated software -, which is their newest "recent" stable distribution, does the test "check_clamav" fails. This applies both to clamav-0.102.0 and .1. The clamav-0.101.x series have no such problem.
Regards, Frans.
I think you'll have to explain it better (in more depth) if you'd like me to understand the point you're trying to make. I have very little idea what you're talking about. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2019-11-22 21:20, Dave Howorth wrote:
On Fri, 22 Nov 2019 20:22:19 +0100 Frans de Boer <frans@fransdb.nl> wrote:
LS, Just want to give some inside because of the outdated software in openSUSE 15.1. Just fear that 15.2 will not be much better as to up-to-date software.
I hope there will be a hybrid someday between the cutting edge (sort off) Tumbleweed and the stable distributions based on very old software.
Frans
I get the next report (all systems): /configure: line 30094: auto=yes: command not found
Also, check_clamav failed on 2 different systems (openSUSE 15.1). It did not failed on openSUSE Tumbleweed.
--- Frans.
http://www.clamav.net/contact.html#ml On all my systems using openSUSE Tumbleweed, all tests work as expected. Alas, under openSUSE 15.1 - with it's mostly antiquated software -, which is their newest "recent" stable distribution, does the test "check_clamav" fails. This applies both to clamav-0.102.0 and .1. The clamav-0.101.x series have no such problem.
Regards, Frans. I think you'll have to explain it better (in more depth) if you'd like me to understand the point you're trying to make. I have very little idea what you're talking about.
Well, I have problems with the clamav-0.102.x series under Leap 15.1. So, I can't upgrade to the newest version of clamav. This stems mainly from the decision to base the Leap series upon some outdated Enterprise version - because they are so stable(?). When Leap 15.1 (and before 15.0) was introduced, some packages where already years old, despite the fact that there where already newer versions. Throughout the life-cycle of leap 15.x, there was/is little change - like modernization - except for security updates. While the world continues, there are no upgrades to the Leap 15.x series, making them ever more antiquated with respect to modern software, to the point that you are stuck with also older security software, because newer one's can't be compiled or run not stable anymore. I understand the need for stable software, but frozen software is not the way to do it. Even Windows 10 has nowadays periodic upgrades. Note: I wrote upgrades, not updates. As a long time user of SuSE and openSUSE (20+ years), I like to see some sort of hybrid version between frozen software and the rolling version if Tumbleweed. Tumbleweed is great, but sometimes I have to revert to a more stable version because Tumbleweed has a glitch sometimes. To end: yes, the above was send in out of some mild frustration. And knowing the history of those Enterprise based distributions, I fear that Leap 15.2 will produce the same or similar results. Regards, Frans. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 23/11/2019 10.57, Frans de Boer wrote:
On 2019-11-22 21:20, Dave Howorth wrote:
On Fri, 22 Nov 2019 20:22:19 +0100 Frans de Boer <> wrote: ... I think you'll have to explain it better (in more depth) if you'd like me to understand the point you're trying to make. I have very little idea what you're talking about.
Well, I have problems with the clamav-0.102.x series under Leap 15.1. So, I can't upgrade to the newest version of clamav. This stems mainly from the decision to base the Leap series upon some outdated Enterprise version - because they are so stable(?). When Leap 15.1 (and before 15.0) was introduced, some packages where already years old, despite the fact that there where already newer versions. Throughout the life-cycle of leap 15.x, there was/is little change - like modernization - except for security updates.
It has been explained often, that the Leap core is based on current SLES (not outdated SLES), basically because it saves work. The core has the SLES packages, and it is their decision which packages to use. There is another part of Leap which is modern, like KDE.
While the world continues, there are no upgrades to the Leap 15.x series, making them ever more antiquated with respect to modern software, to the point that you are stuck with also older security software, because newer one's can't be compiled or run not stable anymore.
I understand the need for stable software, but frozen software is not the way to do it. Even Windows 10 has nowadays periodic upgrades. Note: I wrote upgrades, not updates.
No known security issue, AFAIK.
As a long time user of SuSE and openSUSE (20+ years), I like to see some sort of hybrid version between frozen software and the rolling version if Tumbleweed. Tumbleweed is great, but sometimes I have to revert to a more stable version because Tumbleweed has a glitch sometimes.
I would also like to see a more modern stable version, but if there are no volunteers wanting to do it, we will not have it.
To end: yes, the above was send in out of some mild frustration. And knowing the history of those Enterprise based distributions, I fear that Leap 15.2 will produce the same or similar results.
But you have not answered the question of what is the problem with clamav. If you show why there is a security problem with the old version, and why the new version does not build, that would help. I see a home repo having version 102, and the security repo has version 101. - -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXdkMxwAKCRC1MxgcbY1H 1cvkAKCCOoSi4h3fSVqecMkJNRAm3nDlywCeNyR56wHpGIUAc/GOYOBX9JqiMIU= =m9BZ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Frans de Boer wrote:
Well, I have problems with the clamav-0.102.x series under Leap 15.1. So, I can't upgrade to the newest version of clamav.
afaics, Leap 15.1 has clamav 100.3 and there were never any updates published, right? [snip - ranting] My solution is to build clamav from source, as I have done since forever (approximately). Works very well. I don't know why newer clamav versions are not made available as updates for Leap 15.1. -- Per Jessen, Zürich (8.6°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2019-11-23 13:39, Per Jessen wrote:
Frans de Boer wrote:
Well, I have problems with the clamav-0.102.x series under Leap 15.1. So, I can't upgrade to the newest version of clamav. afaics, Leap 15.1 has clamav 100.3 and there were never any updates published, right?
[snip - ranting]
My solution is to build clamav from source, as I have done since forever (approximately). Works very well.
I don't know why newer clamav versions are not made available as updates for Leap 15.1.
Sorry, I thought I was clear: I did build all from source. As for your latter remark, see my other mailing about "frozen software" by design. -- Frans. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Frans de Boer wrote:
On 2019-11-23 13:39, Per Jessen wrote:
Frans de Boer wrote:
Well, I have problems with the clamav-0.102.x series under Leap 15.1. So, I can't upgrade to the newest version of clamav. afaics, Leap 15.1 has clamav 100.3 and there were never any updates published, right?
[snip - ranting]
My solution is to build clamav from source, as I have done since forever (approximately). Works very well.
I don't know why newer clamav versions are not made available as updates for Leap 15.1.
Sorry, I thought I was clear: I did build all from source.
Sorry, I didn't see that. Well, I have just now built 102.1 for 13.2 and 15.1, no problems. Mind you, I build for email scanning only, this is the config: --prefix=/usr --disable-clamuko --with-dbdir=/var/lib/clamav --sysconfdir=/etc --mandir=/usr/share/man --disable-clamav --without-iconv --with-included-ltdl --disable-clamdtop --disable-milter --disable-clamonacc This time, I had to add "--disable-clamonacc" because libcurl was required and quite a recent one I think. -- Per Jessen, Zürich (11.0°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2019-11-23 14:33, Per Jessen wrote:
Frans de Boer wrote:
On 2019-11-23 13:39, Per Jessen wrote:
Frans de Boer wrote:
Well, I have problems with the clamav-0.102.x series under Leap 15.1. So, I can't upgrade to the newest version of clamav. afaics, Leap 15.1 has clamav 100.3 and there were never any updates published, right?
[snip - ranting]
My solution is to build clamav from source, as I have done since forever (approximately). Works very well.
I don't know why newer clamav versions are not made available as updates for Leap 15.1.
Sorry, I thought I was clear: I did build all from source. Sorry, I didn't see that.
Well, I have just now built 102.1 for 13.2 and 15.1, no problems. Mind you, I build for email scanning only, this is the config:
--prefix=/usr --disable-clamuko --with-dbdir=/var/lib/clamav --sysconfdir=/etc --mandir=/usr/share/man --disable-clamav --without-iconv --with-included-ltdl --disable-clamdtop --disable-milter --disable-clamonacc
This time, I had to add "--disable-clamonacc" because libcurl was required and quite a recent one I think.
Building goes ok, I have mentioned that "check_clamav" failed under Leap 15.1. Same system, only now using Tumbleweed, and all is well. Regards, Frans. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 23/11/2019 21.16, Frans de Boer wrote:
On 2019-11-23 14:33, Per Jessen wrote:
Sorry, I thought I was clear: I did build all from source. Sorry, I didn't see that.
Well, I have just now built 102.1 for 13.2 and 15.1, no problems. Mind you, I build for email scanning only, this is the config:
--prefix=/usr --disable-clamuko --with-dbdir=/var/lib/clamav --sysconfdir=/etc --mandir=/usr/share/man --disable-clamav --without-iconv --with-included-ltdl --disable-clamdtop --disable-milter --disable-clamonacc
This time, I had to add "--disable-clamonacc" because libcurl was required and quite a recent one I think.
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"? - -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXdmZJAAKCRC1MxgcbY1H 1duuAJ94zj0ztLDjzFis343xuIuONTB4RgCghDmoANRkSq0IbI8EHLtUbxtvUN0= =rKLd -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2019-11-23 21:40, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 23/11/2019 21.16, Frans de Boer wrote:
On 2019-11-23 14:33, Per Jessen wrote:
Sorry, I thought I was clear: I did build all from source. Sorry, I didn't see that.
Well, I have just now built 102.1 for 13.2 and 15.1, no problems. Mind you, I build for email scanning only, this is the config:
--prefix=/usr --disable-clamuko --with-dbdir=/var/lib/clamav --sysconfdir=/etc --mandir=/usr/share/man --disable-clamav --without-iconv --with-included-ltdl --disable-clamdtop --disable-milter --disable-clamonacc
This time, I had to add "--disable-clamonacc" because libcurl was required and quite a recent one I think.
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"?
- -- Cheers / Saludos,
Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE-----
iF0EARECAB0WIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXdmZJAAKCRC1MxgcbY1H 1duuAJ94zj0ztLDjzFis343xuIuONTB4RgCghDmoANRkSq0IbI8EHLtUbxtvUN0= =rKLd -----END PGP SIGNATURE-----
One of the tests clamav can run. --- Frans -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----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----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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 -- Per Jessen, Zürich (8.9°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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
Frans de Boer wrote: ============================================================================
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.
I also have "disable-clamav", although that doesn't even seem to be a valid option anymore. (it's not listed in the help).
Also, I hate it when someone enters the discussion, and as usually without any understanding of the subject - not being you Per.
Haha, thanks Frans. :-)
Beside that, there are more issues with the 0.102.x series which are not dependent on the environment,
Would you mind sharing with us? -- Per Jessen, Zürich (8.7°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 24/11/2019 12.09, Per Jessen wrote:
Frans de Boer wrote:
====================================================================== ======
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.
I also have "disable-clamav", although that doesn't even seem to be a valid option anymore. (it's not listed in the help).
Also, I hate it when someone enters the discussion, and as usually without any understanding of the subject - not being you Per.
That means me. I should be offended.
Haha, thanks Frans. :-)
Beside that, there are more issues with the 0.102.x series which are not dependent on the environment,
Would you mind sharing with us?
- -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXdqOtAAKCRC1MxgcbY1H 1fmrAJ9vxMBQqsF0nKl9UXtVdK22ZUkttgCdHllrXYYQ5De9NoL6c+RnsgP2qeg= =hORF -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 24/11/2019 11.11, Per Jessen wrote:
Frans de Boer wrote:
On 2019-11-23 22:31, Carlos E. R. wrote: 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.
clamav not distributed? Look again.
check_clamav is not generally distributed to openSUSE users, I'm sure that is what Carlos meant.
No, that the utility "check_clamav" is not distributed. From your answer, I guess that it is a make target instead. How is the majority of mail list users, who don't build clamav themselves, going to know that? -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
participants (5)
-
Carlos E. R. -
Carlos E. R. -
Dave Howorth -
Frans de Boer -
Per Jessen