Re: Forced rpm install does not seem to work

Darius writes:

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.

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.

This is what I try mas
root

rpm -ivh --force lib64qt3-3.3.7-blah.blah.blah.rpm

I can guaranteed that anytime you use the --force option, whatever you're trying to do it won't work. Guaranteed. 100% of the time.

Let's put it this way: if you really understand what the --force option does, and why it is needed, you would not be asking questions about rpm, you'd be answering them.

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.

Unless the above applies to you, forget that --force exist. Erase it from your mind. Anyone who tells you otherwise, doesn't know what he's talking about.

The rpm does not complain of any errors, and does show that it

Of course it won't complain of any errors. You told it to ignore all the big honking errors that it would otherwise be yelling at you, about.

The --force option is like you putting black masking tape over the "low oil pressure" light on your dashboard, then complain that your car did not warn you before the engine went up in smoke.

What could be going on that the rpm is somehow failing to install the
libqt-mt.so.3 file?

Because you're trying to install the wrong package, for a wrong Linux distribution or version.


Attachment: pgpQENtEJBhD4.pgp
Description: PGP signature

Relevant Pages

  • Re: Redhat to Freebsd
    ... >>researching security updates or in performing kernel or package updates. ... >>I assume it is only the Redhat distro that has the ease of RPM installation? ... So you can build from sources with ports, or install binaries ...
    (comp.unix.bsd.freebsd.misc)
  • Re: ./configure command
    ... The package is not available. ... machines which don't even have an OS at all, let alone RPM, ... There is not a "the tool to package and install on Fedora". ... If he wants to avoid trouble, ...
    (Fedora)
  • Re: Backing up whole system
    ... Amanda is packaged by Fedora and if Gene feels that the packages are ... fedora's rpm is/was incapable of handling the nuances of using only enough ... When an rpm package can build a complete user from scratch, ... Do you really believe that rpm can install every package under the sun, ...
    (Fedora)
  • Re: [SLE] deCSS
    ... >> Anyone know of a reasonably easy decss program to copy DVDs to my hard ... This let's you compile from source but converts it to an rpm ... Then instead of make install you type checkinstall. ... package to meet the dependencies it may not be recognized by the other ...
    (SuSE)
  • Re: Ubunto
    ... developing Java on Fedora? ... The javadoc is in a third package, ... The lower layer is RPM - RPM files and the 'rpm' command, which is all about taking RPM files and unpacking them into the filesystem. ... It will then transactionally install all of them ...
    (comp.lang.java.programmer)