Please direct me to the "right" group, if this is the wrong one...

Can someone explain the following behavior???

[root@modis ~]# yum check-update
Setting up repositories
updates-released 100% |=========================| 951 B 00:00
extras 100% |=========================| 1.1 kB 00:00
base 100% |=========================| 1.1 kB 00:00
Reading repository metadata in from local files
primary.xml.gz 100% |=========================| 347 kB 00:14
updates-re: ################################################## 965/965
Added 27 new packages, deleted 28 old in 3.43 seconds

cpuspeed.i386 1:1.2.1-1.23_FC4 updates-released
gnome-utils.i386 1:2.10.0-4 updates-released
microcode_ctl.i386 1:1.12-1.24_FC4 updates-released
ruby.i386 1.8.3-2.fc4 updates-released
ruby-debuginfo.i386 1.8.3-2.fc4 updates-released
ruby-devel.i386 1.8.3-2.fc4 updates-released
ruby-docs.i386 1.8.3-2.fc4 updates-released
ruby-libs.i386 1.8.3-2.fc4 updates-released
ruby-mode.i386 1.8.3-2.fc4 updates-released
ruby-tcltk.i386 1.8.3-2.fc4 updates-released
termcap.noarch 1:5.4-7fc4 updates-released
[root@modis ~]# yum update
Setting up Update Process
Setting up repositories
updates-released 100% |=========================| 951 B 00:00
extras 100% |=========================| 1.1 kB 00:00
base 100% |=========================| 1.1 kB 00:00
Reading repository metadata in from local files
primary.xml.gz 100% |=========================| 333 kB 00:13
updates-re: ################################################## 966/966
Added 28 new packages, deleted 27 old in 2.90 seconds
No Packages marked for Update/Obsoletion
[root@modis ~]#

Thanks!
Bruce

--
+-------------------+---------------------------------------------------+
Bruce Bowler | Nothing comes from nothing, Nothing ever will -
1.207.633.9600 | Rodgers&Hammerstein
bbowler@bigelow.org |
+-------------------+---------------------------------------------------+

Bruce Bowler <bbowler@bigelow.org> writes:

> Please direct me to the "right" group, if this is the wrong one...
> Can someone explain the following behavior???

> [root@modis ~]# yum check-update
>cpuspeed.i386 1:1.2.1-1.23_FC4 updates-released
> ...
> Added 27 new packages, deleted 28 old in 3.43 seconds
> ...
> [root@modis ~]# yum update
> ...
> Added 28 new packages, deleted 27 old in 2.90 seconds
> No Packages marked for Update/Obsoletion

You probably have more that one place where you get updates-released from
(check your yum.repos.d/files) and they're not fully synced.

The first one has 27 packages newer than your current installation. The
second has none (and updating from there deleted the info on those 27
packages).

When all the sites you update from are in sync you'll get those packages.
Or you can try one by one and see which one has the latest.

-- HASM

"HASM" <not_really@comcast.net> wrote in message
news:m3wtkugvnr.fsf@127.0.0.1...
> Bruce Bowler <bbowler@bigelow.org> writes:
>
>> Please direct me to the "right" group, if this is the wrong one...
>> Can someone explain the following behavior???
>
>> [root@modis ~]# yum check-update
>>cpuspeed.i386 1:1.2.1-1.23_FC4 updates-released
>> ...
>> Added 27 new packages, deleted 28 old in 3.43 seconds
>> ...
>> [root@modis ~]# yum update
>> ...
>> Added 28 new packages, deleted 27 old in 2.90 seconds
>> No Packages marked for Update/Obsoletion
>
> You probably have more that one place where you get updates-released from
> (check your yum.repos.d/files) and they're not fully synced.

That sounds exactly right. It's often helpful to go through the list of
mirrors yourself and find a really good local one, or if you're supporting
more than a few machines to create a local rsync-derived mirror of the
update site and use that for local installations. It really makes things
faster, especially if you have to update a lot of machines all at the same
time.