confusing rpm experience

[netcomander]

Hi all,

I did 'rpm -Uvh' a package (Bye the way it was php-4.0.4...)
When I later tried to 'rpm -e php-4.0...' I got the
reply 'package is not installed'
Than I thought, okay due to this message I can
have another attempt installing the package
but 'rpm -Uvh-4.0..' replies
package is already installed

Does any body knows how to get rid of installed
rpms? As I figured out, despite the complaining
"package is not installed" when I try 'rpm -e ..',
the package is installed.

All this leads into the problem, that I have now to
different versions of php running, which can't be
very healthy.

would be glad to get a hint

 

[ifincham]

Hi,

That can be a bit confusing. When you are installing a rpm you use the full path to the file however when uninstalling you just use the rpm 'name'. That is invariably the start of the filename up to the first numeric after a '-' (i.e. the version number). For example your php rpm would just be 'php' and you'd uninstall it by doing (as root) :

rpm -e php

If you want to know what its going to do first ....

rpm -evv --test php

To list all rpms installed do

rpm -qa

This is useful if used with grep for example :

rpm -qa | grep gnome (list all with 'gnome' in the name)

Hope this helps

 

[Tarquin]

I've had similar experiences and also frustration when RPM will not upgrade a package due to sub-package dependancy issues and will not install sub-packages due to conflict with existing package version :-(. It also would not perform simultaneous upgrade and install using -Fvh and wildcards >:-<.

I ended up using KDE Package Manager and also got it to work using gnoRPM .

So you could try else as alternatives to command line RPM.