ke 18. elok. 2021 klo 9.29 Sebastian Andrzej Siewior (sebast...@breakpoint.cc) kirjoitti: > > On 2021-08-18 07:09:56 [+0300], Martin-Éric Racine wrote: > > I never recovered. I have no idea how often it happens. I just noticed > > prior to upgrading to Bullseye that syslog regularly reports this, and > > fled the bug accordingly. > > Could please , stop freshclam, wipe out your signatures/database, start > freshclam and check if it is better/working? > According to that link, that zero-signature thingy was a one time thing. > I've been looking at freshclam code but there appears to be no update. > If the problem persists I would have to check directly with upstream > what todo.
I purged all clamav packages and re-installed them from Bullseye (0.103.2+dfsg-2). Freshclam succeeded at fetching the initial database. Still, this is not the first time that freshclam gets stuck because of a problem with one of the database patches. Upstream really has to think of a smarter way for freshclam to recover from this. Martin-Éric _______________________________________________ Pkg-clamav-devel mailing list Pkg-clamav-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-clamav-devel
