On Thursday, November 13, 2014 13:25:34 Sebastian Andrzej Siewior wrote: > On 2014-11-13 01:16:25 [-0700], Jesse Molina wrote: > > Severity: grave > > I would downgrade it to important. Scott?
Serious due to incomplete depends. I don't recall the exact policy paragraph, but it's a fails to comply with policy issue. Debian supports partial upgrades, so it shouldn't be possible to get in this situation. > > 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? I don't have a better idea. We need to do something and that's the only approach I can think of that avoids having to manually set a minimum version. Scott K _______________________________________________ Pkg-clamav-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-clamav-devel
