On 12/07/2013 09:07 AM, Mogens Kjaer wrote:
On 12/06/2013 12:49 PM, Lars Hecking wrote:
Something got mixed up somewhere. The first one (md5 20bb...) is from the x86_64 branch, both 6.4 and 6.5, and the second one (md5 d37f...) is from the i386 branch, also 6.4 and 6.5.
d37fe4404a7a5fdb27b29f9b5ed09c73 ./6.4/os/i386/Packages/python-slip-dbus-0.2.20-1.el6_2.noarch.rpm 20bb02e6f3b7b71e09dcaff7f3b0ca02 ./6.4/os/x86_64/Packages/python-slip-dbus-0.2.20-1.el6_2.noarch.rpm d37fe4404a7a5fdb27b29f9b5ed09c73 ./6.5/os/i386/Packages/python-slip-dbus-0.2.20-1.el6_2.noarch.rpm 20bb02e6f3b7b71e09dcaff7f3b0ca02 ./6.5/os/x86_64/Packages/python-slip-dbus-0.2.20-1.el6_2.noarch.rpm
Hm, am I the only mirror maintainer that runs hardlinkpy on the tree after each mirror?
Why are there different md5sum's on these files?
They are noarch rpms, so they should be identical in i386 and x86_64?
I get the following:
# md5sum `locate python-slip-dbus-0.2.20-1.el6_2.noarch.rpm` d37fe4404a7a5fdb27b29f9b5ed09c73 /var/ftp/pub/mirrors/centos/6.4/os/i386/Packages/python-slip-dbus-0.2.20-1.el6_2.noarch.rpm 20bb02e6f3b7b71e09dcaff7f3b0ca02 /var/ftp/pub/mirrors/centos/6.4/os/x86_64/Packages/python-slip-dbus-0.2.20-1.el6_2.noarch.rpm d37fe4404a7a5fdb27b29f9b5ed09c73 /var/ftp/pub/mirrors/centos/6.5/os/i386/Packages/python-slip-dbus-0.2.20-1.el6_2.noarch.rpm d37fe4404a7a5fdb27b29f9b5ed09c73 /var/ftp/pub/mirrors/centos/6.5/os/x86_64/Packages/python-slip-dbus-0.2.20-1.el6_2.noarch.rpm
and: # ls -li `locate python-slip-dbus-0.2.20-1.el6_2.noarch.rpm` 98845547 -rw-rw-r-- 3 mk 500 30844 Mar 26 2012 /var/ftp/pub/mirrors/centos/6.4/os/i386/Packages/python-slip-dbus-0.2.20-1.el6_2.noarch.rpm 98315857 -rw-rw-r-- 1 mk 500 30844 Mar 26 2012 /var/ftp/pub/mirrors/centos/6.4/os/x86_64/Packages/python-slip-dbus-0.2.20-1.el6_2.noarch.rpm 98845547 -rw-rw-r-- 3 mk 500 30844 Mar 26 2012 /var/ftp/pub/mirrors/centos/6.5/os/i386/Packages/python-slip-dbus-0.2.20-1.el6_2.noarch.rpm 98845547 -rw-rw-r-- 3 mk 500 30844 Mar 26 2012 /var/ftp/pub/mirrors/centos/6.5/os/x86_64/Packages/python-slip-dbus-0.2.20-1.el6_2.noarch.rpm
Mogens
They would not necessarily have the exact same md5sum just because they are noarch. The way mock compiles RPMs, it would be built on each builder separately. The possibility exists that something very minor can (and sometimes does) happen to make things not exact. I will analyze these an tell you the difference in an upcoming e-mail.
We have changed our policy and now we will use the same noarch file, from one of the arches, on both if it exist in the arches. That policy did indeed cause a change in the MD5SUM as they were different before. Again, I'll post in another e-mail what is different between the two, but this is as expected.
It should not happen any more moving forward though, as we will only ever release ONE noarch file in future, regardless of it they built slightly differently from the builders.
Thanks, Johnny Hughes