hi, in 5.2 there is a yum-cron in the os dir, but there is a yum-cron only in extras/x86_64 too (not in i386). at the same time in 5.3 there is no yum-cron in the os dir, but there is yum-cron only in extras/x86_64 too (not in i386). at the same time there is a yum-cron in epel-5 too. so imho it'd be useful to clean up this situation.
Farkas Levente wrote:
hi, in 5.2 there is a yum-cron in the os dir, but there is a yum-cron only in extras/x86_64 too (not in i386). at the same time in 5.3 there is no yum-cron in the os dir, but there is yum-cron only in extras/x86_64 too (not in i386). at the same time there is a yum-cron in epel-5 too. so imho it'd be useful to clean up this situation.
We dont really have much interest here as to what EPEL or any other third party repo is doing - you will need to chase it up with them.
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.
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
On Fri, 2009-04-17 at 14:19 +0100, 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.
You can run newer yum-updatesd's with:
yum-updatesd --oneshot
...from cron. etc. Making it compatible with yum-cron isn't easy though (mainly due to configuration differences).
Karanbir Singh wrote:
Farkas Levente wrote:
hi, in 5.2 there is a yum-cron in the os dir, but there is a yum-cron only in extras/x86_64 too (not in i386). at the same time in 5.3 there is no yum-cron in the os dir, but there is yum-cron only in extras/x86_64 too (not in i386). at the same time there is a yum-cron in epel-5 too. so imho it'd be useful to clean up this situation.
We dont really have much interest here as to what EPEL or any other third party repo is doing - you will need to chase it up with them.
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.
may be i was not specific enough, so then the questions are: - in 5.2 why yum-cron in extras/x86_64 if it's in os already? - in 5.3 why yum-cron only in extras/x86_64 but not in extras/i386? imho both the above is a bug.
Farkas Levente wrote:
Karanbir Singh wrote:
Farkas Levente wrote:
hi, in 5.2 there is a yum-cron in the os dir, but there is a yum-cron only in extras/x86_64 too (not in i386). at the same time in 5.3 there is no yum-cron in the os dir, but there is yum-cron only in extras/x86_64 too (not in i386). at the same time there is a yum-cron in epel-5 too. so imho it'd be useful to clean up this situation.
We dont really have much interest here as to what EPEL or any other third party repo is doing - you will need to chase it up with them.
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.
may be i was not specific enough, so then the questions are:
- in 5.2 why yum-cron in extras/x86_64 if it's in os already?
- in 5.3 why yum-cron only in extras/x86_64 but not in extras/i386?
imho both the above is a bug.
and one more: - if yum-cron was removed from upstream OS do centos would like to include it in extras?
-
Farkas Levente -
James Antill -
Karanbir Singh -
Pär Andersson