amircea@libertysurf.fr writes:
Don't misunderstand me, I did not think about messing with the rpm database. I only wonder why does rpm ignore the system database /var/lib/locatedb, which is complete, can be updated and interrogated at will. I seem to remember from the times I was using slackware that it had a script for installing the binary tarballs, this script looked what files existed in the system (there was no database at that time), then told you that such and such file was missing. It seems to me that rpm
I think what you referring to here is verifying the package. Here are some handy rpm commands you could use. # Display a list of all installed packages [local] $ rpm -qa # Display package owning file [local] $ rpm -q -f /bin/bash bash-1.14.7-22 # Verify the package [local] $ rpm -V bash-1.14.7-22 I think verify only reports if it finds discrepancies. So you do the following in a script to check all packages on the system: ----------------------------------- #!/bin/bash for i in $(rpm -qa) do echo "Verifying package: $i" rpm -V $i done ----------------------------------- There are of course many things you can do with rpm. But there are too numerous to list. Read the man page and experiment a little with it. Hope this helps.
could do that too, instead of sticking to its own database which is not complete.
Every package has a list of files that it knows about. You retrieve the list of files for the bash package try: [local] $ rpm -q -l bash-1.14.7-22 You may have a different version of bash installed, so it is OK to use just bash as the package name.
On Mon, Feb 26, 2001 at 01:10:51PM -0600, Victor Cardona wrote:
On Mon, Feb 26, 2001 at 09:41:16AM +0100, amircea@libertysurf.fr wrote:
OK, I found what database it is by using rpm with option -vv (very verbose). Very useful option ! Now to interrogate or modify this database myself is another matter... does anybody know how to do it ? I tried to follow Stephan's suggestion )adjust the database using rpm with option --justdb) but it does not work.
I would shy away from messing with the RPM database. If anything should happen to it (i.e. corruption) then you lose the ability to easily install software. If you have an RPM that has a dependency for something. And you know that you have that something installed, then why not use 'rpm --nodeps -i'. I know it isn't a pretty solution, but it sure beats a reinstall.
Victor Cardona
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
-- Jesse Marlin Software Engineer Intec Telecom Systems Bldg G 4th Floor, 5775 Peachtree-Dunwoody Road Atlanta, GA 30342 Main 404-705-2800 Ph 404-705-2912 Fax 404-705-2805 Email Jesse.Marlin@intec-telecom-systems.com http://www.intec-telecom-systems.com