Peter, thank you for responding now. You're entitled to your opinion, I don't need to agree.
And the link you posted is completely irrelevant here since I'm also the Debian Maintainer, so I *am* the dev that Collin is talking about and I *do* require bug submitters to not just "fire and forget". I ask for active cooperation if you want your bug fixed, if you like it or not. And the most basic information is if the bug is still present or not. I don't think a long list of open tickets that nobody feels like working on is better than a short list that somebody is indeed trying to fix. I just released a new scim package in Debian, but I don't expect any changes as far as bugs are concerned for Ubuntu. I also took the chance to push all those patches upstream (oh, yes, I do have commit rights in the upstream scim project, too). So, if you want to say "do you your homework", I would respond that *you* need to do it. You're barking up the wrong tree. A bug's status is easy enough to change, anyways. Thank you for the patch, it would have likely been in the current release if you just hadn't ignored the ping. -- SCIM help dialogue for scim-skk is in Japanese https://bugs.launchpad.net/bugs/53407 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
