Alex Roitman <[EMAIL PROTECTED]> writes: >> It is no viable strategy to release with a libglade2 that has >> incompatible behaviour to upstream. Just think of a user compiling >> software locally that relies on the changes made in libglade >> 2.4.1. Also, it seems synaptic, which also had this issue (see >> #288642) has already been fixed, as has the Linux kernel's gconfig >> system. >> >> So, I've you cannot convince me that libglade2 should be patched (I >> think you won't be able to :-P), I'll reassign #290811 this to meld. > > I completely agree. My hope would be that you or somebody else with more > weight (developer-wise :-) than I am would push the > http://bugzilla.gnome.org/show_bug.cgi?id=163322 > towards its resolution upstream. This problem will affect all distros, > once they upgrade to 2.4.1. > > I would kindly ask you to do two things: > > 1. Try my testcases from that bugzilla page > 2. Post your opinion to the bugzilla page > Yeah, will do that. I'll hopefully come around to deal with this issue today or tomorrow; I also will rise it on the GTK+ developers list.
Rotty -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
