I ran "yum upgrade" early yesterday from a remote ssh login, but upon looking at the set of packages I decided to wait until I could sit at the console to reboot. So I declined to proceed with the upgrade when prompted.
Later when I ran "yum ugrade" again, it found no packages to update. After some poking around checking the mirrors, running "yum clean headers", etc., I finally tried "yum clean all" and thereafter "yum ugrade" worked flawlessly.
I've never seen this happen with "yum update", so I don't know why it would be different with "upgrade", but there you are.
On Thu, 2006-08-31 at 08:36 -0700, Bart Schaefer wrote:
I ran "yum upgrade" early yesterday from a remote ssh login, but upon looking at the set of packages I decided to wait until I could sit at the console to reboot. So I declined to proceed with the upgrade when prompted.
Later when I ran "yum ugrade" again, it found no packages to update. After some poking around checking the mirrors, running "yum clean headers", etc., I finally tried "yum clean all" and thereafter "yum ugrade" worked flawlessly.
I've never seen this happen with "yum update", so I don't know why it would be different with "upgrade", but there you are. _______________________________________________
Yum has a cache for a period of time, maybe that came into play and cleaning the metadata made everything better?
On 8/31/06, Johnny Hughes mailing-lists@hughesjr.com wrote:
Yum has a cache for a period of time, maybe that came into play and cleaning the metadata made everything better?
I presume that's what it is, but I've sometimes answered "no" to the same prompt from "yum update" and then successfully done the update a few minutes later; so I found it curious that even after several hours I couldn't "yum upgrade" again without cleaning the caches.
-
Bart Schaefer -
Johnny Hughes