Sorry, I opened this bug when I was tired. My apologies for the lack of
detail.
I did a global upgrade, which is how I ended up in that situation.
libclamav6 was held back. Seems obvious that the package needed to be
upgraded but wasn't, but I was not thinking right at the time.
Seems like a simple oversight.
On 11/13/14 4:25, Sebastian Andrzej Siewior wrote:
On 2014-11-13 01:16:25 [-0700], Jesse Molina wrote:
Severity: grave
I would downgrade it to important. Scott?
Fails on start. I imagine this wasn't tested?
You imagine wrong. But this case in particular wasn't.
Setting up clamav-freshclam (0.98.5~rc1+dfsg-3) ...
[....] Starting ClamAV virus database updater: freshclamERROR: This tool
requires libclamav with functionality level 79 or higher (current f-level: 77)
failed!
This is a fresh install of clamav and clamav-freshclam after a dpkg purge.
Almost a complete purge:
ii clamav-base 0.98.5~rc1+dfsg-3
ii libclamav6 0.98.4+dfsg-2+b1
You have the old libclamav6 dangling around. If you do an "apt-get
upgrade" then it should be fixed.
We have depends on libclamav6 based on library functions / ABI. Now the
ABI remains unchanged but stops working. This was neither tested nor
expected.
I guess the simplest thing to do is to depend the whole clamav package
on the built version instead of versioned symbols like we now.
This check comes from check_flevel() and it is not exported so havp &
friends won't care about his.
Any comments?
Sebastian
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
