RPM remove broken packages

diego_cn · 05-22-2008, 11:38 AM

Hi,

I am running RHEL4. I accidentally deleted some files that belongs to a package. Now when I try to remove that package with:

<code>
rpm -e package
</code>

But it will not let me do it. Is there any ways to force remove a broken rpm package?

Thanks,
di

jailbait · 05-22-2008, 11:45 AM

What is the error message?

Do you intend to reinstall the rpm once you get the broken version removed?

What is the name of the rpm? There are some rpms that will result in a system crash if you remove them.

-----------------------
Steve Stites

diego_cn · 05-22-2008, 02:21 PM

Quote:

Originally Posted by jailbait

What is the error message?

Do you intend to reinstall the rpm once you get the broken version removed?

What is the name of the rpm? There are some rpms that will result in a system crash if you remove them.

-----------------------
Steve Stites

Hi jailbait,

Thanks for the reply. The RPM package is third party one custom build by our company.

Code:

rpm -ql packagename

Shows everything is installed under /opt, which I removed entirely. Since that linux machine is not connected to network, I can only describe the err message:

Code:

chmod: Cannot access /opt/... No such file or directory
/var/tmp/rpm-tmp.82404 line xx: /opt/... No such file or directory
Error: %preun(packagename) scriptlet failed, exit status 1.

I guess with all the files removed, I just need to "unregister" the rpm package to make it marked as uninstalled, so I can install the package again.

lazlow · 05-22-2008, 02:45 PM

The easiest way is usually just to reinstall the rpm (use the force option). This will reinstall the files you removed. Then uninstall the rpm. After that, go back and remove the left over files.

jailbait · 05-22-2008, 03:05 PM

What lazlow says is correct. In addition you may run into a few problems with the rpm script if it wasn't written to take such things as missing directories into consideration. Try recreating some of the missing directories:

mkdir /opt

That might get you past some poor coding in the rpm script.

--------------------
Steve Stites

unSpawn · 05-22-2008, 03:22 PM

I disagree. If one fscked up by deliberately removing files by hand instead of uninstalling the package it is not the package managers fault nor "poor coding" but PEBCAK. Reinstalling the package to uninstall it is unnecessary. AFAIK the OP is right if he just needs to "unregister" it (never mind the connotations of the term). Executing 'rpm --justdb -e packagename' should do just that.

jailbait · 05-22-2008, 03:47 PM

unSpawn,

I agree that diego_cn should be able to uninstall the rpm even though he has deleted /opt. He also says in his second post that he wants to install the rpm again. So installing the new rpm with update or force is also a viable way to override the old rpm.

I have seen rpm packages that assume that such things as /opt or /usr exist and fail if they don't. Since this rpm was written in house and not by a distribution it is quit possible that it doesn't have if statements creating /opt if /opt does not exist, etc.

------------------
Steve Stites

unSpawn · 05-22-2008, 05:42 PM

Quote:

Originally Posted by jailbait

He also says in his second post that he wants to install the rpm again.

Thanks for pointing me to that. I should have read his post more carefully.

diego_cn · 05-22-2008, 11:27 PM

--justdb

That's what I am looking for. Thanks for all your helps.

To clarify the matter a little bit more, for future reference: The original rpm packages was coded such that it has to install through a external script file. Therefore it cannot be manually installed. So reinistall with --force option does not work here.

p.s yum has spoiled me and I forget much of the rpm arguments already