Missing debsums cause bad warnings

[naapuri]

If a package doesn't have debsums, the bcfg2 client incorrectly says that "Bad files are: <packagename>".

...
> /usr/bin/debsums -as libcap1
> /usr/bin/debsums -as libcomerr2
> /usr/bin/debsums -as libconsole
> /usr/bin/debsums -as libdb4.2
< debsums: no md5sums for libdb4.2
Package libdb4.2 failed validation. Bad files are:
 libdb4.2
> /usr/bin/debsums -as libdb4.3
< debsums: no md5sums for libdb4.3
Package libdb4.3 failed validation. Bad files are:
 libdb4.3
> /usr/bin/debsums -as libdb4.4
< debsums: no md5sums for libdb4.4
Package libdb4.4 failed validation. Bad files are:
 libdb4.4
> /usr/bin/debsums -as libdevmapper1.02
> /usr/bin/debsums -as libedit2
> /usr/bin/debsums -as libgcc1
> /usr/bin/debsums -as libgcrypt11
...

(Re-installing these packages will help, since debsums installs a post-installation script that calculates md5sums if needed.)

[desai]

The warnings are fixed in [1e7086f009aeea0b749fa3ff24946438298f5943] (SVN r2540). I think that the packages should be reinstalled, since we can't verify the checksums.