Pradeep Kilambi wrote:
Miroslav Suchý wrote:
I do not see any other options. And you?
My personal preferences are (from best to worse): 2, 3, 1, 4.
Please share your opinions about this.
Dint we already come to a conclusion on this :). I spoke to James
Then I must missed it. :)
antill on the options and how yum handles. Older yum clients will not
be able to handle sha256 and newer clients will be able to handle both.
Having python-haslib into el5 from epel is not our decision. Yes that
will make our life easy ofcourse. python-hashlib dependency if any has
to be on yum not yum-rhn-plugin. We don't deal with checksums in our
plugin. Its all yum code that depends on it. So adding python-hashlib to
plugin is wrong thing to do. It should be yum and we from
satellite/spacewalk dont maintain it. So yea we can file a request for
yum to include it. But I doubt it as its gonna be supported from 5.5
anyway. Also older u releases will have to be patched which is not
possible. So if someone is using 5u3 or older they cannot use
python-hashlib. So we have to account for that. We cannot blindly
generate everything with sha256. Now since the new clients handle both
types
* if its newer version of client we will default to sha256.
* else if its older version default to sha1/md5
* else if its custom default to sha1/md5.
So currently thats the approach I was gonna take unless we can convince
people to include python-hashlib into el5.4 or older.
Do I understood it correctly that we will go through 4 option?:
: 4. Genereate two repos and based on heuristic serve repo with MD5/SHA1
: to EL5 clients and serve repo with SHA256 to F11 clients.
--
Miroslav Suchy
Red Hat Satellite Engineering
_______________________________________________
Spacewalk-devel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-devel
