Re: Removal of RPM after installing update

On Sat, 05 Apr 2008, in the Usenet newsgroup comp.os.linux.setup, in article
<47F75FC3.10403@xxxxxxxxx>, Nico Kadel-Garcia wrote:

Doug Laidlaw wrote:

Moe Trin wrote:

sledguy@xxxxxxxxx wrote:

But now I have an older version, 5.8.0 that is still installed which
was installed by RPM. I thought I would just remove it but when I
execute rpm -e without the -nodep qualifier it tells me of all the
packages that are dependant upon it.
You are discovering the problem with package managers. Most of them do
not tolerate someone bypassing them by installing tarballs.

I missed the beginning of this, but if there is a version of perl on there
that needs to be removed, "make uninstall" or its equivalent will (or
should) get rid of it for a fresh start.

[compton ~]$ rpm -ql perl | grep Makefile
[compton ~]$

The typical binary rpm (or even .deb) does not come with the Makefile, so
trying to run 'make uninstall' (even assuming /usr/bin/make is installed
and you are in the "right" directory) is not likely to do something
desirable, never mind that the Makefile has an 'uninstall' target.

That will also randomly flush components of *OTHER* RPM installed packages,
which the installation overwrote. Ideally, you'd run 'rpm -V' after that to
see which RPM's need to be re-installed.

Again, I don't know of that many packages that come with Makefiles, and
/usr/bin/make expects the Makefile in the "current" directory. I also
suspect you mean 'rpm -Va' to test all installed packages.

The O.P. could try installing his present 5.8.8. package with checkinstall: It is available for most
distros, and will take care of the problems he has faced.

Doug - re-read the problem. He installed perl-5.8.8 with no problems other
than the fact that it's a tarball, and his package manager (rpm) still
lists the package that _it_ installed. The correct solution is to NOT
install tarballs to update stuff that was installed by the package
manager. His problem is that he can't tell the package manager that
something has been updated.

I have had occasional failures with it, but it would be better (and
far easier) than building one's own RPM.

Yes, but it's even easier to stick with the packages supplied by your
distribution. That way, _they_ are monitoring the world news and are
aware when security problems develop. If you don't like using a
package manager, then you probably should be using a different type of
Linux - see the "Linux From Scratch" guide from the LDP (available at or go to

Old guy

Relevant Pages

  • Re: linux software installation
    ... It depends on which specific Linux distribution you are using. ... Different Linux distributions use different software package management tools. ... With RPM, you do need to know, beforehand, the name of the software package. ... If you hack your way through downloading, compiling and installing some warez manually, rpm won't know anything about it. ...
  • [opensuse] RPM dependencies
    ... I just tried installing a package on my version of Linux - I ... error: Failed dependencies: ... Is there a command (except for rpm -i), ...
  • Re: [SLE] Compiling SuSE
    ... This is just a weekend project. ... Perhaps one use the package 'y2pmsh' ... But if you decide to do it, I would recommend installing a minimal SUSE ... start with recompiling the rpm packages that are installed on that minimal ...
  • Re: RPM installing error
    ... verify the rpm package with -V. ... Try installing it with the --aid option. ... Redhat Channel Partner and Training Partner ...
  • Re: how do I uninstall a .tar.gz package?
    ... Other than using the source packages...the only package manager that ... Let's assume the package is named 'X' and the rpm file is X.rpm. ... To see the files 'belonging' to X, *after* installing: ...