How do I fake an RPM file being installed?
In some recent update, I seem to have gotten the file "libdvdread.so.3" installed in "/usr/lib" (if you want to check, the file length is 127044, and the date is Jan 27, 2008). This looks fine.
Now I have a bunch of rpm's that insist on having the package "libdvdread.so.3" and I can't fine a package that has it. How do I tell the RPM database that this file is alive and well in my system? It ought to be pretty simple, but there doesn't seem to be a simple way to do it. Thus the request: HELP! |
If that is the only dependency preventing installation, I would personally just force the installation with the --nodeps option to the RPM command. You can fake entries, or do things like take an RPM package and only install it in the database, without installing the files, but that requires an rpm in the first place.
|
If it were just a single package that wanted the file/package, I'd do the --nodeps route. The problem is that SEVERAL packages desire this file, thus the question.
The more general problem is that this comes up using 'yum' to fetch packages, and do updates. The nice automated utilities (read: GUI's) don't have a simple override. I was hoping for a solution like "Look, I have this file! Put it in your database and don't talk to me about it. Trust me!". |
Quote:
Are you mixing repositories? Which ones do you use? Can you post the "/tmp/update.err" output of picking one package (from the same repo you got libdvdread from) that depends on libdvdread and running 'yum -y update [packagename] 2>&1 | tee /tmp/update.err'? |
Quote:
Provides libdvdread.so.3 and install it |
All times are GMT -5. The time now is 06:37 AM. |