Karanbir Singh wrote:
The reason why we carried it in 5.0 etc was since yum-updatesd didnt really do much. If there is anyway to make yum-updatesd run its updates at a specific time, that would completely remove the need / role for yum-cron. Which might be the best result allaround anyway.
In 5.2 the same rpm file was in os/i386, os/x86_64 and for some reason also extras/x86_64. The one in extras/x86_64 is still there in 5.3:
centos]$ find 5.2 5.3 -name 'yum-cron*'|xargs sha1sum b656b9602177e99379fd01f59fb5579e492a4ef7 5.2/os/x86_64/CentOS/yum-cron-0.6-1.el5.centos.noarch.rpm 857a69bfabecf553baa2bbb164dd31cf2cf85da5 5.2/os/SRPMS/yum-cron-0.6-1.el5.centos.src.rpm b656b9602177e99379fd01f59fb5579e492a4ef7 5.2/os/i386/CentOS/yum-cron-0.6-1.el5.centos.noarch.rpm b656b9602177e99379fd01f59fb5579e492a4ef7 5.2/extras/x86_64/RPMS/yum-cron-0.6-1.el5.centos.noarch.rpm b656b9602177e99379fd01f59fb5579e492a4ef7 5.3/extras/x86_64/RPMS/yum-cron-0.6-1.el5.centos.noarch.rpm
-- Pär Andersson National Supercomputer Centre, Sweden