Have you checked that the 'wrong' RPMs are removed?

Post #255,668 by static 5/16/06 11:54:55 PM Reply	Have you checked that the 'wrong' RPMs are removed? We had that sort of problem with MySQL. The RH one was the wrong version and something that wanted the libraries kept picking the wrong include files. Because we were running MySQL from a tarball, we just removed the RPMs for the other version and redirected the other thing and it worked. Wade. "Insert crowbar. Apply force."
Post #255,736 by tuberculosis 5/17/06 12:44:22 PM 5/17/06 1:00:45 PM Reply	Never mind I found it -e (for erase?). Only it can't do it - because about 20+ packages depend on it. Brilliant dependency management there. Freakin' great. And there is no rpm upgrade package available so I guess I'm going to abandon this adventure. Thanks for the help. [link\|http://www.blackbagops.net\|Black Bag Operations Log] [link\|http://www.objectiveclips.com\|Artificial Intelligence] [link\|http://www.badpage.info/seaside/html\|Scrutinizer] Edited by tuberculosis May 17, 2006, 01:00:45 PM EDT Expand All History
Post #255,821 by static 5/18/06 12:16:05 AM Reply	File a bug. Not that that will fix it, but if you don't tell them, they won't know. Wade. "Insert crowbar. Apply force."
Post #255,832 by tuberculosis 5/18/06 2:57:57 AM Reply	With/against who? wxPython? RedHat? [link\|http://www.blackbagops.net\|Black Bag Operations Log] [link\|http://www.objectiveclips.com\|Artificial Intelligence] [link\|http://www.badpage.info/seaside/html\|Scrutinizer]
Post #255,841 by broomberg 5/18/06 7:33:33 AM Reply	Don't bother RH: We support what is on our supported list. WxPython: We TOLD you, you just need to replace lib x with lib y and it should work fine. RH: If you replace lib x with lib y, then all the software we tested and support will no longer be supported. While it may work, don't bother calling us if it doesn't. I've run into this situation several times. It is FAR easier (in my case) to get dispensation to run a Debian box for my projects than force our RH boxes to run them. The general rule is if it needs any vendor support it goes on the RH. If it doesn't, we try to place it on RH but we can then fall back.
Post #255,851 by static 5/18/06 9:28:29 AM Reply	My point still stands. Even if they have no interest in fixing any level of that specific problem, sooner or later someone will ask "how many bugs did we close that we don't want to or can't fix?". That, IMO, is why you should file a bug with RH. Wade. "Insert crowbar. Apply force."
Post #255,860 by Yendor 5/18/06 9:50:46 AM Reply	Bollocks. The main reason I switched from RH to Debian (back in '02) was the following...I had a circular dependency situation going on between three different libs. No, I don't remember what they were. Basically, I couldn't install the latest version of some package because that would remove the older package, upon which other software relied upon that version and that version only. Over the course of 6 months, I filed at least 3 bug reports with RH and up2date and wherever else I could find to submit bugs with these RPM packages. None of them was ever even acknowledged -- much less "closed because [they] don't wanna look at it." Once fed up enough, I switched from RH to Debian and haven't looked back. Nothing I have heard in the intervening time makes me believe that RH has fixed ant of these problems inherent to the RPM review/dependency process. (NOTE: I'm not saying that it's the RPM format itself. It just all goes back to Debian's policy, and RPM-based-architectures' lack thereof.) -YendorMike "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." - Benjamin Franklin, 1759 Historical Review of Pennsylvania

Welcome to IWETHEY!