Since we have introduced preferredChecksum property for Channel domain
object, taskomatic should be updated so that repomd generation
reflects that property.
Initial support, which covers RPM checksum selection based on the channel preference is submitted in 19e9648b9ce1f01af95b04c3abaddd3c43eb4337.
TODO: the metadata files themselves still use hardcoded sha1 checksum
method to compute their checksums. The channel preference should apply
here as well.
The rest of functionality implemented in 33f92350022b76a9ed4fc90e9be798cab8f21909.
So for testing dhughes and I were attempting to downloading dmidecode from rhel-i386-server-5.
1) cleared the repomd
2) regenerated it
3) attempted to yum install dmidecode
This failed. Upon investigation it appears that:
1) The newly generated repomd files have the sha-256 sum for the file
2) The database appears to have sha1 set as the default for that channel
3) RHEL <= 5 yum clients will never understand anything other than md5, so either way it should have failed.
It looks to me that there's two problems here:
1) It should be set to generate md5
2) sha256 should not be generated if the type is set to sha1
With the recent work to distinguish between metadata and RPM preferred checksum methods, new attribute has been added to Channel domain object: preferredRpmChecksum. This property is now being consulted to generate the per-package checksums in repo metadata files.
e75e8272ff5719c2001059778f8e93d9a14c2998 is now available on webdev.
Verified in dev on 10/13/09