-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/20/2010 10:26 AM, Matt Domsch wrote: > On Tue, Oct 19, 2010 at 02:25:53PM -0400, Deaderick, David (EIE) wrote: >> Has anyone noticed the inconsistency in checksums in >> linux.dell.com/repo/hardware/latest for >> megaraid_sas-v00.00.04.29-1.noarch.rpm? >> >> >> >> All files have the same size, header, etc. but there are two different >> sets of checksums. >> >> >> >> md5sum for a few selected files: >> >> >> >> d4eb4f1abc01f77ca67db6cf7f3f88d8 >> per610/rh50_64/sas_raid/r269100/megaraid_sas-v00.00.04.29-1.noarch.rpm >> >> d4eb4f1abc01f77ca67db6cf7f3f88d8 >> per710/rh50_64/sas_raid/r269100/megaraid_sas-v00.00.04.29-1.noarch.rpm >> >> d4eb4f1abc01f77ca67db6cf7f3f88d8 >> per810/rh50_64/sas_raid/r269100/megaraid_sas-v00.00.04.29-1.noarch.rpm >> >> c6b74b642ecfd11b7b0fce3f8fe7291b >> per900/rh50_64/sas_raid/r269097/megaraid_sas-v00.00.04.29-1.noarch.rpm >> >> >> >> It appears there are two different copies of the same file. One has about >> 80 hard links and the other has about 118 hard links. >> >> >> >> dell-satellite-sync fails the first time it tries to rhnpush the same RPM >> with a different checksum. > > You do see 2 different Dell releases (file promotions), R269097 and > R269100, which target different sets of systems. That accounts for > the 80 vs 118 hardlinks. > > The files are slightly different. rpmdiff shows that the contents are > identical, but hexdump shows there are slight variations within the > RPM header. > > -SIGGPG: > 883f0305004c33a920e74433e25e3d77751102ad6d009c0a554f82697bfe0ffd97629a24ad9104edfe07df0099014e8ac25ff771810a25a890179ff4e72779d00e > +SIGGPG: > 883f0305004c33a920e74433e25e3d77751102ad6d00a08700df613e77d040dcc2db9cf09ea0dc45299de4009f57ecde37b8ef8f178b03e3b1ad289d889ff51400 > -DSAHEADER: > 883f0305004c33a920e74433e25e3d77751102db3b009c09cbc51dc476dad609a8f0ada480f57986e880b9009f7ea27dbd5bf824ae2aed865188c85ddc8772146f > +DSAHEADER: > 883f0305004c33a920e74433e25e3d77751102db3b009f4ad2752a960ed510718686d33b1fa9202427bac6009d111b5b8352fb49f13f5f2b64e3fd6e4d85d2602e > > Which looks like a slight difference in when the packages were GPG-signed, no > functional difference. > > Perhaps catching and ignoring the failure in dell-satellite-sync is > the right solution here, as changing the files in those releases, > which is what the hardware repo is based on, can't happen anymore.
I did notice this issue early on, which is why I had to add the - --rhel4-only and --rhel5-only options. The --force option causes dell-satellite-sync to pass that option to rhnpush (which is where the failure is happening), which should push any subsequent packages with similar headers and overwrite what is in Satellite. As long as the actual drivers are functionally the same as Matt suggests, this should work fine. Does this work for you David? Regards, Vinny -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJMvz5nAAoJEJ4G2V8NTLSjTcAH/i5hZhf9MjPQjHVAQyYYiK7s ocCJFYQiIubWhZGR7D/DeNKrZA9+0Ygaq9D/l8L8hhy/evFySirEIEkRTluAnRnK CU5bwziiOCw0fDG2AmBYQCYNGpwpxsLhYFAboMQW61dMKwdbtdoniKjRvTY/6b+j 4wxL4kn+gx8GssSAqy3uWzZ+9m4v0GabVQreBOzeHnHwUcyrKCzvkkw9SxIR+RkJ TsOy0cB19XD50X6dt3x45WrF1bikl2KUhPUETHsT1aVsvSP21Xn8Z8VCyMkpq7u3 ozAg+9uOl6NEUIwhbBRNujYBUYHnFAOB5XpA6Xs5xYAiW+C4hIoX9J2i5dWCnbw= =iDI4 -----END PGP SIGNATURE----- _______________________________________________ Linux-PowerEdge mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
