Idea: Plain $ dpkg --verify #with no arguments is great to find all the problems on the system. However then one needs dlocate etc. to find out the package which the problem files belong to. So there should be a way to get it to tell us at the same time.
I have an other related probelm
'dpkg --verify' gives me:
"dpkg: error: control file 'md5sums' missing value separator"
But doesn't tell me *which* package has a problem.
I have to do this to locate this package:
for a in $(dpkg-query --show --showformat '${binary:Package}\n');
do dpkg --verify $a || echo $a;
done
By the way it's 'gootool', an unofficial package you may find here:
http://goofans.com/download/utility/gootool
The md5 seems fine; but this is an other problem.
Alexandre Detiste
Hi! They are only peripherally related. The problem in the original bug report cannot be fixed w/o adding another output format, as the curent one (rpm) is defined and does not include the package name. Ah, yeah, fixed this now for 1.18.x. It seems it's not using two spaces to separate the hash from the filename. So that seems like a manually built md5sums file. Thanks, Guillem