Why does the md5sum from a binary installed with a custom RPM not match the md5sum of the file from the source RPM?
Updated -
If an RPM includes a file that is simply copied from the RPM package to some place on the filesystem, the installed file should have the same checksum and md5sum as the original file in the source RPM. However, in the case of binary files, the default behavior of rpmbuild
is to strip binaries. This results in the installed binary having a different md5sum than the original file.
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.