Summary: | Kopete can't connect to ICQ anymore | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Bram Schoenmakers <me> |
Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
Status: | VERIFIED FIXED | ||
Severity: | normal | CC: | bugs |
Priority: | High | ||
Version: | 2006.0 | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://bugs.kde.org/show_bug.cgi?id=130630 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Bram Schoenmakers
2006-07-11 10:10:14 UTC
Already working on it. Wow, FlameEyes, you're a freak (in the positive sense of the word of course :) Many thanks for working on this so quickly. I'm unable to patch kdenetwork and kde-base/kopete right now, as the patch itself doesn't apply, will look what I can do about them. False alarm, it applies, I just can't use PATCHES variable. Err nevermind, it does _not_ apply :/ Now I'm a bit confused myself, but I'm afraid I can't do much about this. If the patch does run with net-im/kopete it would be great if you could post the patch file... it's annoying to be forced using webicq. ;) The patch for net-im/kopete is now committed, kde-base/kopete and kde-base/kdenetwork will follow, now the backport is present. Are you sure the patch is committed ? I just looked through the webcvs of net-im/kopete and there is no patch. It might take a bit to come to mirrors, but now all three of them are fixed in their latest ~arch version. Thank you very much for integrating the KDE fixes into portage. The same problem came back. Since yesterday kopete says again: ICQ server thinks the client you are using is too old I hope to see a fix again soon in portage :) It is not the _same_ problem, it's just the same _symptom_, and it's fixed already: http://farragut.flameeyes.is-a-geek.org/articles/2006/07/31/the-icq-mess-part-n-m-k-1 I highly recommend you find something other than ICQ to use, considering how much they change the protocol. Thanks! |