Re: General RPM question

[Chris Kloiber <ckloiber rochester rr com>]

Michael Rich wrote:
> 
> I have a sort of general RPM question that I was wondering about.
> 
> What is usually the best method to do updates per say?  For instance, the
> other day I was compiling FreeAMP, and it said I needed a newer version of
> GTK, so I slid on over to RH website and pulled down a an updated RPM pack.
> I then proceeded to try to install them with a command like:
> 
> rpm -U XXXXXX.rpm (don't remember the file name)
> 
> and it basically told me that there were dependencies on another package, so
> I couldn't upgrade.  When I downloaded and tried to upgrade that other, it
> basically told me it was dependant on that original one I was trying to
> upgrade (circular references it appears).
> 
> Now what is the sort of accepted way to do updates like this?  I ended up
> finding a switch to ignore dependencies, but that crap could come back to
> haunt me one of these days since they are usually there to keep me from
> doing something stupid.
> 
> Any suggestions/tips that could help an aspiring (hehe) Linux newbie?
> 
> Michael Rich
> http://alphax86dev.cjb.net
> http://www.cdx.sk/userwebs/zdrpg
> 
> --
> To unsubscribe: send e-mail to axp-list-request@redhat.com with
> 'unsubscribe' as the subject.  Do not send it to axp-list@redhat.com

If two packages depend upon each other like that, you can update both at
once.
Put both rpms in an otherwise blank directory, and issue the command:

rpm -Uvh *.rpm --nodeps

or maybe even:

rpm -Uvh *.rpm --force

One or the other will work. Since you are talking about the GTK
libraries in particular, I would suggest you do this without X windows
running (say: run level 3, not having used startx) so that none of the
GTK libraries are in use. BTW- Don't ever try to update glibc on a
running system, or you won't have a running system anymore (I found out
the hard way :)

Chris Kloiber