Hello! On 16.09.2014 04:25, Gunnar Hjalmarsson wrote: > Please share the analysis which roles out the possibility that this is a > scim bug. Thank you.
How about you or someone else shares the analysis THEY have done to rule out this is a Ubuntu bug? Where is the Ubuntu triage? I thought that was the way it is supposed to be done. Have Ubuntu folks gotten this lazy nowadays? Apparently, you guys have a Ubuntu bug open. Keep the discussion there until you can clearly point out this is a bug that occurs in a Debian-only environment as well. NOT THE OTHER WAY AROUND! The "burden of proof" (if you want to call it that) is on the bug reporter. It is pretty sick to think that the Debian maintainer has to prove that something so far occuring only (!) in a clearly Ubuntu-environment with software that has no equivalent in Debian is NOT a DEBIAN bug. Stop kidding me and do your homework. Regards Rolfg -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
