there is a fix for this in kde svn, from #kde topic: Problems with kopete connecting to MSN is fixed in svn, both trunk and branch. Instructions for building it are here: http://wiki.kde.org/tiki-index.php?page=Kopete+SVN Reproducible: Always Steps to Reproduce: 1. 2. 3.
fixed SVN commit 415681 by ogoffart from http://websvn.kde.org/tags/?rev=415681&view=rev
please get a fixed version on portage as soo as you devs can... this is a very annoing bug...
Same problem with profile 2005.0 under AMD64
I ported the patch from svn to kde 3.4.0 least i hope so :)
Created attachment 59321 [details, diff] kdenetwork-3.4.0-kopete-msn.patch
can I just copy this patch into the "files" directory in the kopete portage directory?
put it in the files directory and add something like this: # fix kde bug 105929. Applied for 3.4.1. PATCHES1="${PATCHES1} ${FILESDIR}/kdenetwork-3.4.0-kopete-msn.patch" to the end of your ebuild file... I'd do this in your overlay directory (/usr/local/portage) though...since the change will get overwritten next time you sync...
Ok it works I try backport it 3.3.2 to, I need it at work :)
ok, but I also needed to digest the ebuild, because I got: >>> emerge (1 of 1) kde-base/kopete-3.4.0-r2 to / !!! Security Violation: A file exists that is not in the manifest. !!! File: files/kdenetwork-3.4.0-kopete-msn.patch Thank you!
Created attachment 59324 [details, diff] kdenetwork-3.3.2-kopete-msn.patch
I cant test 3.3.2 patch before tomorrow
Created attachment 59329 [details, diff] kdenetwork-3.4.0-kopete-msnlogin.patch This patch fixes the problem.
Created attachment 59330 [details] kdenetwork-3.4.0-r3.ebuild Updated ebuild. BTW, sorry for the sending the patch again, it wasn't present when I looked at the page, so I made the patch, tested it and submited. When the page reloaded after sending the patch, I saw someone had already sent it while I was testing.
(In reply to comment #4) > I ported the patch from svn to kde 3.4.0 > > least i hope so :) Thanks Raul, this patch seems to work nicely.
now we have the patch... time to get it into portage... Devs please do it ASAP Thanks
The patch worked for me - but I wasn't able to compile with USE flag "kdeenablefinal"... I don't remember the exact error, something about a redundant declaration or something.... it worked fine with "-kdeenablefinal" though.... Just a warning - I don't know if they want to include it into portage until it works in all cases. I used the first patch - (kdenetwork-3.4.0-kopete-msn.patch) I can't speak for the second one....and I really don't have the time to keep recompiling to test patches.
Intresting I have kdeenablefinal turned on at home and it works
Created attachment 59348 [details, diff] kdenetwork-3.4.0-kopete-msn-2.patch Small typo fix, changed one sslloginhandler.o -> sslloginhandler.lo in Makefile.in dunno if that helps, im not c++ expert
And i can confirm that kde 3.3.2 patch works the last typo fix is already in kde-3.3.2 patch
for the forum-users redirected to this place: a quick how-to-apply-the-3.3.2-patch: * become root (mostly 'su') * cd /usr/portage/kde-base/kdenetwork/ * edit kdenetwork-3.3.2.ebuild to become this: [---snip---] src_unpack() { kde_src_unpack epatch "${FILESDIR}/${P}-kopete-msn.patch" } [---snip---] * Download that file in the patch-list above and save it to /usr/portage/kde-base/kdenetwork/files/ * run 'ebuild kdenetwork-3.3.2.ebuild digest' to add the digest of the file. * run 'emerge kdenetwork' to update WARNING: this manual update WILL BE DELETED once you run 'emerge sync'. (unless the dev's have made that update to portage.
(In reply to comment #16) > The patch worked for me - but I wasn't able to compile with USE flag > "kdeenablefinal"... > > I don't remember the exact error, something about a redundant > declaration or something.... > > it worked fine with "-kdeenablefinal" though.... It doesn't compile for me with the 'kdeenablefinal' either.
Created attachment 59387 [details] Kopete ebuild for the split-ebuild setup This ebuild seems to work for me. It works with the provided patch.
can you please post compile output I think it is something about the Makefile.am part
I could not compile kopete with USE="kdeenablefinal". With USE="-kdeenablefinal" kopete compiles succesfully. I used the split ebuild. Here is the error I get: creating libkopete_msn_shared_la.all_cpp.cpp ... /bin/sh ../../../libtool --silent --mode=compile --tag=CXX i686-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I../../.. -I./ui -I./ui -I../../../kopete/libkopete -I../../../kopete/libkopete/ui -I../../../kopete/libkopete/ui -I/usr/kde/3.4/include -I/usr/qt/3/include -I. -DQT_THREAD_SUPPORT -D_REENTRANT -D_FILE_OFFSET_BITS=64 -Wnon-virtual-dtor -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts -Wall -W -Wpointer-arith -Wwrite-strings -DNDEBUG -DNO_DEBUG -O2 -O2 -march=athlon-xp -pipe -mmmx -m3dnow -msse -fomit-frame-pointer -Wformat-security -Wmissing-format-attribute -fno-exceptions -fno-check-new -fno-common -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -c -o libkopete_msn_shared_la.all_cpp.lo `test -f 'libkopete_msn_shared_la.all_cpp.cpp' || echo './'`libkopete_msn_shared_la.all_cpp.cpp distcc[17702] ERROR: compile /root/.ccache/libkopete_.tmp.giga.17698.ii on localhost failed In file included from libkopete_msn_shared_la.all_cpp.cpp:4: msnaddcontactpage.cpp: In member function ` MSNAddContactPage::MSNAddContactPage(bool, QWidget*, const char*)': msnaddcontactpage.cpp:29: warning: unused parameter `bool connected' In file included from /usr/kde/3.4/include/kssl.h:25, from sslloginhandler.cpp:29, from libkopete_msn_shared_la.all_cpp.cpp:18: /usr/kde/3.4/include/ksslpeerinfo.h: At global scope: /usr/kde/3.4/include/ksslpeerinfo.h:31: error: use of `KInetSocketAddress' is ambiguous /usr/kde/3.4/include/ksockaddr.h:234: error: first declared as `class KInetSocketAddress' here /usr/kde/3.4/include/ksocketaddress.h:642: error: also declared as `class KNetwork::KInetSocketAddress' here /usr/kde/3.4/include/ksslpeerinfo.h:31: error: `KInetSocketAddress' denotes an ambiguous type /usr/kde/3.4/include/ksockaddr.h:234: error: first type here /usr/kde/3.4/include/ksocketaddress.h:642: error: other type here make[5]: *** [libkopete_msn_shared_la.all_cpp.lo] Fejl 1 make[5]: Leaving directory `/var/tmp/portage/kopete-3.4.0-r3/work/kopete-3.4.0/kopete/protocols/msn' make[4]: *** [all-recursive] Fejl 1 make[4]: Leaving directory `/var/tmp/portage/kopete-3.4.0-r3/work/kopete-3.4.0/kopete/protocols/msn' make[3]: *** [all-recursive] Fejl 1 make[3]: Leaving directory `/var/tmp/portage/kopete-3.4.0-r3/work/kopete-3.4.0/kopete/protocols' make[2]: *** [all-recursive] Fejl 1 make[2]: Leaving directory `/var/tmp/portage/kopete-3.4.0-r3/work/kopete-3.4.0/kopete' make[1]: *** [all-recursive] Fejl 1 make[1]: Leaving directory `/var/tmp/portage/kopete-3.4.0-r3/work/kopete-3.4.0' make: *** [all] Fejl 2 !!! ERROR: kde-base/kopete-3.4.0-r3 failed.
Created attachment 59447 [details, diff] kdenetwork-3.4.0-kopete-msn-3.patch From kde svn log "SVN commit 416060 by wstephens: SSLLoginHandler breaks --enable-final because it uses the old style KInetSocketAddress class and the rest of MSN uses the new KNetwork::KInetSocketAddress." Patched again Makefile.in
Created attachment 59448 [details, diff] kdenetwork-3.3.2-kopete-msn-2.patch
Created attachment 59476 [details] Candidate for kdenetwork-3.3.2-r1.ebuild with backported patch Trivial ebuild update for kdenetwork-3.3.2 to apply the backported patch (http://bugs.gentoo.org/attachment.cgi?id=59448&action=view). The only change, apart from appending -r1 to the version number, was the addition of the following line after line 19: epatch ${FILESDIR}/kdenetwork-3.3.2-kopete-msn-2.patch Hey, the new ebuild had to be put up, nomatter how trivial, right? :-P At least the impatient will have something to stuff in their overlay to get MSN working with Kopete/KDE-3.3.2 again, without having to upgrade to 3.4.x.
Created attachment 59589 [details] Modified the split-ebuild version for msn-3 patch Modified the split-ebuild version of kopete-3.4.0-r3 to macht msn-3 patch since kdenetwork-3.4.0-kopete-msn-2.patch became obsolete
I wanted ask is the 3.3.2 still failing? maybe can some dev add it to portage
The split-ebuild doesn't include all of the previous patches. The msn patch line should be prefixed with ${PATCHES1}
Created attachment 59678 [details] Added ${PATCHES1} to split-ebuild version for msn-3 patch
Comment on attachment 59678 [details] Added ${PATCHES1} to split-ebuild version for msn-3 patch Sorry, didn't noticed that ${PATCHES1} wasn't in the split-ebuild in the first place
*** Bug 93794 has been marked as a duplicate of this bug. ***
0.10.1 is out and should work with MSN again... http://kopete.kde.org/index.php?page=downloads
portage should have kde-base/kopete/kopete-3.4.0-r3.ebuild with the following fix: # fix for kopete login bug: 93213 # fix kde bug 105929 PATCHES1="${PATCHES1} ${FILESDIR}/kdenetwork-3.4.0-kopete-msn-3.patch" because all users wont switch to 3.4.1 which is currently hard masked
I added the patch for kdenetwork-3.3.2. Thanks. About kde 3.4: kde 3.4.1 will be available just in a few days, it will be unmasked as soon as it is officially released.
(In reply to comment #36) > I added the patch for kdenetwork-3.3.2. Thanks. > > About kde 3.4: kde 3.4.1 will be available just in a few days, it will be > unmasked as soon as it is officially released. > (from the Kopete developers on IRC): with KDE 3.4.1 will come Kopete 0.10.2 So there is no need to hard-mask Kopete 0.10.1, as it is designed to work with KDE 3.4.0
(In reply to comment #36) > About kde 3.4: kde 3.4.1 will be available just in a few days, it will be > unmasked as soon as it is officially released. It's not that smart to let people wait 2 weeks for a fix, even if kde 3.4.1 is about to be released. Think about users that don't know how to overlay portage / patch manually ...
Sorry, but I have to me-too comment #38. Fixing packages already marked stable should be one of the highest priorities if we want Gentoo to be an acceptable distro for users, and a respected distro among its peers.
(In reply to comment #39) > Sorry, but I have to me-too comment #38. Fixing packages already marked stable > should be one of the highest priorities if we want Gentoo to be an acceptable > distro for users, and a respected distro among its peers. kde 3.4 is not marked stable.
You're absolutely right. Forgive my sleepy brain. :) I do think that such an easy fix should be put out more quickly (under ~arch in this case), but at least it's not as bad as I was thinking.
kde 3.4.1 is available now, closing. Sorry that nobody was around last week to fix it immediately, that just happens.
(In reply to comment #40) > (In reply to comment #39) > > Sorry, but I have to me-too comment #38. Fixing packages already marked > stable > > should be one of the highest priorities if we want Gentoo to be an > acceptable > > distro for users, and a respected distro among its peers. > > kde 3.4 is not marked stable. But the fixed kdenetwork isn't available for the stable (3.3.2) release, either, so the previous comments still make sense.