• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 427
  • Last Modified:

Updating GNOME in Red Hat V6.0 via RPM to lastest stable release

I want to upgrade GNOME to the current stable, released version, as I understand that the GNOME desktop and associated applications were extremely buggy as shipped/installed with the Red Hat V6.0 distro.

My Questions:

1) What GNOME RPMS do I need to download, and from where, to accomplish an update to the latest stable GNOME releases for i386?

2) What is the best RPM process/procedure for accomplishing a GNOME update, with respect to satisfying dependancies?

3) Do I use the RPM Freshen or Update feature of RPM? What is the exact syntax that will accomplish a GNOME update?

Thanks all for you answers and comments, as always :-)
  • 3
  • 2
1 Solution
JimIntrigliaAuthor Commented:
OK... doing some hoemwork and making some progress I think. Anybody add to what I have learned or confirm my beliefs:

1) I believe the latest stable GNOME release for Red hat i386 /base is located at:

Do I also need to download /Devel and update the old /devel packages as well?  What's the difference between the /base and the /devel packages?

2&3) According to the online Red hat RPM manual at:

"RPM's freshen option works well with single packages or with a group of packages. It's especially handy if you've just downloaded a large number of different packages, and you only want to upgrade those packages that are already installed on your system. Using the freshen option means that you won't have to pick through the downloaded packages, deleting any unwanted ones before using RPM."

"In this case, you can simply issue the following command:

# rpm -Fvh *.rpm

RPM will automatically upgrade only those packages that have already been installed."

OK, so I download all of the /base rpm packages into the same /temp directory and run the rpm command line listed above. That should update all GNOME libraries to the current release satifying file dependancies along the way?

Since there has been a number of releases of GNOME since RHV6.0 (Gnome-core was at 1.0.4-34 for RHV6.0), should I rpm -Fvh using the Gnome-core-1.0.53 (latest stable RH i386) or should I increment gradually through stable releases since 1.0.4-34 until I reach 1.0.53?

Concerned about missing previous files not included in the current stable Gnome-core stable release (hit this situation with bzip2 package update via RPM).
To see what GNOME RPMS you need, do the following:

Mount the install cdrom. Then type:

    # cd /mnt/cdrom/RedHat/base

Look in the comps file and search for GNOME. The list there is all the              packages that the GNOME enviroment likes to have installed. List down the the names.

    # cd /mnt/cdrom/RedHat/RPMS

Copy the RPMs to a temporary directory.

cd to the temp dir, then do a

    # rpm -Fvh *rpm

That will get them installed. You might have to run the command a couple times to take care of dependencies.
JimIntrigliaAuthor Commented:
Adjusted points to 150
JimIntrigliaAuthor Commented:
Hi bernardh,

OK.. I follow what you are saying, but rather than copy the RPM's off my RH V6.0 CD-ROM (to a temporary dir), I believe I need to download the lastest stable release of GNOME RPM's V1.0.53 (from ftp://ftp.gnome.org/pub/GNOME/stable/releases/gnome-1.0.53/redhat/i386/Base/)
and then run the RPM -Freshen option. This should update GNome on my PC to the latest version.

If I used the RPM's off the RH CD-ROM, -RPM -freshen would have no effect, as what I have presently installed would match what is on the RH6.0 CD-ROM, which is are outdated Gnome software release.

That make sense?

or you can check thee mirror sites for updates, http://www.redhat.com/download/mirror.html
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now