Over the past several days it seems like yum is not doing any updates. I see postings on the list of updates, and my PC at the office seems to be grabbing the later versions, but not at home. For example mlocate-0.14-0.fc5.1 is out. My installed version is mlocate-0.12-1.2. But when I do a yum update, it says no updates (same applies to the recent kernel release, it's not picking that up). I even went so far as to do a yum remove of mlocate and then a yum install of it and sure enough it still grabbed the -0.12-1.2 version rather than the latest one. I have not been messing with the .repos so I can't understand why it has stopped updating. Any suggestions?
Jacques B.
On 3/30/06, Jacques B. jjrboucher@gmail.com wrote:
Over the past several days it seems like yum is not doing any updates. I see postings on the list of updates, and my PC at the office seems to be grabbing the later versions, but not at home. For example mlocate-0.14-0.fc5.1 is out. My installed version is mlocate-0.12-1.2. But when I do a yum update, it says no updates (same applies to the recent kernel release, it's not picking that up). I even went so far as to do a yum remove of mlocate and then a yum install of it and sure enough it still grabbed the -0.12-1.2 version rather than the latest one. I have not been messing with the .repos so I can't understand why it has stopped updating. Any suggestions?
Jacques B.
Have you tried "yum clean all" to clear out the cache, header, etc.?
On 3/30/06, Jacques B. jjrboucher@gmail.com wrote:
Over the past several days it seems like yum is not doing any updates. I see postings on the list of updates, and my PC at the office seems to be grabbing the later versions, but not at home. For example mlocate-0.14-0.fc5.1 is out. My installed version is mlocate-0.12-1.2. But when I do a yum update, it says no updates (same applies to the recent kernel release, it's not picking that up). I even went so far as to do a yum remove of mlocate and then a yum install of it and sure enough it still grabbed the -0.12-1.2 version rather than the latest one. I have not been messing with the .repos so I can't understand why it has stopped updating. Any suggestions?
This very thing happened to me last night, but tonight a yum update works fine. When I installed FC5 last weekend, I modified my repo files to pull from a half dozen repos geographically near me. I just figured last night that the repos I use hadn't yet seen the updated packages.
On 3/30/06, J. K. Cliburn jcliburn@gmail.com wrote:
On 3/30/06, Jacques B. jjrboucher@gmail.com wrote:
Over the past several days it seems like yum is not doing any updates. I see postings on the list of updates, and my PC at the office seems to be grabbing the later versions, but not at home. For example mlocate-0.14-0.fc5.1 is out. My installed version is mlocate-0.12-1.2. But when I do a yum update, it says no updates (same applies to the recent kernel release, it's not picking that up). I even went so far as to do a yum remove of mlocate and then a yum install of it and sure enough it still grabbed the -0.12-1.2 version rather than the latest one. I have not been messing with the .repos so I can't understand why it has stopped updating. Any suggestions?
Strange, but now it's working. Didn't do the yum clean all (or yum clean packages). I do run that once in a while, but it doesn't appear to be necessary (at least never has been). I'm wondering if somehow things are setup to regulate the number of systems updating by staggering updates. I can't imagine as they would have to selectively chose to disadvantage some people by delaying their patching. Probably what may have been happening is that a maximum number of connections to the repos was being reached. I was getting a single update here and there, but not complete list of updates. Might that have been the problem?
At least I now know it's not the configuration of my system. That was my main concern as that is the only thing I have direct control over correcting.
Thanks,
Jacques B.
On Thu, 30 Mar 2006, Jacques B. wrote:
Over the past several days it seems like yum is not doing any updates. I see postings on the list of updates, and my PC at the office seems to be grabbing the later versions, but not at home. For example mlocate-0.14-0.fc5.1 is out. My installed version is mlocate-0.12-1.2. But when I do a yum update, it says no updates (same applies to the recent kernel release, it's not picking that up). I even went so far as to do a yum remove of mlocate and then a yum install of it and sure enough it still grabbed the -0.12-1.2 version rather than the latest one. I have not been messing with the .repos so I can't understand why it has stopped updating. Any suggestions?
Try "yum clean all" and see if that fixes it. If not, try removing yum-changelog. (That one gave me some weird problems similar to what you describe.)
alan alan@clueserver.org wrote: Try "yum clean all" and see if that fixes it. If not, try removing yum-changelog. (That one gave me some weird problems similar to what you describe.) huh, I can't slocate yum-changelog but I am seeing some yum files with .rpmnew and .rpmorig. I assume rpmnew = FC5 and the intact file is the FC4? When rpm does over write a config file .rpmorig is produced and the current config file would be FC5? Weird, I had read that the new yum behavior was to erase the rpm packages upon completion, but I found 300+ rpm files still there. Something amiss between .rpmnew and .rpmorig? I did do the yum upgrade path and darn near have a working machine again... I'm happy. Ric
================================================ My father, Victor Moore (Vic) used to say: "There are two Great Sins in the world... ...the Sin of Ignorance, and ...the Sin of Stupidity. Only the former may be overcome." R.I.P. Dad.
Linux user# 44256 Sign up at: http://counter.li.org/ ================================================ --------------------------------- Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls. Great rates starting at 1¢/min.
On 4/2/06, Rickey Moore wayward4now@yahoo.com wrote:
alan alan@clueserver.org wrote: Try "yum clean all" and see if that fixes it. If not, try removing yum-changelog. (That one gave me some weird problems similar to what you describe.) huh, I can't slocate yum-changelog but I am seeing some yum files with .rpmnew and .rpmorig. I assume rpmnew = FC5 and the intact file is the FC4? When rpm does over write a config file .rpmorig is produced and the current config file would be FC5? Weird, I had read that the new yum behavior was to erase the rpm packages upon completion, but I found 300+ rpm files still there. Something amiss between .rpmnew and .rpmorig? I did do the yum upgrade path and darn near have a working machine again... I'm happy. Ric
You did not say that your installation was an upgrade from FC4. You should examine at all .repo files. Make sure that they point to FC5 and not FC4. While you are at it also examine your rpm database to see if you have duplicate packages, i.e. FC4 packages installed along with the FC5 package.
Rickey Moore wrote:
alan alan@clueserver.org wrote: Try "yum clean all" and see if that fixes it. If not, try removing yum-changelog. (That one gave me some weird problems similar to what you describe.) huh, I can't slocate yum-changelog but I am seeing some yum files with .rpmnew and .rpmorig. I assume rpmnew = FC5 and the intact file is the FC4? When rpm does over write a config file .rpmorig is produced and the current config file would be FC5? Weird, I had read that the new yum behavior was to erase the rpm packages upon completion, but I found 300+ rpm files still there. Something amiss between .rpmnew and .rpmorig? I did do the yum upgrade path and darn near have a working machine again... I'm happy. Ric
You get .rpmnew/.rpmsave files when (a) rpm updates a package, AND (b) a configuration file has changed beteeen the previous and current package releases, AND (c) you made a change to that configuration file.
Whether the old one is renamed to .rpmsave or the new one is installed as .rpmnew depends on how the packager has decided to handle configuration file changes.
Either way, you need to find all of these files and decide for yourself how you want to handle them, typically by merging any manual changes you made in the original configuration files into the "new" configuration files.
You can have these issues whenever packages are upgraded, but of course you gets *lots* of them when you do a distribution upgrade.
Paul.
-
Alan -
J. K. Cliburn -
Jacques B. -
Kam Leo -
Paul Howarth -
Rickey Moore