Bug#467298: updating etch -> volatile helps

also sprach Fabian Ruff <[EMAIL PROTECTED]> [2008.04.07.0049 +0200]: > I think that updating to volatile doesn't really fixes the problem: > > I've experienced the same problems as mentioned above and updated to > volatile about 3-4 weeks ago: > > ~# apt-show-versions |grep clamav > clamav-base/etc

Bug#467298: updating etch -> volatile helps

Hello, I think that updating to volatile doesn't really fixes the problem: I've experienced the same problems as mentioned above and updated to volatile about 3-4 weeks ago: ~# apt-show-versions |grep clamav clamav-base/etch uptodate 0.92.1~dfsg-1volatile1 clamav-daemon/etch uptodate 0.92.1~dfs

Bug#467298: updating etch -> volatile helps

Hi, Florian Schlichting schrieb: > I just updated to volatile (0.92.1...), and all remaining updates were > downloaded like a breeze! I experienced exactly the same. > I think this suggests Stephen was right in > suspecting the mirrors shut out old connections from old clients... Ack. I think s

Bug#467298: updating etch -> volatile helps

Hi, we've had problems very similar to those described above, with freshclam basically unable to download updates from anywhere, and clamd eventually dying because of this. I just updated to volatile (0.92.1...), and all remaining updates were downloaded like a breeze! I think this suggests Steph