/var/lib/dpkg/info/$package.md5sums
Hi!
While tracking down an incident in our network, I used 'debsums' to
check what files have been modified on our still Sarge boxes and on
our Etch boxes, too.
I noticed that for some essential packages there are no md5sums
information in /var/lib/dpkg/info/:
debsums: no md5sums for bzip2
debsums: no md5sums for console-data
debsums: no md5sums for debian-archive-keyring
debsums: no md5sums for gnupg
debsums: no md5sums for gpgv
debsums: no md5sums for initscripts
debsums: no md5sums for iproute
debsums: no md5sums for klogd
debsums: no md5sums for libbz2-1.0
debsums: no md5sums for module-init-tools
debsums: no md5sums for modutils
debsums: no md5sums for mount
debsums: no md5sums for netbase
debsums: no md5sums for openbsd-inetd
debsums: no md5sums for sysv-rc
debsums: no md5sums for sysvinit
debsums: no md5sums for sysvinit-utils
debsums: no md5sums for udev
debsums: no md5sums for util-linux
Simple question: Why are there no md5sums available?
Shouldn't they exist in any package?
If not, why not?
Ciao
Max
--
Follow the white penguin.
Reply to: