Psi 0.11 has had two betas so far. It might be a good idea to get the build process working in Portage before the final version comes out and panic ensues.
Where would those 0.11 beta tarballs be located? I cannot seem to find them anywhere.
http://psi-im.org/files/beta/0.11/beta2/psi-0.11-beta2.tar.bz2
These will probably help too. Is it worth making a separate bug record for QCA2? http://delta.affinix.com/download/qca/2.0/beta2/
Created attachment 89494 [details] psi-0.11_beta2.ebuild Please remember : psi-0.11 isn't stable yet! Ok. I finally made an ebuild for psi-0.11_beta2 To install it, you will need also: - qca2, available here: http://bugs.gentoo.org/show_bug.cgi?id=129536 - if you are interested in ssl connection in psi, you also need qca-openssl plugin, available here: http://bugs.gentoo.org/show_bug.cgi?id=137132 - YOU _DON'T_ WANT QCA-GNUPG PLUGIN!!! it's broken in beta2 and nothing will work. remember - you have been warned ;) Psi could be slotted like qca, but it's simply _to_ much of work. If anybody have enough free time - you can play with it. If you try this new psi, plz report is it working for you or not (I hope it will work ;) ). Regards, Przemek
Created attachment 89495 [details, diff] psi-slotted_qca2.patch small patch for psi, to work with slotted qca2 Plz keep in mind - there's no extras version (for now ;) ). I'll start work on it _soon_. Regards, Przemek
I found official psi fix for qca-gnupg: http://el-tramo.be/files/psi/qca-gnupg_fix.diff psi-0.11_beta2 works with qca-gnupg without problems. Updated qca-gnupg ebuild can be found here: http://bugs.gentoo.org/show_bug.cgi?id=137132 Regards, Przemek
> psi-0.11_beta2 works with qca-gnupg without problems. Well, not quite. There is a known bug that you can't have two accounts with OpenPGP enabled. Other than that, it's supposed to work after that patch.
Created attachment 89499 [details] psi-0.11_beta2.ebuild psi-0.11_beta2_branchupdate - I added USE falg xmms (can only be set to disabled) - with branchudpate version, libjingle support is added. USE flag is next step on my TODO list (possibly will be ready tommorow). Regards, Przemek
As it is it tries to use stuff from qt3 and fails to build. Makefile:4780: warning: overriding commands for target `.moc/moc_opt_appearance.cpp' Makefile:4495: warning: ignoring old commands for target `.moc/moc_opt_appearance.cpp' Makefile:4786: warning: overriding commands for target `.moc/moc_opt_sound.cpp' Makefile:4507: warning: ignoring old commands for target `.moc/moc_opt_sound.cpp' Makefile:4789: warning: overriding commands for target `.moc/moc_opt_advanced.cpp' Makefile:4513: warning: ignoring old commands for target `.moc/moc_opt_advanced.cpp' /usr/qt/3/bin/uic profileopen.ui -o .ui/profileopen.h /usr/qt/3/bin/uic profilemanage.ui -o .ui/profilemanage.h uic: File generated with too recent version of Qt Designer (4.0 vs. 3.3.6) I updated to use eclass qt4 and it asked to downgrade x11-libs/qt-4.1.3 to x11-libs/qt-4.1.2. I changed DEPEND to $(qt_min_version 4.1.3) and it is now building psi-0.11 ....... After some time.... It fails while linking. dlg.o .obj/moc_mucaffiliationsview.o .obj/moc_rosteritemexchangetask.o .obj/moc_mooddlg.o .obj/moc_pepmanager.o .obj/moc_privacymanager.o .obj/moc_privacydlg.o .obj/moc_privacyruledlg.o .obj/moc_ahcommanddlg.o .obj/moc_ahcformdlg.o .obj/moc_nodeselectordlg.o .obj/moc_psioptions.o .obj/moc_voicecaller.o .obj/moc_voicecalldlg.o .obj/moc_optionsdlg.o .obj/moc_optionstab.o .obj/moc_opt_application.o .obj/moc_opt_chat.o .obj/moc_opt_events.o .obj/moc_opt_status.o .obj/moc_opt_appearance.o .obj/moc_opt_lookfeel.o .obj/moc_opt_iconset.o .obj/moc_opt_groupchat.o .obj/moc_opt_sound.o .obj/moc_opt_toolbars.o .obj/moc_opt_advanced.o .obj/moc_busywidget.o .obj/moc_fancylabel.o .obj/moc_iconselect.o .obj/moc_iconsetselect.o .obj/moc_iconsetdisplay.o .obj/moc_iconwidget.o .obj/moc_iconbutton.o .obj/moc_psitextview.o .obj/moc_iconaction.o .obj/moc_fancypopup.o .obj/moc_urllabel.o .obj/moc_urlobject.o .obj/moc_iconlabel.o .obj/moc_icontoolbutton.o .obj/moc_fancypopuplist.o .obj/moc_psitabwidget.o .obj/moc_main.o .obj/qrc_psi.o .obj/qrc_iconsets.o -L/usr/X11R6/lib -L/usr/lib64/qt4 -lz -lXss -L/usr/lib -lqca-2 -lXext -lX11 -lm -lpthread -lQt3Support_debug -lQtXml_debug -lQtGui_debug -lQtNetwork_debug -lQtCore_debug /usr/lib/gcc/x86_64-pc-linux-gnu/4.1.1/../../../../x86_64-pc-linux-gnu/bin/ld: cannot find -lQt3Support_debug collect2: ld returned 1 exit status make[1]: *** [psi] Error 1 make[1]: Leaving directory `/var/tmp/portage/psi-0.11_beta2/work/psi-0.11-beta2/src' make: *** [sub-src-make_default] Error 2 In any case it is in overlay because it will build for some users.
It needs qt built with debug use flag.Also it seems to me that one must rebuild qca and it's pluggins with debug to have then work.
I think the rule is, if you want debug, it has to be turned on for everything. If you don't want debug, you have to turn it off for everything (i.e., you can't mix and match.)
same bug I encountered when I was buildong qca{-xxx}, without having qt built with debug use flag. I'll correct this one today. as for min_qt_ver, your qt4.eclass should give you list of proper qt versions. check your qt4.eclass with the one from portage - I synced yesterday and it works for me. Regards, Przemek
Created attachment 90318 [details] darcs psi ebuild (psi-0.11_pre1.ebuild, but "pre"-suffix is wrong) If someone wants to test the latest features, took me some time to get this working. Perhaps someone is interested in this. Changes: * Darcs fetch ;-) * Support for jingle * Support for plugins (unuseable) * xmms-USE-flag only allowed when not building psi-jingle * Support for debugging (USE-Flag or QT-build) * Language-support is untested
Few days ago I made an ebuild with jingle support, but psi hangs on start. Have you tried enabling jingle support? Regards, Przemek
> Few days ago I made an ebuild with jingle support, but psi hangs on start. Have > you tried enabling jingle support? Yes, but I had no possibility to test it yet. The "Voice call"-item in the menu is grayed out, but I think the reason for that is, that nobody on my list has jingle support. The other gentoo box with psi-0.11 does not have this menu-item, but just as it does not have jingle support. Anyway my psi did hang sometimes, but I "fixed" this by disabling OpenPGP in my accounts (so it seems to be a qca-gnupg problem, like the darcs warning said). Btw.: It compiles on my amd64, but failed on x86 (for me). Some error inside libjigle, but I have not looked deeper into it yet.
Hi! As I finally become a dev, I do my best to psi ebuilds :) First I have to handle qca-2 ebuild and it's plugins. After that I psi-0.11 should be in portage. But beware - for a time being it may be hard masked, since it's still not working as it should. Regards, Przemek
Hi ! There is an error in the HOMEPAGE url (in the ebuild). It is HOMEPAGE="http://psi-im.org/" instead of HOMEPAGE="http:/psi-im.org/".
Created attachment 105141 [details, diff] patch for 64 bit system net-im/psi-0.11_pre20061231 and USE="plugins jingle spell" compile and work fine on AMD64 system this patch(small fix for long int addr).
Created attachment 105212 [details, diff] psi-pluginmanager_qstring_arg_num.patch (In reply to comment #18) > Created an attachment (id=105141) [edit] > patch for 64 bit system > > net-im/psi-0.11_pre20061231 and USE="plugins jingle spell" compile and work > fine on AMD64 system this patch(small fix for long int addr). Is psi not compiling without that patch? Qt compiled with 64bit support should cast is as 64 bit integer... it's a bit strange, if it's not compiling without it... ps. but in this code there is small typo ;) (see patch) maybe this was the problem?
it is small bug... const PsiAccount* account at 64bit system == long int but in line qDebug(qPrintable(QString("Want to send stanza to account %2").arg((int)account))); we say int = long int it is gcc error(32bit=64bit :) )
(In reply to comment #20) > it is small bug... > const PsiAccount* account at 64bit system == long int but in line > qDebug(qPrintable(QString("Want to send stanza to account > %2").arg((int)account))); > > we say int = long int it is gcc error(32bit=64bit :) ) lol... I don't have an amd64 box, so I have to read something about it... but I fought that int is (always?) int, and it shouldn't count here :/ where can I read about this gcc issue? Best regards, Przemek
int is int always... but address(blalba *dindin) at 64 bit systems = long int(or int64)(at 32 bit = int). Hm... maybe man pages for gcc4(in gcc4 moooooore checks)? sorry for my English...
(In reply to comment #22) > int is int always... but address(blalba *dindin) at 64 bit systems = long > int(or int64)(at 32 bit = int). > Hm... maybe man pages for gcc4(in gcc4 moooooore checks)? > > sorry for my English... http://lists.debian.org/debian-user/2006/04/msg00681.html nice explenation. You're right, but this is true for gcc and doesn't have to be true on other archs... I'll add it to CVS today, together with ~amd64 keyword. Thx for the patch and sorry for my english also ;) Regards, Przemek
But my patch need adapted for this ebuild... i can`t adapted now.
(In reply to comment #24) > But my patch need adapted for this ebuild... i can`t adapted now. no problem - I already create one, that my friend (with amd64 box) will check for me, today :) Cheers, Przemek
Uriy, can you open options dialog and click appearance button? is psi crashing than or everything works as expected?
Psi work but slow in this dialog. If crash need see gdb backtrace...
on psi dev mailing list, suggestion for amd64 problem was made : to remove this line with qDebug :) fixed in newest snap ebuild in portage. Cheers, Przemek
Seeing this bug reminded me that it's now up to beta4.
should be more accurate ;) Cheers, Przemek
Well, yes and no... I don't really care about the non-official-beta releases. :-)
(In reply to comment #31) > Well, yes and no... I don't really care about the non-official-beta releases. > :-) cvs snapshots aren't releases - that's why psi-0.11 is (and for some time will be) hard masked in gentoo ;) Cheers, Przemek
cant build 0.11_pre20070201 with jingle use flag with lots of "undefined referencing.." errors
(In reply to comment #33) > cant build 0.11_pre20070201 with jingle use flag with lots of "undefined > referencing.." errors yes... --as-needed... https://bugs.gentoo.org/show_bug.cgi?id=165125
I know that cvs snapshots aren't releases... what I said was that I only care about the official beta releases.
RC1 is now out.
I've tried to update this ebuild, but unsuccessfully. It also needs qca-2.0.0-beta5.tar.bz2 and qca-openssl-0.1-20070508.tar.bz2 from http://delta.affinix.com/download/qca/2.0/beta5/.
Created attachment 119107 [details] app-crypt/qca/qca-2.0_beta5.ebuild version bump
Created attachment 119108 [details] app-crypt/qca-openssl/qca-openssl-0.1_pre20070508.ebuild New package needed for psi-0.11
Created attachment 119110 [details] net-im/psi/psi-0.11_rc1.ebuild Created from _pre ebuild. Removed plugins and sasl use flag. Compiled correct with "spell ssl xscreensaver" use flags. Jingle support not tested.
hi! (In reply to comment #38) > Created an attachment (id=119107) [edit] > app-crypt/qca/qca-2.0_beta5.ebuild > > version bump well.... the problem is that qca-2 isn't just a version bump. qca-1 is used not only by the psi, but with some other projects as well. so qca-2 has to be slotted. unfortunatelly - qca-2 need to be patched for this, as well as any other project that depend on it. for now - it's only a psi snap/rc versions, but afaik kde4 will use it. I already created an updated ebuild together with 'slotting' patch. I should released it in short time - stay tune. Best regards, Przemek
(In reply to comment #40) > Created an attachment (id=119110) [edit] > net-im/psi/psi-0.11_rc1.ebuild > > Created from _pre ebuild. > > Removed plugins and sasl use flag. Compiled correct with "spell ssl > xscreensaver" use flags. Jingle support not tested. well... there's _no_ jingle support in RC1 :/ btw - qca2 is included in psi srcs, so why you need them in the tree? Regards, Przemek
(In reply to comment #42) > well... there's _no_ jingle support in RC1 :/ > > btw - qca2 is included in psi srcs, so why you need them in the tree? > > Regards, > Przemek > According to http://psi-im.org/wiki/Build_Instructions_Qt4 instructions, the qca is bundled only on svn snapshots, but not in releases. <i>Note: QCA 2.0 and related plugins are currently bundled with the Psi source code from darcs/svn but <b>not in releases</b>. In the svn/darcs sources they are enabled and built by default, so you don't need to do anything about them other than installing their dependencies.</i>
I just emerged psi-0.11_rc1 and get the following: $ psi psi: Symbol `_ZTIN3QCA11SASLContextE' has different size in shared object, consider re-linking psi: Symbol `_ZTVN3QCA11SASLContextE' has different size in shared object, consider re-linking psi: symbol lookup error: psi: undefined symbol: _ZN3QCA15KeyStoreManagerC1EP7QObject $ What to do? Thanks.
on my amd64 work without problems, please add to portage
(In reply to comment #45) > on my amd64 work without problems, please add to portage plz, give me two more days - I need to finish one thing on my univ. sorry for the delay. Cheers, Przemek
In the Psi forum, I was told that the error occuring with my installation (see comment #44) is caused by the wrong qca2 version installed. I have emerged qca-2.0_beta5.ebuild and psi-0.11_rc1.ebuild. What's wrong with that?
(In reply to comment #47) > In the Psi forum, I was told that the error occuring with my installation (see > comment #44) is caused by the wrong qca2 version installed. I have emerged > qca-2.0_beta5.ebuild and psi-0.11_rc1.ebuild. What's wrong with that? plz try ebuild from http://bugs.gentoo.org/show_bug.cgi?id=129536 together with attached patch. I'm curently testing psi-0.11_rc1 build :) Regards, Przemek
Created attachment 119940 [details] psi-0.11_rc1.ebuild psi-0.11_rc1 test ebuild - works for me. qca2: https://bugs.gentoo.org/show_bug.cgi?id=129536 qca-openssl: https://bugs.gentoo.org/show_bug.cgi?id=137132 plz test and give a word does this ebuild works for all of you. Cheers, Przemek
Yes, Psi starts and works now. But there are two issues I noticed at first sight: - Encryption can be turned on - The "Modify" button in Account Setup does nothing.
Of course, I meant "Encryption can _not_ be turned on."
I assume you've configured an encryption key in account preferences, and are talking with another user who also has a key configured. Otherwise it wouldn't work.
I can't check my key configuration because I cannot open the account preferences. The "Modify" button in "Account Setup" does nothing.
(In reply to comment #53) > I can't check my key configuration because I cannot open the account > preferences. The "Modify" button in "Account Setup" does nothing. > I have also the same problem. It looks like a QT4.3 beta related bug: http://forum.psi-im.org/post/31400
(In reply to comment #49) > Created an attachment (id=119940) [edit] > psi-0.11_rc1.ebuild > > psi-0.11_rc1 test ebuild - works for me. > > qca2: > https://bugs.gentoo.org/show_bug.cgi?id=129536 > > qca-openssl: > https://bugs.gentoo.org/show_bug.cgi?id=137132 > > plz test and give a word does this ebuild works for all of you. > > Cheers, > Przemek > Works for me on ~amd64, but I had to use the ebuild from comment #28 on bug 129536 for qca-2.0.0_beta5 because former ones didn't work for various reasons. Conditional dependency on app-crypt/qca-openssl is missing, too... I changed ssl? ( dev-libs/openssl ) to ssl? ( dev-libs/openssl app-crypt/qca-openssl ) in RDEPEND and it works fine. And I have the same issue with "Modify" button in "Account Setup" dialog mentioned in comment #50, too.
The "Modify" button in "Account Setup" seems to be fixed with the 20070606 nightly snapshot of psi. As far as I understand the bug only occured with QT-4.3 and KDE. For me the snapshot compiled fine and the Account Setup works now.
Created attachment 124252 [details] psi-0.11_pre20070708.ebuild Much improved ebuild: 1) >=qca-2.0.0_beta7 is now needed; 2) better organization of DEPEND & RDEPEND and add runtime dependency on qca-ossl if USE="ssl"; 3) new 'crypt' USE flag adds conditional dependency on qca-gnupg for cryptography through GPG keys; 4) use get_libdir() rather then hardcode QTDIR path to make multilib users happy; 5) use tc-getCXX() in qmake invocation to get the right compiler for both compilation and linking; 6) respect LDFLAGS; 7) disable dnotify on non-linux kernels; See bug #129536 for new ebuilds of qca-2.0.0_beta7 and qca-{ossl|gnupg}.
Created attachment 124272 [details] psi-0.11_pre20070708.ebuild A minor fix and use dohtml to install documentation. Thanks to Flameeyes!
Hi, the ebuild psi-0.11_pre20070708 works much better then RC1. I have only small issue with previous version of qca. Compilation of psi failed on unresolved symbols. Removing of qca-2.0_beta5 helped.
(In reply to comment #59) > Hi, > the ebuild psi-0.11_pre20070708 works much better then RC1. I have only small > issue with previous version of qca. Compilation of psi failed on unresolved > symbols. Removing of qca-2.0_beta5 helped. > Of course you should have removed qca-2.0.0_beta5 when upgrading to beta7! Two different versions of the same package cannot co-exist in the same slot! Linking can break also if you have emerged qca-1.0* without applying the slotting patch because in the linker command line -L/usr/lib (where qca1 is usually installed) appears before -L/usr/lib/qca2: in this case I suggest you to re-emerge qca-1 applying that patch or to completely remove qca-1* from your system.
I don't have a qca-1.0 in my system and I removed the old qca-2.0 version. So it is OK now. Maybe there should be some note at the end of the qca ebuild. E.g.: "You can have installed on one version of the qca-2.0 package. Please unmerge any other versions except this one!" Maybe a detection with the correct command for unmerging can be included.
Well... Portage should take care of uninstallation of older ebuilds when a new version is installed, so I cannot understand what you are saying...
So this is a problem with change package type from not sloted to sloted. Portage didn't clean out the old package(beta5) during the installation of new slotted package. It must be done manually.
0.11-RC2 seems to be out...
Created attachment 125145 [details] psi-0.11_rc2.ebuild
(In reply to comment #48) > (In reply to comment #47) > > In the Psi forum, I was told that the error occuring with my installation (see > > comment #44) is caused by the wrong qca2 version installed. I have emerged > > qca-2.0_beta5.ebuild and psi-0.11_rc1.ebuild. What's wrong with that? > > plz try ebuild from http://bugs.gentoo.org/show_bug.cgi?id=129536 together with > attached patch. With RC2, the problem I described in comment #44 occurs again. Unfortunately, I have forgotten which patch the "attached patch" is. Please, can you give me a hint? Thanks :-)
(In reply to comment #66) > (In reply to comment #48) > > (In reply to comment #47) > > > In the Psi forum, I was told that the error occuring with my installation (see > > > comment #44) is caused by the wrong qca2 version installed. I have emerged > > > qca-2.0_beta5.ebuild and psi-0.11_rc1.ebuild. What's wrong with that? > > > > plz try ebuild from http://bugs.gentoo.org/show_bug.cgi?id=129536 together with > > attached patch. > > With RC2, the problem I described in comment #44 occurs again. Unfortunately, I > have forgotten which patch the "attached patch" is. Please, can you give me a > hint? Thanks :-) > Try qca-2.0.0_beta7, qca-tls, qca-gnupg, qca-ossl from bug #129536.
(In reply to comment #67) > (In reply to comment #66) > > > > With RC2, the problem I described in comment #44 occurs again. Unfortunately, I > > have forgotten which patch the "attached patch" is. Please, can you give me a > > hint? Thanks :-) > > Try qca-2.0.0_beta7, qca-tls, qca-gnupg, qca-ossl from bug #129536. I already have qca-2.0.0_beta7, qca-gnupg and qca-ossl installed from bug #129536. qca-tls-1.0-r3 from the Portage tree is also installed. The error described in comment #44 is still present. In bug #129536, there is no ebuild for qca-tls, only a patch. I tried qca-tls-1.0-r3 from Portage with that patch, but then building Psi failed (supposedly because the patch creates a dependency to qca1).
(In reply to comment #68) > > I already have qca-2.0.0_beta7, qca-gnupg and qca-ossl installed from bug > #129536. qca-tls-1.0-r3 from the Portage tree is also installed. The error > described in comment #44 is still present. > > In bug #129536, there is no ebuild for qca-tls, only a patch. I tried > qca-tls-1.0-r3 from Portage with that patch, but then building Psi failed > (supposedly because the patch creates a dependency to qca1). > Did you uninstall any other qca ebuilds (like beta5)?
(In reply to comment #69) > Did you uninstall any other qca ebuilds (like beta5)? Yes, I did.
(In reply to comment #70) > (In reply to comment #69) > > Did you uninstall any other qca ebuilds (like beta5)? > > Yes, I did. > Maybe you should try to rebuild the qca, then qca-plugins and then psi. If doesn't help, please send the output of eix -Ic "qca|psi"
The rebuild didn't help. Here is what you asked for: tux peter # eix -Ic "qca|psi" [I] app-crypt/qca (2.0.0_beta7(2)[1]@07/18/2007): Qt Cryptographic Architecture (QCA) [I] app-crypt/qca-tls (1.0-r3@07/18/2007): plugin to provide SSL/TLS capability to programs that utilize the Qt Cryptographic Architecture (QCA) [I] app-crypt/qca-gnupg [1] (0.1_p20070706(2)@07/18/2007): GnuPG plugin for QCA [I] app-crypt/qca-ossl [1] (0.1_p20070706(2)@07/18/2007): TLS, S/MIME, PKCS#12, crypto algorithms plugin for QCA [I] media-libs/libdvbpsi (0.1.5@02/04/2007): library for MPEG TS/DVB PSI tables decoding and generation [I] net-im/psi (0.11_rc2[1]@07/18/2007): QT 4.x Jabber Client, with Licq-like interface [1] /usr/local/portage Found 6 matches. tux peter #
(In reply to comment #72) > The rebuild didn't help. Here is what you asked for: > > tux peter # eix -Ic "qca|psi" > [I] app-crypt/qca (2.0.0_beta7(2)[1]@07/18/2007): Qt Cryptographic Architecture > (QCA) > [I] app-crypt/qca-tls (1.0-r3@07/18/2007): plugin to provide SSL/TLS capability > to programs that utilize the Qt Cryptographic Architecture (QCA) > [I] app-crypt/qca-gnupg [1] (0.1_p20070706(2)@07/18/2007): GnuPG plugin for QCA > [I] app-crypt/qca-ossl [1] (0.1_p20070706(2)@07/18/2007): TLS, S/MIME, PKCS#12, > crypto algorithms plugin for QCA > [I] media-libs/libdvbpsi (0.1.5@02/04/2007): library for MPEG TS/DVB PSI tables > decoding and generation > [I] net-im/psi (0.11_rc2[1]@07/18/2007): QT 4.x Jabber Client, with Licq-like > interface > [1] /usr/local/portage > > Found 6 matches. > tux peter # > Hmm, versions are the same as I have. Are you using stable or unstable environment?
I'm using ~x86.
i've a bit updated ebuild to download sources from svn compiled and works fine on ~amd64 with all of USE flags
(In reply to comment #68) > (In reply to comment #67) > > (In reply to comment #66) > > > > > > With RC2, the problem I described in comment #44 occurs again. Unfortunately, I > > > have forgotten which patch the "attached patch" is. Please, can you give me a > > > hint? Thanks :-) > > > > Try qca-2.0.0_beta7, qca-tls, qca-gnupg, qca-ossl from bug #129536. > > I already have qca-2.0.0_beta7, qca-gnupg and qca-ossl installed from bug > #129536. qca-tls-1.0-r3 from the Portage tree is also installed. The error > described in comment #44 is still present. With these libraries installed, I tested again with different versions of Psi. The following happens at present: - psi-0.10-r2 doesn't build (needs QCA1 which I removed) - psi-0.11_pre20070314 builds and works - psi-0.11_rc1 doesn't build (I now have qca-2.0.0_beta7; do I need beta5? Fails with "error: ‘const class QCA::Certificate’ has no member named ‘matchesHostname’".) - psi-0.11_rc2 builds, but doesn't work (see comment #44) For now, I'm happy with psi-0.11_pre20070314 (no GnuPG ...), but I'm still not sure why RC2 doesn't work.
(In reply to comment #76) > (In reply to comment #68) > > (In reply to comment #67) > > > (In reply to comment #66) > > > > > > > > With RC2, the problem I described in comment #44 occurs again. Unfortunately, I > > > > have forgotten which patch the "attached patch" is. Please, can you give me a > > > > hint? Thanks :-) > > > > > > Try qca-2.0.0_beta7, qca-tls, qca-gnupg, qca-ossl from bug #129536. > > > > I already have qca-2.0.0_beta7, qca-gnupg and qca-ossl installed from bug > > #129536. qca-tls-1.0-r3 from the Portage tree is also installed. The error > > described in comment #44 is still present. > > With these libraries installed, I tested again with different versions of Psi. > The following happens at present: > > - psi-0.10-r2 doesn't build (needs QCA1 which I removed) > - psi-0.11_pre20070314 builds and works > - psi-0.11_rc1 doesn't build (I now have qca-2.0.0_beta7; do I need beta5? > Fails with "error: ‘const class QCA::Certificate’ has no member named > ‘matchesHostname’".) > - psi-0.11_rc2 builds, but doesn't work (see comment #44) > > For now, I'm happy with psi-0.11_pre20070314 (no GnuPG ...), but I'm still not > sure why RC2 doesn't work. > What's are yours USE flags on psi ebuid? # emerge -1av net-im/psi These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] net-im/psi-0.11_rc2 USE="crypt spell ssl xscreensaver -doc" 0 kB [1] Did you try the revdep-rebuild command?
(In reply to comment #77) > What's are yours USE flags on psi ebuid? > > # emerge -1av net-im/psi > > These are the packages that would be merged, in order: > > Calculating dependencies... done! > [ebuild R ] net-im/psi-0.11_rc2 USE="crypt spell ssl xscreensaver -doc" 0 > kB [1] # emerge -1av net-im/psi These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ] net-im/psi-0.11_rc2 [0.11_pre20070314] USE="crypt%* ssl -doc -spell -xscreensaver (-jingle%) (-plugins%) (-sasl%)" 0 kB [1] # Currently, I have 0.11_pre20070314 installed (see comment #76), that's why it looks so complicated. > Did you try the revdep-rebuild command? It's about the gcc (concerning gcj) and kdvi packages. I don't think that this is related, but I'm going to rebuild these packages nevertheless.
(In reply to comment #78) > (In reply to comment #77) > > What's are yours USE flags on psi ebuid? > > > > # emerge -1av net-im/psi > > > > These are the packages that would be merged, in order: > > > > Calculating dependencies... done! > > [ebuild R ] net-im/psi-0.11_rc2 USE="crypt spell ssl xscreensaver -doc" 0 > > kB [1] > > # emerge -1av net-im/psi > > These are the packages that would be merged, in order: > > Calculating dependencies... done! > [ebuild U ] net-im/psi-0.11_rc2 [0.11_pre20070314] USE="crypt%* ssl -doc > -spell -xscreensaver (-jingle%) (-plugins%) (-sasl%)" 0 kB [1] > > # > > Currently, I have 0.11_pre20070314 installed (see comment #76), that's why it > looks so complicated. > Could you try to build it with the same USR flags as I have?
(In reply to comment #79) > Could you try to build it with the same USR flags as I have? I just did so; the error still persists. :-( Any other ideas? Debugger?
(In reply to comment #76) > > With these libraries installed, I tested again with different versions of Psi. > The following happens at present: > > - psi-0.10-r2 doesn't build (needs QCA1 which I removed) > - psi-0.11_pre20070314 builds and works > - psi-0.11_rc1 doesn't build (I now have qca-2.0.0_beta7; do I need beta5? > Fails with "error: ‘const class QCA::Certificate’ has no member named > ‘matchesHostname’".) > - psi-0.11_rc2 builds, but doesn't work (see comment #44) > > For now, I'm happy with psi-0.11_pre20070314 (no GnuPG ...), but I'm still not > sure why RC2 doesn't work. > 0.11_rc1 needs qca-2.0.0_beta5. beta7 is needed since psi-0.11_pre20070708.
Created attachment 126746 [details] psi-0.11_pre20070801.ebuild Updated ebuild. Now uses new eqmake4 function from qt4.eclass to generate Makefiles rather then manually call qmake.
Created attachment 130417 [details] psi-0.11_pre20070909.ebuild Updated snapshot. It now requires latest qca-2 test release. I am maintaining an overlay for psi, qca2 and a few other ebuilds. If you are interested, please have a look at http://repo.or.cz/w/underlay.git
(In reply to comment #83) > Created an attachment (id=130417) [edit] > psi-0.11_pre20070909.ebuild > > Updated snapshot. It now requires latest qca-2 test release. > > I am maintaining an overlay for psi, qca2 and a few other ebuilds. If you are > interested, please have a look at http://repo.or.cz/w/underlay.git > David, I've tried to emerge psi-0.11_pre20070909 using your overlay and I got hundreds of "undefined reference" errors. Is it an old --as-needed bug? What will you advice? All errors are QCA related and look like this: .obj/psiaccount.o: In function `PsiAccount::pgp_signFinished()': psiaccount.cpp:(.text+0x12379): undefined reference to `QCA::SecureMessage::success() const' psiaccount.cpp:(.text+0x123b6): undefined reference to `QCA::SecureMessage::signature() const' psiaccount.cpp:(.text+0x124b2): undefined reference to `QCA::SecureMessage::errorCode() const' psiaccount.cpp:(.text+0x124dc): undefined reference to `QCA::PGPKey::keyId() const' psiaccount.cpp:(.text+0x12533): undefined reference to `QCA::KeyStoreEntry::isNull() const' psiaccount.cpp:(.text+0x1254a): undefined reference to `QCA::KeyStoreEntry::id() const' psiaccount.cpp:(.text+0x12593): undefined reference to `QCA::KeyStoreEntry::~KeyStoreEntry()' psiaccount.cpp:(.text+0x125a7): undefined reference to `QCA::KeyStoreEntry::~KeyStoreEntry()' psiaccount.cpp:(.text+0x125cb): undefined reference to `QCA::SecureMessage::errorCode() const'
(In reply to comment #84) > (In reply to comment #83) > > Created an attachment (id=130417) [edit] > > psi-0.11_pre20070909.ebuild > > > > Updated snapshot. It now requires latest qca-2 test release. > > > > I am maintaining an overlay for psi, qca2 and a few other ebuilds. If you are > > interested, please have a look at http://repo.or.cz/w/underlay.git > > > > David, I've tried to emerge psi-0.11_pre20070909 using your overlay and I got > hundreds of "undefined reference" errors. Is it an old --as-needed bug? What > will you advice? > Nope, I have a ~x86 box at home using --as-needed and psi emerges fine there. It looks more likely a non slot-aware qca1 version installed on your system. You should either remove =qca-1* or upgrade to qca-1.0-r3 which can be found in my overlay.
0.11_rc3 was released.
Stable Psi 0.11 will be released tomorrow.
(In reply to comment #87) > Stable Psi 0.11 will be released tomorrow. indeed they have :) quote: "Well, despite everything, we're finally releasing 0.11. There's not much to say here that isn't said in the release notes / readme which everyone is encouraged to read before upgrading. Windows installer: http://downloads.sourceforge.net/psi/psi-0.11-win-setup.exe Mac image: http://downloads.sourceforge.net/psi/Psi-0.11.dmg Source: http://downloads.sourceforge.net/psi/psi-0.11.tar.bz2 Other archives: http://sourceforge.net/project/showfiles.php? group_id=14635&package_id=53260&release_id=545913 Other packages will trickle in as they're available, I know that suse packages are ready thanks to Nikolay Derkach. Translations will be coming in shortly; unfortunately due to a failure in our translation process (and due to no fault of the translators themselves) these aren't ready yet, but will be coming in shortly I have no doubt. Happy release time :) /K " source: http://lists.affinix.com/pipermail/psi-devel-affinix.com/2007-October/007393.html
Created attachment 133650 [details] psi-0.11.ebuild We are now waiting for bug #129536...
Przemyslaw Maciag is on his honeymoon.So this will take some time. Sorry guys.
Psi uses qca-cyrus-sasl if it is available. Note that the current qca-cyrus-sasl plugin was released prior to kde-svn r723798 <http://websvn.kde.org/trunk/kdesupport/qca/plugins/qca-cyrus-sasl/qca-cyrus-sasl.cpp> and psi is affected by both problems.
*** Bug 198044 has been marked as a duplicate of this bug. ***
We've passed a full month that Psi 0.11 has been officially released and still no ebuild. Just making sure this hasn't fallen into a black hole...
Attachment 133650 [details] (psi-0.11.ebuild) does not work with the ebuilds from bug #129536. There's a bunch of QCA link errors.
Created attachment 136972 [details, diff] this patch removes all sly sotring and just takes first smile for iconselect. psi have built-in qca2 - why we don't use it? May be add USE=builtin-qca for it ? and small patch from http://forum.psi-im.org/thread/4235 - psi-iconselect-direct-order.patch
The linking problem seems to be GCC (Gentoo 4.1.2 p1.0.2) preferring the /usr/lib64/libqca.so over /usr/lib64/qca2/libqca.so despite the latter being in -L immediately before -lqca > psi have built-in qca2 - why we don't use it? Why don't we just static link our entire systems and have them use double the RAM and HD space?
hi, I'd like to ask ... what I understand from the comments, jingle support was removed - is there any way (er, I mean ebuild) to try psi with jingle support or do I have to follow the instructions at http://psi-im.org/wiki/Jingle_branch ?
Skype is available with qtstatic flag, I don't understand why Psi can't be. It could be masked as long as it works only with this flag. Crowds are waiting for Psi-0.11 in portage!! :)
(In reply to comment #98) > Skype is available with qtstatic flag, I don't understand why Psi can't be. It > could be masked as long as it works only with this flag. Crowds are waiting for > Psi-0.11 in portage!! :) sorry for such a big delays - my personal life didn't allow me to work on psi ebuild for some time. I now have some time to change that and I'll do my best! expect to see changes in short time :) Cheers, Przemek
Created attachment 138080 [details] psi-0.11.ebuild Ok. This should do the trick with slotted qca. psi makefiles are generated thrugh qmake and I'm not sure how order of certain libraries is created (I'll try to find out more from docs). IMPORTANT: new qca gnupog and ossl plugins are available. take ebuild from bug http://bugs.gentoo.org/show_bug.cgi?id=129536 and rename them to beta2. plz test and give me a sign is it works for you. PS. I'm going to test icon patch today! Cheers, Przemek
(In reply to comment #100) > > plz test and give me a sign is it works for you. > > PS. I'm going to test icon patch today! > > Cheers, > Przemek > seems to be it works... for me. thanks. & i'm add psi-iconselect-direct-order.patch how about jingle & plugins ?
(In reply to comment #101) > seems to be it works... for me. thanks. good! so I'm not the only one :) > & i'm add psi-iconselect-direct-order.patch ok. plz tell me - what this patch gives to psi? > how about jingle & plugins ? I'm testing them right now. _maybe_ I'll add them, but only as experimental... I have to see how much broken they are.
(In reply to comment #102) > > & i'm add psi-iconselect-direct-order.patch > ok. plz tell me - what this patch gives to psi? http://forum.psi-im.org/thread/4235 > > how about jingle & plugins ? > I'm testing them right now. _maybe_ I'll add them, but only as experimental... > I have to see how much broken they are. > jingle work for me ~year ago on x86, plugins just a framework at the moment... any way - thanks for you work :)
(In reply to comment #102) > (In reply to comment #101) > > > how about jingle & plugins ? > I'm testing them right now. _maybe_ I'll add them, but only as experimental... > I have to see how much broken they are. > AFAIK, public API for plugins isn't final yet and hasn't been officially released or announced. So I think that enabling plugins may not be a good idea...
> cd ${S}/src && eqmake4 src.pro > cd ${S} && eqmake4 ${PN}.pro This is not needed, qmake takes care of recursively running itself on *.pro files in subdirs, if you use the top-level Makefile generated by qmake. Running `eqmake4 ${PN}.pro` should be enough. Furthermore, why did you set dependencies for qca plugins to >=2.0.0_beta2? AFAIK, beta1 works fine too...
(In reply to comment #104) > AFAIK, public API for plugins isn't final yet and hasn't been officially > released or announced. So I think that enabling plugins may not be a good > idea... plugins aren't at final stage. but I think I'll make use of them, with big info that users are enabling it on their own. few plugins now exists and people are using them. as for jingle - official source tarball don't have them... I think I'll pass this one for now. (In reply to comment #105) > > cd ${S}/src && eqmake4 src.pro > > cd ${S} && eqmake4 ${PN}.pro > > This is not needed, qmake takes care of recursively running itself on *.pro > files in subdirs, if you use the top-level Makefile generated by qmake. Running > `eqmake4 ${PN}.pro` > should be enough. true, it should. I have to check one thing. maybe I try it now... > Furthermore, why did you set dependencies for qca plugins to >=2.0.0_beta2? > AFAIK, beta1 works fine too... since beta2 are out, there's no need to add beta1 to the tree. If it not brakes anything, I prefer newer betas.
(In reply to comment #106) > (In reply to comment #104) > > AFAIK, public API for plugins isn't final yet and hasn't been officially > > released or announced. So I think that enabling plugins may not be a good > > idea... > > plugins aren't at final stage. but I think I'll make use of them, with big info > that users are enabling it on their own. few plugins now exists and people are > using them. > > as for jingle - official source tarball don't have them... I think I'll pass > this one for now. Wise choice. ;) > > (In reply to comment #105) > > > cd ${S}/src && eqmake4 src.pro > > > cd ${S} && eqmake4 ${PN}.pro > > > > This is not needed, qmake takes care of recursively running itself on *.pro > > files in subdirs, if you use the top-level Makefile generated by qmake. Running > > `eqmake4 ${PN}.pro` > > should be enough. > > true, it should. I have to check one thing. maybe I try it now... > > > Furthermore, why did you set dependencies for qca plugins to >=2.0.0_beta2? > > AFAIK, beta1 works fine too... > > since beta2 are out, there's no need to add beta1 to the tree. If it not brakes > anything, I prefer newer betas. > Agreed.
(In reply to comment #100) Works fine for me, however every window appears at top left corner of the screen. Is this a Psi bug?
I've been testing this ebuild under x86 arch (under the Kde3 destkop, the window maker wm and even under kde4, altough not the one from portage) along the qca2-related ebuilds in the portage tree for some times. I didn't had any problem : compiled fine and is running nicely (I have no window positioning problem -- at least using the last stable qt4 release from portage). Nice work
Created attachment 141701 [details] psi-0.11.ebuild slightly modified ebuild. Mainly the mirror changed: $ diff -ruN temp/psi-0.11.ebuild /var/paludis/repositories/local/net-im/psi/psi-0.11.ebuild --- temp/psi-0.11.ebuild 2008-01-24 10:06:19.799761352 +0100 +++ /var/paludis/repositories/local/net-im/psi/psi-0.11.ebuild 2008-01-24 10:03:13.841164169 +0100 @@ -6,8 +6,7 @@ DESCRIPTION="QT 4.x Jabber Client, with Licq-like interface" HOMEPAGE="http://psi-im.org/" -SRC_URI="http://downloads.sourceforge.net/${PN}/${P}.tar.bz2" -RESTRICT="mirror" +SRC_URI="mirror://sourceforge/${PN}/${P}.tar.bz2" IUSE="crypt doc kernel_linux spell ssl xscreensaver" SLOT="0" @@ -31,18 +30,18 @@ QT4_BUILT_WITH_USE_CHECK="qt3support" src_compile() { - # growl is mac osx extension only - maybe someday we will want this + # disable growl as it is a mac osx extension only local myconf="--disable-growl --disable-bundled-qca" use kernel_linux || myconf="${myconf} --disable-dnotify" use ssl || myconf="${myconf} --disable-openssl" use spell || myconf="${myconf} --disable-aspell" use xscreensaver || myconf="${myconf} --disable-xss" - QTDIR=/usr/$(get_libdir) ./configure \ - --prefix=/usr ${myconf} \ - || die "configure failed" + # cannot use econf because of non-standard configure script + ./configure --disable-growl --disable-bundled-qca \ + --prefix=/usr --qtdir=/usr ${myconf} \ + || die "econf failed" - cd ${S}/src && eqmake4 src.pro cd ${S} && eqmake4 ${PN}.pro SUBLIBS="-L/usr/lib/qca2" emake || die "emake failed"
troll: would you mind, if I add the ebuild to the tree? It doesn't have any patches, as it seems to work fine without them. We might want to add an -r1 that will be a patched experimental version (jingle and stuff).
Created attachment 141702 [details] psi-0.11.ebuild nah.. never review ebuilds in a rush. this one is better. I have had some duplicate configure options in there. I also got rid of the multilib eclass as the configure script is 'intelligent' enough to find QT4 if you tell it only '--qtdir=/usr'.
(In reply to comment #112) use ssl || myconf="${myconf} --disable-openssl" This does not make sense with external qca. configure help says "--disable-openssl Disable use of OpenSSL (bundled QCA only)"
Created attachment 141704 [details] psi-0.11.ebuild yep, I did it wrong twice! .. too early in the morning ;-) but while I'm at it I read this in the configure options: --disable-openssl Disable use of OpenSSL (bundled QCA only) As we do not use the bundled QCA we can ignore that option. I dumped the check for ssl in $myconf and the dependency for openssl. psi does not link directly to openssl. ssl use flag is still needed to specify the dependency on app-crypt/qca-ossl though.
(In reply to comment #113) > (In reply to comment #112) > > use ssl || myconf="${myconf} --disable-openssl" > > This does not make sense with external qca. > configure help says "--disable-openssl Disable use of OpenSSL (bundled QCA > only)" > thanks. I just figured out myself. Just compile checked my latest changes.
(In reply to comment #115) > thanks. I just figured out myself. Just compile checked my latest changes. Worked for me.
Seems to works fine again. Maybe this should be placed in the portage tree -- hardmasked of course.
cd ${S} && eqmake4 ${PN}.pro cd ${S} isn't necessary, and should be quoted if used anyway. SUBLIBS="-L/usr/lib/qca2" Maybe "-L/usr/$(get_libdir)/qca2" ?
Created attachment 142261 [details] psi-0.11.ebuild good point. thanks, I've fixed it.
Created attachment 143041 [details] psi-0.11.ebuild psi 0.11 doesn't depend on libpng anymore. you need to build qt4 with png support psi and qt without png support gives: Iconset::load(): Couldn't load image/png graphic for the psi/appearance icon for the Crystal - System (default) iconset [...] --- psi-0.11.ebuild.old 2008-02-09 15:39:09.000000000 +0100 +++ psi-0.11.ebuild 2008-02-09 15:23:56.000000000 +0100 @@ -15,7 +15,6 @@ COMMON_DEPEND="$(qt4_min_version 4.2.3) =app-crypt/qca-2* - media-libs/libpng spell? ( app-text/aspell ) xscreensaver? ( x11-libs/libXScrnSaver )" @@ -26,7 +25,7 @@ crypt? ( >=app-crypt/qca-gnupg-2.0.0_beta2 ) ssl? ( >=app-crypt/qca-ossl-2.0.0_beta2 )" -QT4_BUILT_WITH_USE_CHECK="qt3support" +QT4_BUILT_WITH_USE_CHECK="qt3support png" src_compile() { # disable growl as it is a mac osx extension only
(In reply to comment #120) > psi 0.11 doesn't depend on libpng anymore. > you need to build qt4 with png support works fine here (on x86-arch). thx
works fine for me too ~amd64 I think this lines from /usr/portage/profiles/package.mask not need anymore # Stefan Schweizer <genstef@gentoo.org> (21 Aug 2006) # beta psi, with jingle support >=net-im/psi-0.11_alpha0 no such ebuild in portage tree
(In reply to comment #122) > works fine for me too > ~amd64 > > I think this lines from /usr/portage/profiles/package.mask > not need anymore > > # Stefan Schweizer <genstef@gentoo.org> (21 Aug 2006) > # beta psi, with jingle support > >=net-im/psi-0.11_alpha0 > > no such ebuild in portage tree > I just synced and there is always psi-0.11_pre20070314.ebuild in portage, a version which works very bad with current stable Qt version. But I agree those two should be removed.
Bumped.
Right now there is an ebuild for psi-0.11, but it doesn't have jingle USE flag. Does anybody know if jingle is supported or dropped in current psi?
(In reply to comment #125) > Right now there is an ebuild for psi-0.11, but it doesn't have jingle USE flag. > Does anybody know if jingle is supported or dropped in current psi? > AFAIK, it's still experimental and thus NOT supported.
The error <<has different size in shared object, consider re-linking>> can be fixed by remergint the package owning the file. See bug 338347 . The issue is not in the app, but in portage 2.2, or in revdep-rebuild.
