> > I've been getting those messages too for about a week. I updated to > > the devel version on December 26th, after staying with 0.75 for too > > long. I do *not* have any old copies of either libclamav or freshclam > > anywhere; I've checked carefully with "find" and "locate". clamscan -V > > reports ClamAV devel-20041226/702/Wed Feb 9 06:31:34 2005 > > You are running a copy between 80 and 81. .81 was released on Jan 26, and > .82 on Feb 06 of this year.
Thank you to both of the people who pointed this out. I think there may be an assumption on the part of the authors that all the clamav users actually run the command and see the warnings. For me at least that is not the case, it is invoked by an SMTP filter and I never see it, except sometimes accidentally when I'm checking something. The traffic on this list is way too high to read every post (at least for someone like me who just uses the code and is not actively tracking every minor change - something I dare not do on a production system) and the releases that force a rebuild are *not* clearly marked in the subject lines in this group. I always miss them. That may be my failing but I bet I'm not alone. Can I suggest a mailing list for announcements to be used for "must do" upgrades using the stable source chain; or at a minimum a very visible subject line to be standardised on, maybe to the extent that I can catch it consistently with a procmail filter to ensure it stands out. I appreciate all the work you guys do keeping this code up to date, but I get the impression that the majority of users are 'bleeding edge' developers. Please keep us plodders in mind too, where our primary goal is stability and a lack of surprises and sudden urgent repairs. I've seen way too many posts of people installing new fixes then having something break to be willing to do that. thanks Graham _______________________________________________ http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
