On Mon, Jun 27, 2011 at 11:52 AM, Camaleón <noela...@gmail.com> wrote:
> On Mon, 27 Jun 2011 13:58:43 +0200, Eric Viseur wrote: > > > In my understanding, the stable-updates repo was esthablished in order > > to replace the volatile repo. Thus, updated clamav should be pushed in > > it, but I note it's only available in the testing branch. Did I > > misunderstood the role of the stable-updates repo, or is clam 0.97.1 > > just coming in late ? > > Nope, your understaing is totally correct, but... > > > I have a server complaining about clam not being up to date every > > night, so it's getting a little annoying, and I'd like to avoid apt > > -pinning if possible. > > ... for the stable/olstable branch is my understanding that only security > bugfixes are corrected, so if the clamav update does not closes any > serious flaw you will keep seeing the clamav warning at the logs. But > don't worry, your clients are still protected, your AV firms updated and > your files analyzed for any treat. > This is incorrect. Here are the announcement of squeeze-updates, with a list of reasons why squeeze-updates will push ahead a release... http://lists.debian.org/debian-volatile-announce/2011/msg00000.html It even mentions clamav as one which needs to be current to be useful. Our expectations for squeeze-updates to release clamav ahead of stable merely to be current are correct. Note you don't need to use squeeze-updates, so we are opting into something which can be a little more bleeding edge. If you only want security and bug fixes that is handled by security repo and standard stable repo.
