I got it to work. I didn't use -Uhv. And no, I wasn't using wildcards, it was just an example (bad one at that). I was trying to update MySQL from 3.23 to 4. I installed the client tools first, then the shared, then tried the server package but got errors about perl-DBD being needed by MySQL-3.23. I then tried to remove MySQL-3.23 with the -ev option, that said it was required by perl-DBD, then when I tried to remove perl-DBD it said it was needed by MySQL-3.23. I finally got it to work with a --force -ihv MySQL-server.rpm. The databases are all up and running just fine on the new version. For future reference though, how does one go about updating a package? The way up2date does it. I don't mind using up2date, but it always seems like its a few releases behind. -----Original Message----- From: psyche-list-admin@xxxxxxxxxx [mailto:psyche-list-admin@xxxxxxxxxx] On Behalf Of Tom Diehl Sent: Wednesday, July 23, 2003 12:14 AM To: psyche-list@xxxxxxxxxx Subject: Re: rpm upgrading On Tue, 22 Jul 2003, Matt D. Brei wrote: > I must be a bit confused on the upgrading of a package using rpm. I use > rpm -Uhv <package> but it still gives me package conflicts with * > errors. Does the --replacepkgs option have to be used for this? Most likely no. You will have to tell us a little more about what you are trying to do. Are you using wildcards in your incantations?? If so don't do that until you understand what you are doing. Suggest cut-N-pasting EXACT command line used and the errors. --- ..........Tom -- Psyche-list mailing list Psyche-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/psyche-list -- Psyche-list mailing list Psyche-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/psyche-list
