-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday 28 April 2003 13:18 pm, Ben Rosenberg wrote:

* Curtis Rey (crrey@charter.net) [030428 10:58]: ->-----BEGIN PGP SIGNED MESSAGE----- ->Hash: SHA1 -> ->I have a package (winex3) that is listed twice according to rpm. If I issue ->the rpm -e winex3 command It say that there are multiple instances of this ->packages. -> ->A query indicates that the packages is listed twice so I was going to go into ->the file and comment out/delete it then re-issue the rpm -e command in order ->to have rpm at a current state. -> ->Does anyone know of some solutions to this problem? I only have one instance ->of winex3 to the best of my knowledge and won't to reinstall it. But, I have ->to get rpm to cooperate first in order to determine if the program or the

Curtis,

Do this..

rpm -q winex3

This should give you the names of both of the packages. Just rpm -e the older of the two and you should be fine.

Rofl. I did this (usually use the "-qv" flags), but it, of course only found one instance of the prog. However, I ran "rpm =e winex3-3.0-1" and it insisted that it was not installed. Then I did "rpm -Uhv winex3-3.0-1.i386.rpm" and it insisted that it was already installed (sheesh). So I added the "--force" flag and it, of course installed it again. Then I immediatly ran the "rpm -e winex3" command again and it removed it = LOLOLOLOLOL ! So, I did a "locate winex3" command and sure enough, sitting in the /usr/lib dir was the "transgaming_winex3" dir as usuall. The difference being that it only held the the subdir's in it and they were all empty <scratches head>. So, I rm'ed this and it should be gone, gone, gone < fingers crossed>. The rpm prog has been doing some weird things off and on over the last couple of months. One day I can access it the next (prolly after updates from SuSE for security) I can't. And the intermittant problem of it not seeing things gone or there. Him. Will be upgrading to version 8.2 and doing back up of basic desktop, files, etc... Now the next question is, since /home and /usr/local are segregated on their own partitions, what is the new gcc version do to those things I have saved and keep intact for the new install. Someone tell be that they'll run as before because the new gcc version is backwards compatible. Oh and then the Nvidia fun (me thinks I'll get the installer now, burn to disc, and have on hand - hehe). Anyway, Thanks as usual and again Ben :) :) :) Cheers, Curtis. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+rsrW7WVLiDrqeksRAlSRAJ4mUWU+jQLmmxodFXf2Ls9bK/1tmQCdER5D a8GnCcEC/I2ZRfN3HG7AZvM= =00N2 -----END PGP SIGNATURE-----

At 07:11 29-4-2003 +0100, Linux World 999 wrote:

----- Original Message ----- From: "Curtis Rey" To: Sent: Tuesday, April 29, 2003 7:56 PM Subject: Re: [SLE] Where is the RPM data base

<snip>

Is there an option to rebuild the database to correct his problem?

man rpm

LW999

-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday 29 April 2003 04:10 am, Vishal Khanna wrote:

try updateddb

Close. Try "rpm --rebuilddb" Updatedb is more designed for locate. Case in point, install a new package/tarball. Imediately after doing so run "locate and generally it won't be found. Run the updatedb and then it will. This is the find/locate data base. For rpm the "--rebuilddb" flag rebuilds anything rpm into the it's data base. HTH, Curtis. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+r5kr7WVLiDrqeksRAq5zAKCWm57FjhOk/2E6gDPcDIlFwI2osQCdG2Hs dAGTaEGnQtZB6vmtergGZTU= =4TBY -----END PGP SIGNATURE-----