Note that the problem isn't the md5sums, the problem is that the owners of important files are incorrect:
Lintian check results for .../network-scan-linux-glibc2-x86_64.deb: E: lexmark-network-scan: control-file-has-bad-owner md5sums build/build != root/root E: lexmark-network-scan: control-file-has-bad-owner postinst build/build != root/root E: lexmark-network-scan: control-file-has-bad-owner preinst build/build != root/root E: lexmark-network-scan: control-file-has-bad-owner prerm build/build != root/root
Note that the problem isn't the md5sums, the problem is that the owners of important files are incorrect:
Lintian check results for .../network- scan-linux- glibc2- x86_64. deb: network- scan: control- file-has- bad-owner md5sums build/build != root/root network- scan: control- file-has- bad-owner postinst build/build != root/root network- scan: control- file-has- bad-owner preinst build/build != root/root network- scan: control- file-has- bad-owner prerm build/build != root/root
E: lexmark-
E: lexmark-
E: lexmark-
E: lexmark-