On Wed, Apr 27, 2005 at 10:42:00PM -0500, Micah Anderson wrote: > Since the bug appears when you install libwxgtk2.4-python, it seems it > is a problem with the wx2.4 package. The solution is to Conflict > against wxpython2.5.3.
Conflicting with future unknown packages is not a solution to anything except perhaps boredom and stable upgrades. I don't want to sound rude, but I've continually had some new clown want to exchange a dozen justifications on this subject, without any examination of the real facts at hand. wx2.5 is a broken mess. It is none of wx2.4's business to get tangled up in that. This is not a symptom tracking system, and there is no bug in the 2.4 package that the above solution applies to. I close these bugs now, because the last time I left them open for information purposes, people abused them as polling booths. As if force of opinion ever fixed a bug. If people who don't read existing reports stop reporting without checking out why their bugs were summarily closed, then I'm beginning to see that as less of a bad thing. wx2.6 will be along soon. Until then 2.5 must go away if people can't be trusted to play with it responsibly. The more you waste my time on this, the longer that will (obviously) take to happen. And the more likely that wx2.6 will languish in unstable with serious unsolved bugs too. Ron -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
