Hi, (This is for the record, I am going public on some discussion happened in private mails.)
On Fri, Jun 14, 2013 at 02:31:30PM +0800, Tz-Huan Huang wrote: > Hi Rolf and Takashi Yano, > > On Fri, Jun 14, 2013 at 2:04 PM, Rolf Leggewie <f...@rolf.leggewie.biz> wrote: > > > > Hello everyone, > > > > I believe Yano-san is running Debian stable. Thank you very much for the > > information provided in this bug report. > > > > On Friday, 14 June, 2013 12:34 PM, Tz-Huan Huang wrote: > >> > >> As Osamu Aoki said, the scim-bridge and related packages are > >> removed (since the scim-bridge has been merged into scim). > > > > Am I incorrect to think that this only happened in 1.4.14 and thus is only Incorrect. Rolf, you knew better! (1.4.13 did not have scim-bridge source in scim anyway.) > > valid for testing and unstable? I haven't really looked very deeply into > > this at the moment due to lack of time but felt I should point this out. > > Oops... You are right, Rolf. Sorry for the wrong information. > I'll try to setup a stable box to figure out the problem if possible. No. scim-bridge was a separate package. Its removal is valid for stable. Look: http://packages.qa.debian.org/s/scim-bridge.html (Of course it happened before the release. So it was in testing and unstable when it was removed.) scim-bridge exists only in oldstable. Rolf disregarded my reminder to act if he wishes to keep scim in releasable shape on this matter. Upon his request, these communication were in private mails. (Aron, I think you also involved on this. CCed.) If Rolf's lack of time is the persistent excuse, I do not think that is right excuse to be the solo maintainer. Also, See the last bug which triggered removal of scim-bridge: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604381 (Rolf has a patch posted but he never uploaded package properly to close this bug. Then package removed and he does not even remember... sigh...) Due to the innactivity by scim maintainers (despite my reminder in private mail), this scim-bridge was removed. I think we should have discussed publicly in group and should not hide the problem as the Debian Social Contract demands. Then one unfortunate situation over a maintainer did not cause this situation. Osamu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
