Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 345
  • Last Modified:

RPM Dependancy Problem: Gnome Update

I have Red Hat Linux V6.0 installed i386, and are in the process of updating the GNOME desktop to stable release V1.0.53. When I run rpm -Fvh *.rpm (freshen). I have a dependancy:

extace-1.1.14 is needed by gnome-media-1.0.51-1.

Problem is the earliest release of extace out there is extace-1.2.x.

Questions:
1) What do I need to do to resolve this dependancy
2) Where can I find this release of extace?

Concerns:
1) If I download the next earliest version available of extace (1.2.x), will rpm  realize a newer extace is available or is rpm just looking for a specifi filename?

2) If I install the latest extace package, will rpm -Fvh *.rpm still report a dependacy by gnome-media-1.0.51-1 because the specific release extace-1.1.14 is not installed?
0
JimIntriglia
Asked:
JimIntriglia
1 Solution
 
bernardhCommented:
have you tried the -Ivh or the -Uvh --force parameters?

0
 
ohad23Commented:
hi,
doing rpm -qpi extace* yeilds:
eXtace is a audio visualization plugin for the GNOME GUI desktop
environment. It connects to EsounD (the Enlightened Sound Daemon) and
displays the audio data as either a 3D textured landscape, a 3D
pointed landscape, a 16-128 channel graphic EQ, or a colored
Oscilloscope.

you can find extace* at your nearest mirror or find it in http://rpmfind.net and download it.
alternativly go to http://tech.buffalostate.edu/~dave/extace/ and read all about it !!!
0
 
JimIntrigliaAuthor Commented:
ohad23

Thanks for your response. The version of extace that RPM is reporing a dependancy on is not available at either site you provided.

Question #1 is presently the focus a this time. Apparently, he belief by those knowledgeable of RPM is that downloading a later version of extace would resolve he dependancy problem when rpm -Fvh --test *.rpm is rerun. This is not the case.

I have found that a (downloading) a later version of extace still results in the aforemenioned reported extace dependancy problem with: rpm -Fvh --test #.rpm.

0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
ohad23Commented:
hi,
do you have an earlier version of extace installed on your system ???
if not rpm -Fvh will not install the new version. presonaly, i prefer rpm -Uvh for upgrading.
the latest extace i have is extace-1.2.15-1 (from redhat 6.2 beta). a problem may result from gnome-media needing an exacact version (here 1.1.14)and not version >= 1.1.10.
your option are:
a) find extace 1.1.14 and install it or
b) "gamble", install the latest extace available and do rpm -Uvh package.rpm --nodeps. you should do this only if extace is backward compatible and no changes were made to the program API.

Good Luck.
0
 
JimIntrigliaAuthor Commented:
ohad23

Thanks for the additional info. Good point on the rpm freshen option.. it will not install extace, which was not part of Gnome desktop in RH V6.0 release. I tried a trial install of extace-1.2.1-1, and got an rpm message saying that a file would conflict with a Gnome-media file in user/bin.

Sheesh.

Will continue plugging away at getting this resolved.
0
 
ReinierCommented:
Sometimes such a message means that rpm cannot remove an old package because other old, soon to upgraded, rpm's need it. In that case it would be not such a gamble to use the --nodeps option. You might simply have a chicken and egg problem here. Check it out.
0
 
ohad23Commented:
no,
it means that a file in the current package is already installed on you system. you get the file name and possibly the package it came from.
check the file and the package it came from and decide if it's ok to overwrite it.
0
 
JimIntrigliaAuthor Commented:
I was successful in upgrading my GNOME desktop from RHV6.0 to RHV6.1 this morning, finally. It certainly was not easy or straightforward! Much more work to be done with the rpm utility to straighen-out this dependancy "chicken and egg" lunacy.

Anyway - here's what I had to do to resolve all dependancies and get a good RPM freshen *.rpm to work:

1. rpm -Uvh gnome-media-1.0.51-1.i386.rpm extace-1.2.1-1.i386.rpm

2. rpm -ivh libxml-1.7.3-1.i386.rpm

3. rpm -Uvh gnumeric-0.38-8.i386.rpm libglade-0.7-1.i386.rpm

4. delete libxml-1.7.3-1.i386.rpm (kept insisting a dependancy on lib.so.0, which was installed already. rpm -rebuilddb did not help this time around.

Thanks all for your comments and suggestions!
0
 
JimIntrigliaAuthor Commented:
Thanks for sticking with this and helping me work this out ;-)
0

Featured Post

Important Lessons on Recovering from Petya

In their most recent webinar, Skyport Systems explores ways to isolate and protect critical databases to keep the core of your company safe from harm.

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