Re: Re-2: [VUA 31-1] Updated clamav package

[Tobias Ulbricht <ulbricht@tkm.uni-karlsruhe.de>]

Hello.

Matus UHLAR - fantomas wrote:
> > > > AFAIK the correct syntax for NotifyClamd option in freshclam.conf is:
> > > > NotifyClamd /path/to/clamd.conf/file eg: NotifyClamd /etc/clamav/clamd.conf
> > > > instead of "NotifyClamd true".
> > >
> > > maybe the thread on 
> > > http://lists.debian.org/debian-volatile/2007/03/msg00017.html helps?
>
>
> On 04.04.07 10:50, dominik.habbel@wkn-online.com wrote:
>
> > The Problem is already solved. Sorry, it was my fault: I accidently installed package 0.90.1-0volatile1 instead of volatile2. The problem should not occur in volatile2.
>
>
> Please, teach your MUA to wrap lines below 80 characters, by not doing this
> you violate http://www.debian.org/MailingLists/#codeofconduct
>
> ...How could that happen? Do you install volatile packages manually?

Since this is an issue for several days now, I post again to the list:

apt-get update
<snip>
grep clamav-freshclam /var/lib/apt/lists/* -h | grep Filename
<snip>
pool/volatile/main/c/clamav/clamav-freshclam_0.90.1-0volatile1_i386.deb

The package "*volatile2*" _is_ on the server, but the Packages* files 
are not up-to-date.
I regularly check this on volatile.debian.net since the announcement of 
the update.

I don't know who does the update of the Packages* files, but you should 
know, that ATM there is no automatic update of clamav-* packages to 
volatile2, ( except the "clamav" package itself, which is correctly at 
*volatile2*)

Cheers,
Tobias.