On one notebook (so far), I have not picked up the new kernel: kernel-2.6.18-92.1.22.el5.i686.rpm
I have gotten it on some notebooks.
So far the only difference I can see between the systems that MIGHT matter is those that got the update were new installs and had not reached 3 installed kernels. The one that failed already had 3 kernels in /boot. But I seem to recall this was about how many to keep in /boot, not when to stop receiving them....
Robert Moskowitz wrote on Wed, 17 Dec 2008 08:42:01 -0500:
kernel-2.6.18-92.1.22.el5.i686.rpm
This kernel hasn't been even announced yet, so what's the problem?
So far the only difference
the difference is the mirrors they use
I think you should now that :-)
Kai
Kai Schaetzl wrote:
kernel-2.6.18-92.1.22.el5.i686.rpm
This kernel hasn't been even announced yet, so what's the problem?
the kernel was announced about 15 hrs back, where are you looking and how are you failing to notice ?
Karanbir Singh wrote:
Kai Schaetzl wrote:
kernel-2.6.18-92.1.22.el5.i686.rpm
This kernel hasn't been even announced yet, so what's the problem?
the kernel was announced about 15 hrs back, where are you looking and how are you failing to notice ?
I do an rsync to my local repo. I had looked at the logs just to see what came over, and saw the new kernel. Of course I can't see what the xml is saying is currently available...
So then I ran yum update on some of my systems. Some picked up the new kernel one did not (so far).
Robert Moskowitz wrote:
I do an rsync to my local repo. I had looked at the logs just to see what came over, and saw the new kernel. Of course I can't see what the xml is saying is currently available...
So then I ran yum update on some of my systems. Some picked up the new kernel one did not (so far).
you seem to run into this problem often, it might be worth actually looking to find the part of your process that is broken and fixing it.
within the CentOS setup, metadata for a package is only created once and only at one place and is done within a few seconds of the email being sent out announcing the package.
Karanbir Singh wrote:
Robert Moskowitz wrote:
I do an rsync to my local repo. I had looked at the logs just to see what came over, and saw the new kernel. Of course I can't see what the xml is saying is currently available...
So then I ran yum update on some of my systems. Some picked up the new kernel one did not (so far).
you seem to run into this problem often, it might be worth actually looking to find the part of your process that is broken and fixing it.
within the CentOS setup, metadata for a package is only created once and only at one place and is done within a few seconds of the email being sent out announcing the package.
This really has me buffaloed.
I suppose I can run a clean and see what happens, but the systems that got the new kernel, got it, and how do you take it back to try again?
And the system that that did not get, well, I suppose a clean might see if it gets it now. Stay tuned.
Robert Moskowitz wrote:
Karanbir Singh wrote:
Robert Moskowitz wrote:
I do an rsync to my local repo. I had looked at the logs just to see what came over, and saw the new kernel. Of course I can't see what the xml is saying is currently available...
So then I ran yum update on some of my systems. Some picked up the new kernel one did not (so far).
you seem to run into this problem often, it might be worth actually looking to find the part of your process that is broken and fixing it.
within the CentOS setup, metadata for a package is only created once and only at one place and is done within a few seconds of the email being sent out announcing the package.
This really has me buffaloed.
I suppose I can run a clean and see what happens, but the systems that got the new kernel, got it, and how do you take it back to try again?
And the system that that did not get, well, I suppose a clean might see if it gets it now. Stay tuned.
Yes a yum clean all on the notebook that did not get the kernel is now not only getting the kernel but also: cups and enscript.
So I had some problems here. The metadata or dbcache? This is my notebook, and when I am away at conferences, I change my source of update and base to the mirrors, and when I get back I change back to my local repo. That might be why it got lost? I guess I should add a 'yum clean all' whenever I make these changes....
But I guess you did not announce the kernel, but anyone pulling the updates locally would be getting them?
Robert Moskowitz wrote:
But I guess you did not announce the kernel, but anyone pulling the updates locally would be getting them?
How did you work out that the kernel was not announced ? Re read my last email to you on this subject.
Karanbir Singh wrote:
Robert Moskowitz wrote:
But I guess you did not announce the kernel, but anyone pulling the updates locally would be getting them?
How did you work out that the kernel was not announced ? Re read my last email to you on this subject.
From Kai's comment and not reading your message carefully.
Sorry about that.
Robert Moskowitz wrote:
I do an rsync to my local repo. I had looked at the logs just to see what came over, and saw the new kernel. Of course I can't see what the xml is saying is currently available...
So then I ran yum update on some of my systems. Some picked up the new kernel one did not (so far).
If you're running 'yum update' against your local mirrored repo, try running 'yum clean metadata' on systems that aren't picking up updates that you know exist (i.e, are picked up on other systems), and then retry 'yum update'.
Karanbir Singh wrote on Wed, 17 Dec 2008 15:53:00 +0000:
the kernel was announced about 15 hrs back,
last digest I got is 24 hours old, Vol. 46, Issue 7, no kernel in it.
Kai
Kai Schaetzl wrote:
Karanbir Singh wrote on Wed, 17 Dec 2008 15:53:00 +0000:
the kernel was announced about 15 hrs back,
last digest I got is 24 hours old, Vol. 46, Issue 7, no kernel in it.
You might want to investigate a bit on how list digests work :D
Karanbir Singh wrote on Wed, 17 Dec 2008 17:56:34 +0000:
You might want to investigate a bit on how list digests work
I know how they work ;-) I was under the impression that announce is digest-only as I don't have any "normal" announcements. Apparently, this isn't the case.
Kai
on 12-17-2008 9:31 AM Kai Schaetzl spake the following:
Karanbir Singh wrote on Wed, 17 Dec 2008 15:53:00 +0000:
the kernel was announced about 15 hrs back,
last digest I got is 24 hours old, Vol. 46, Issue 7, no kernel in it.
Kai
When I went to school, 15 was less than 24, so that is why it isn't in the digest.
Join centos-announce. The traffic is light.
-
Kai Schaetzl -
Karanbir Singh -
Ned Slider -
Robert Moskowitz -
Scott Silva