From: Luke S. <lsc...@us...> - 2005-04-07 18:05:24
|
On Thu, Apr 07, 2005 at 07:31:26PM +0200, Pekka Riikonen wrote: > > Ok, oldstatus branch links without any problems against SILC Toolkit > 0.9.13, and basic usage seems to work without problem. > > : > > : > : further, there are bugs > : > : http://sourceforge.net/tracker/index.php?func=detail&aid=1170853&group_id=235&atid=100235 > : > : > : > This is reproducible but without working environment I cannot say more. > : > Looking at code, the find_conversation_with_account uses type > : > GAIM_CONV_CHAT, and the chat is created by Gaim itself, so if it returns > : > the IM chat (which is of same name as the channel chat) instead of channel > : > chat, I don't know what to say... The type is supposed to be used to > : > distinguish between chats. But, with working environment I can debug this > : > more... > : > Right... The oldstatus branch seems indeed to miss the type parameter in > the gaim_find_conversation_with_account, so, if there is a chat that has > same name as IM conversation, then it returns which ever it finds first > (which can be wrong one). This is pretty difficult to fix, unless the > type check is introduced to oldstatus. On protocols where channels have > specific identifier (like #) this problem does not exist. You decide. I think as per Stu's email we can agree on fixing this for 2.0.0 (head) only. I can handle bug reports as such. > > : > > : > : http://sourceforge.net/tracker/index.php?func=detail&aid=1033303&group_id=235&atid=100235 > : > : > : > The auto-join bug I could not reproduce (ie. worked). > : > : I've only tried one, that works, I haven't tried two. I'm currently > : using cvs HEAD, so I'm without a working environment myself, I will > : try this at home. > : > Ok. Found and fixed the bug, in SILC Toolkit, in CVS more specificly. Awesome! I'm closing that bug accordingly. > > : > : http://sourceforge.net/tracker/index.php?func=detail&aid=1039864&group_id=235&atid=100235 > : > : > : > I have two differente accounts for two different networks in my account > : > list. Servers are different, nicks are different. I haven't needed same > : > nick on same network yet, so I never tried that when I did the plugin. > : > The same nick issue with same server, though, is reproducible. But, > : > aren't accounts created by Gaim not the plugin? > : > : right, but I've tried "luke" on silc.twocrazyguys.net, a server a > : friend of mine and I set up, and "lschiere" on silc.silcnet.org, I can > : sign on *either one* fine, but if I go to sign on both, the second one > : will fail to load the key. When that failed for me, I did not try > : same sn. > : > Seems to work. Although, everything goes into the same Buddy List, which > I'm not sure if it is correct or not. All I know, I don't like it > :) Perhaps there's some specific kind of set up where this fails to > work? visually, yes, they would be in the same buddy list window, and groups would be mixed, but the tooltip's "Account" line should indicate to which it belongs; each buddy should belong to just one account. This would allow you to pick what server/network to communicate over even if the other side was also using gaim and thus had the same key for both networks. on a side note, I tend to agree with Stu that gaim should be allowing one key per account, not one per client as is presently the case. I *suspect* that might solve this problem for me. As you do not seem to be able to duplicate it, is there any debuging info I can provide? > > : http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=273871 > : is the specific issue I'm thinking of. This will keep silc out of > : debian, presumably out of Ubuntu, and quite likely out of the other > : debian based distros as well. > : > I can feel the pain in everyone involved in that thread, though this is > the first I hear about this. However, as the binary packages, on debian > and on every other distribution, is done by a contributor who contributes > ones free time to this thing of ours, they are well within their rights to > stop contributing. All I can promise you is that I'll talk to toma and > see what he has to say. Right, I understand that. Somewhere I'd gotten the impression that Toma was packaging it as part of the silcnet organization. I appoligize for the confusion my mistake has created. luke > > Pekka > ________________________________________________________________________ > Pekka Riikonen priikone at silcnet.org > Secure Internet Live Conferencing (SILC) http://silcnet.org/ |