> Date: Saturday, May 14, 2016 16:20:41 -0700 > From: Alice Wonder <alice at domblogger.net> > > On 05/14/2016 01:22 PM, Walter H. wrote: >> Hello, >> >> just curious; >> since March 3rd, 2016 everdays logwatch-mail >> shows this: >> >> Last Status: >> WARNING: Your ClamAV installation is OUTDATED! >> WARNING: Local version: 0.99 Recommended version: 0.99.1 >> >> >> on May 4th, 2016 I updated clamav by >> yum update clamav >> since then the daily logwatch-mail >> shows this: >> >> Last Status: >> WARNING: Your ClamAV installation is OUTDATED! >> WARNING: Local version: 0.99.1 Recommended version: 0.99.2 >> >> I guess, that it happened accidentally, that I just updated the day >> before ClamAV did a bigger change; >> as I had tried 'yum update clamav' several times before; >> >> do these warnings raise any problems? >> could they be suppressed? >> >> Greetings, >> Walter >> >> > > It's been awhile since I used ClamAV but when I did, I would > rebuild the new version by modifying the src.rpm of the old version > to the new version but using a 0 in the release tag so that it > would be replaced by a repo maintained version as soon as it hit > the repositories. >It generally takes a week or so for an update to make it to epel. They are still showing 0.99.1-1. You might want to check the epel-testing repo in a couple of days. I think that that clamav warning message is a bit more dire sounding than necessary.
On Sun, May 15, 2016 at 02:55:01AM +0000, Richard wrote:> > > Date: Saturday, May 14, 2016 16:20:41 -0700 > > From: Alice Wonder <alice at domblogger.net> > > > > On 05/14/2016 01:22 PM, Walter H. wrote: > >> Hello, > >> > >> just curious; > >> since March 3rd, 2016 everdays logwatch-mail > >> shows this: > >> > >> Last Status: > >> WARNING: Your ClamAV installation is OUTDATED! > >> WARNING: Local version: 0.99 Recommended version: 0.99.1 > >> > >> do these warnings raise any problems? > >> could they be suppressed? > >> > > It's been awhile since I used ClamAV but when I did, I would > > rebuild the new version by modifying the src.rpm of the old version > > to the new version but using a 0 in the release tag so that it > > would be replaced by a repo maintained version as soon as it hit > > the repositories. > > > > It generally takes a week or so for an update to make it to epel. > They are still showing 0.99.1-1. You might want to check the > epel-testing repo in a couple of days. > > I think that that clamav warning message is a bit more dire sounding > than necessary. >Agreed. As an observation, I don't update daily, but more than once a week. For the last two clamav updates, 0.98.7->0.99 and 0.99->0.99.1, the warnings lasted for 5 and 4 weeks. jon -- Jon H. LaBadie jon at jgcomp.com 11226 South Shore Rd. (703) 787-0688 (H) Reston, VA 20190 (703) 935-6720 (C)
On 15 May 2016 07:11, "Jon LaBadie" <jcu at labadie.us> wrote:> > On Sun, May 15, 2016 at 02:55:01AM +0000, Richard wrote: > > > > > Date: Saturday, May 14, 2016 16:20:41 -0700 > > > From: Alice Wonder <alice at domblogger.net> > > > > > > On 05/14/2016 01:22 PM, Walter H. wrote: > > >> Hello, > > >> > > >> just curious; > > >> since March 3rd, 2016 everdays logwatch-mail > > >> shows this: > > >> > > >> Last Status: > > >> WARNING: Your ClamAV installation is OUTDATED! > > >> WARNING: Local version: 0.99 Recommended version: 0.99.1 > > >> > > >> do these warnings raise any problems? > > >> could they be suppressed? > > >> > > > It's been awhile since I used ClamAV but when I did, I would > > > rebuild the new version by modifying the src.rpm of the old version > > > to the new version but using a 0 in the release tag so that it > > > would be replaced by a repo maintained version as soon as it hit > > > the repositories. > > > > > > > It generally takes a week or so for an update to make it to epel. > > They are still showing 0.99.1-1. You might want to check the > > epel-testing repo in a couple of days. > > > > I think that that clamav warning message is a bit more dire sounding > > than necessary. > > > Agreed. As an observation, I don't update daily, but more than > once a week. For the last two clamav updates, 0.98.7->0.99 and > 0.99->0.99.1, the warnings lasted for 5 and 4 weeks. >Well it's not even been built for rawhide yet: apps.fedoraproject.org/packages/clamav I know nb has been pretty busy this week, letsencrypt rebranded to certbot and we've been validating the package rename etc Keep an eye on this bug for activity: bugzilla.redhat.com/show_bug.cgi?id=1333949
On Sun, May 15, 2016 04:55, Richard wrote:> > It generally takes a week or so for an update to make it to epel. > They are still showing 0.99.1-1. You might want to check the > epel-testing repo in a couple of days.wouldn't it be a good idea to include libclamunrar.so and libclamunrar_iface.so?> I think that that clamav warning message is a bit more dire sounding > than necessary.I agree; Greetings, Walter