[Spacewalk-list] diffirence between yum and up2date

[Justin Sherrill]

Michiel van Es wrote:
> Hello,
> 
> I found out that some machines (CentOS 4 machines) are not seeing
> updates through yum but up2date does.
> What is the diffirence between the 2? Both use Spacewalk right?
> 
> 
> An example:
> 
> [root at bcmw01p ~]# yum -y update
> Setting up Update Process
> Setting up repositories
> spacewalk-client-tools    100% |=========================| 1.9 kB    00:00
> Reading repository metadata in from local files
> No Packages marked for Update/Obsoletion
> [root at bcmw01p ~]# up2date -fu
> 
> Fetching Obsoletes list for channel: centos4...
> 
> Fetching Obsoletes list for channel: centos4-Base...
> 
> Fetching Obsoletes list for channel: centos4-Updates...
> 
> Fetching Obsoletes list for channel: centos4-extras...
> 
> Fetching Obsoletes list for channel: centos4-addons...
> 
> Name                                    Version        Rel
> ----------------------------------------------------------
> OpenIPMI                                1.4.14         1.4E.25
>  i386
> OpenIPMI-libs                           1.4.14         1.4E.25
>  i386
> audit                                   1.0.16         4.el4
>  i386
> audit-libs                              1.0.16         4.el4
>  i386
> autofs                                  4.1.3          238
>  i386
> bash                                    3.0            21.el4
>  i386
> bluez-utils                             2.10           5.el4
>  i386
> centos-release                          4              8
>  i386
> comps                                   4.8CENTOS      0.20090804
>  i386
> coreutils                               5.2.1          36.el4.centos
>  i386
> cpp                                     3.4.6          11
>  i386
> crash                                   4.0            5.0.0.2
>  i386
> curl                                    7.12.1         11.1.el4_8.1
>  i386
> curl-devel                              7.12.1         11.1.el4_8.1
>  i386
> dapl                                    2.0.15         1.el4
>  i386
> diskdumputils                           1.4.1          7
>  i386
> e2fsprogs                               1.35           12.24.el4
>  i386
> e2fsprogs-devel                         1.35           12.24.el4
>  i386
> file                                    4.10           8.el4
>  i386
> freetype                                2.1.9          10.el4.7
>  i386
> gcc                                     3.4.6          11
>  i386
> glibc                                   2.3.4          2.43
>  i686
> glibc-common                            2.3.4          2.43
>  i386
> glibc-devel                             2.3.4          2.43
>  i386
> glibc-headers                           2.3.4          2.43
>  i386
> grep                                    2.5.1          32.4.el4
>  i386
> hotplug                                 2004_04_01     7.10
>  i386
> httpd                                   2.0.52         41.ent.4.centos4
>  i386
> httpd-devel                             2.0.52         41.ent.4.centos4
>  i386
> httpd-suexec                            2.0.52         41.ent.4.centos4
>  i386
> hwdata                                  0.146.33.EL    17
>  noarch
> initscripts                             7.93.34        1.centos4
>  i386
> iptables                                1.2.11         3.2.RHEL4
>  i386
> iputils                                 20020927       22.el4
>  i386
> isdn4k-utils                            3.2            19.el4
>  i386
> jwhois                                  3.2.2          15.el4
>  i386
> kernel                                  2.6.9          89.0.11.EL
>  i686
> kernel-devel                            2.6.9          89.0.11.EL
>  i686
> kernel-smp                              2.6.9          89.0.11.EL
>  i686
> kernel-utils                            2.4            18.el4
>  i386
> 
> 
> Kind regards,
> 
> Michiel
> 

So up2date talks to the server and gets a real time list of available
packages.  It also does some dependency solving on the server side.

yum however simply downloads the yum cache on the server that may lag
behind what is actually in the channel or may be out of date (if
something isn't working correctly).

You might wanna try deleting /var/cache/rhn/repodata/CHANNEL_LABEL

then run 'yum update' on a client.  It will error out, but should
initiate a yum cache rebuild.  If you look in that directory after a few
minutes you'll see files in there being created.

If you don't, then something is wrong.  Make sure taskomatic is running.

-Justin


------------------------------------------------------------------------

_______________________________________________
Spacewalk-list mailing list
Spacewalk-list at redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list


-- 
Justin Sherrill, RHCA          1801 Varsity Drive.
Software Engineer                Raleigh, NC 27603
Red Hat, Inc.