FedoraThis forum is for the discussion of the Fedora Project.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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.
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!".
The package is libdvdread-.*.rpm (as in 'rpm -qf /usr/lib/libdvdread.so.*').
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'?
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!
You can create package with no files that only has
Provides libdvdread.so.3
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
