Forced rpm install does not seem to work

Darius · External Since: Nov 25, 2006 Posts: 72

This message is not archived

Lenard · External Since: Apr 07, 2004 Posts: 455

Sam wrote:

> The only time you can legitimately use the --force option would be for a
> an rpm package that you built yourself, as a developer, but which contains
> some
> packaging error that; but you still want to temporarily install it. You
> know what the packaging error is, but you want to take a look at some
> other unrelated stuff in the package, and that you will soon rebuild a
> fixed package and use it to replace the broken one.

Re-installing the same rpm package using the --force switch is another legit
reason after someone went braindead briefly and manually deleted some of
the files related to the package. I've seen people delete the contents of
the /lib/modules/<kernel-version-number> directory for the running kernel
(for example) and wonder why they are having problems with the kernel
afterwards.

But you are right the use of the --force switch should be limited in use for
only extremely rare reasons.

--
Contained within the Microsoft EULA;
This Limited Warranty is void if failure of the Product has resulted
from accident, abuse, misapplication, abnormal use or a virus.

Darius · External Since: Nov 25, 2006 Posts: 72

This message is not archived

Darius · External Since: Nov 25, 2006 Posts: 72

This message is not archived

Robert Heller · External Since: Sep 13, 2006 Posts: 255

At Fri, 22 Dec 2006 14:08:38 +0000 Darius <Darius@::1.t> wrote:

>
> On Thu, 21 Dec 2006 21:33:55 -0600, Sam scribed:
>
> > That means that the rpm that you "tracked down" is the wrong one. It's for
> > a different Linux distribution or version. You must find the rpm package
> > for the exact version and release of the Linux distribution you're running.
> > You cannot take an rpm built for Mandrake, for example, and try to shoehorn
> > it into Fedora. It won't work.
>
> Where I got the original rpm from a website that claimed it was for
> the right distro etc., so I'll try looking for another version
> somewhere else.
>
> Thanks for the info about --force option Smile

.

If you need this library to *build* something, you'll need a -devel RPM.

(Asside to "Sam": It is possible to install RPMs from 'foreign' distros
and have things work. Yes, there can be issues and not all 'foreign'
distros 'work' and sometimes you need to do --nodeps. I have various
RPMS from off the RedHat world working just fine on my CentOS system.)

>
> Darius
>

--
Robert Heller -- 978-544-6933
Deepwoods Software -- Linux Installation and Administration
http://www.deepsoft.com/ -- Web Hosting, with CGI and Database
heller.RemoveThis@deepsoft.com -- Contract Programming: C/C++, Tcl/Tk

Unruh · External Since: May 27, 2005 Posts: 2192

Lenard <lenard.RemoveThis@127.0.0.1> writes:

>Sam wrote:

>> The only time you can legitimately use the --force option would be for a
>> an rpm package that you built yourself, as a developer, but which contains
>> some
>> packaging error that; but you still want to temporarily install it. You
>> know what the packaging error is, but you want to take a look at some
>> other unrelated stuff in the package, and that you will soon rebuild a
>> fixed package and use it to replace the broken one.

Nope. rpm -i package.2.i386.rpm
rpm -e package.1
OOps now a lot of the programs installed by package 2 have been erased.
(Note thie happens most often when the distribution decided to rename the
package between version 1 and 2 but they still shared programs)

Now you need to install package.2 again to reinstall the programs the
removal of package.1 erased.
This happens often when you update rather than reinstall.
Try running rpm -Va |grep missing on such a system sometime.

>Re-installing the same rpm package using the --force switch is another legit
>reason after someone went braindead briefly and manually deleted some of
>the files related to the package. I've seen people delete the contents of
>the /lib/modules/<kernel-version-number> directory for the running kernel
>(for example) and wonder why they are having problems with the kernel
>afterwards.

>But you are right the use of the --force switch should be limited in use for
>only extremely rare reasons.

>--
>Contained within the Microsoft EULA;
>This Limited Warranty is void if failure of the Product has resulted
>from accident, abuse, misapplication, abnormal use or a virus.

Darius · External Since: Nov 25, 2006 Posts: 72

This message is not archived

noi · External Since: Oct 19, 2004 Posts: 614

On Thu, 21 Dec 2006 23:38:30 +0000, Darius wrote this:

> I have a problem with QT in that some package I want to install requires
> libqt-mt.so.3 so the package can install. I have tracked down the rpm to
> install the missing file, but when I try the installation of the app, I
> keep on getting an error that libqt-mt.so.3 is needed, even though it's
> supposed to have installed. This is what I try mas root
>
> rpm -ivh --force lib64qt3-3.3.7-blah.blah.blah.rpm
>
> I have read online that this should install everything, but it does not
> seem to matter whether I am in X under konsole, or not using X, it just
> gives the same error when I try installing the other application I want.
>
> The rpm does not complain of any errors, and does show that it
> "succeeded", the progress bar being 100%.
>
> What could be going on that the rpm is somehow failing to install the
> libqt-mt.so.3 file?
>
> Thanks
> Darius

Try again after installing the lib64qt3-3.3.7-DeveL-blah.blah.blah.rpm if
there is one.

Unruh · External Since: May 27, 2005 Posts: 2192

noi <noi.DeleteThis@siam.com> writes:

>On Thu, 21 Dec 2006 23:38:30 +0000, Darius wrote this:

>> I have a problem with QT in that some package I want to install requires
>> libqt-mt.so.3 so the package can install. I have tracked down the rpm to
>> install the missing file, but when I try the installation of the app, I
>> keep on getting an error that libqt-mt.so.3 is needed, even though it's
>> supposed to have installed. This is what I try mas root
>>
>> rpm -ivh --force lib64qt3-3.3.7-blah.blah.blah.rpm

Have you actually looked to see if libqt-mt.so.3 is installed?
If you do
rpm -ql lib64qt3|grep libqt-mt.so.3
is it listed?

>>
>> I have read online that this should install everything, but it does not
>> seem to matter whether I am in X under konsole, or not using X, it just
>> gives the same error when I try installing the other application I want.

Look to see if it is installed. And tell us EXACTLY what the errors are.
You admit you are confused, but we are supposed to believe you when you say
things. We do not. Show us the output exactly.

>>
>> The rpm does not complain of any errors, and does show that it
>> "succeeded", the progress bar being 100%.
>>
>> What could be going on that the rpm is somehow failing to install the
>> libqt-mt.so.3 file?
>>
>> Thanks
>> Darius

>Try again after installing the lib64qt3-3.3.7-DeveL-blah.blah.blah.rpm if
>there is one.