From nix at go-nix.ca Sun Jul 1 12:10:16 2007 From: nix at go-nix.ca (Gabriel Schulhof) Date: Sun, 1 Jul 2007 19:10:16 +0300 (EEST) Subject: [OTR-dev] Hang during key generation Message-ID: <60587.88.113.2.57.1183306216.squirrel@go-nix.ca> Hi! I've started to hack on a Maemo port for pidgin-otr, and I've run into my first hurdle: When I push the "Generate" button int the config dialog, it causes Pidgin to hang. I have stepped through both pidgin-otr and libotr and the crucial call seems to be privkey.c:414: gcry_pk_genkey(&key, parms); This hangs in such a way that there's no CPU activity and, when I interrupt the process, it tells me it's inside select() - so, waiting for events, I assume. Now, I realize that's inside libgcrypt and not libotr, but I'm just wondering if someone on this list has encountered this behaviour before, and if so, what the resolution towards successful key creation was. TIA for your help, Gabriel From nix at go-nix.ca Sun Jul 1 14:59:41 2007 From: nix at go-nix.ca (Gabriel Schulhof) Date: Sun, 1 Jul 2007 21:59:41 +0300 (EEST) Subject: [OTR-dev] Patch: cleaner account option menu Message-ID: <61350.88.113.2.57.1183316381.squirrel@go-nix.ca> Hi! The attached patch makes use of the functions pidgin_account_option_menu_get_selected() and g_signal_emit_by_name() to greatly reduce the code required for dealing with pidgin-otr's accounts combo. HTH, Gabriel -------------- next part -------------- A non-text attachment was scrubbed... Name: omgp.account-menu-fix.diff Type: text/x-patch Size: 2998 bytes Desc: not available URL: From nix at go-nix.ca Sun Jul 1 15:24:03 2007 From: nix at go-nix.ca (Gabriel Schulhof) Date: Sun, 1 Jul 2007 22:24:03 +0300 (EEST) Subject: [OTR-dev] (Better) patch: cleaner account option menu In-Reply-To: <61350.88.113.2.57.1183316381.squirrel@go-nix.ca> References: <61350.88.113.2.57.1183316381.squirrel@go-nix.ca> Message-ID: <61449.88.113.2.57.1183317843.squirrel@go-nix.ca> Hi! Always happens ... please find a lower-impact patch attached. HTH, Gabriel -------------- next part -------------- A non-text attachment was scrubbed... Name: omgp.account-menu-fix.minimal.diff Type: text/x-patch Size: 1693 bytes Desc: not available URL: From nix at go-nix.ca Sun Jul 1 15:35:46 2007 From: nix at go-nix.ca (Gabriel Schulhof) Date: Sun, 1 Jul 2007 22:35:46 +0300 (EEST) Subject: [OTR-dev] (Better) patch: cleaner account option menu In-Reply-To: <61449.88.113.2.57.1183317843.squirrel@go-nix.ca> References: <61350.88.113.2.57.1183316381.squirrel@go-nix.ca> <61449.88.113.2.57.1183317843.squirrel@go-nix.ca> Message-ID: <61506.88.113.2.57.1183318546.squirrel@go-nix.ca> Hi! Forgot to remove item_get_account(). Sorry. Gabriel -------------- next part -------------- A non-text attachment was scrubbed... Name: omgp.account-menu-fix.minimal.diff Type: text/x-patch Size: 1766 bytes Desc: not available URL: From ian at cypherpunks.ca Sun Jul 1 17:22:26 2007 From: ian at cypherpunks.ca (Ian Goldberg) Date: Sun, 1 Jul 2007 17:22:26 -0400 Subject: [OTR-dev] Hang during key generation In-Reply-To: <60587.88.113.2.57.1183306216.squirrel@go-nix.ca> References: <60587.88.113.2.57.1183306216.squirrel@go-nix.ca> Message-ID: <20070701212226.GA5757@yoink.cs.uwaterloo.ca> On Sun, Jul 01, 2007 at 07:10:16PM +0300, Gabriel Schulhof wrote: > Hi! > > I've started to hack on a Maemo port for pidgin-otr, and I've run into my > first hurdle: > > When I push the "Generate" button int the config dialog, it causes Pidgin > to hang. I have stepped through both pidgin-otr and libotr and the crucial > call seems to be > > privkey.c:414: gcry_pk_genkey(&key, parms); > > This hangs in such a way that there's no CPU activity and, when I > interrupt the process, it tells me it's inside select() - so, waiting for > events, I assume. Now, I realize that's inside libgcrypt and not libotr, > but I'm just wondering if someone on this list has encountered this > behaviour before, and if so, what the resolution towards successful key > creation was. > > TIA for your help, It's gathering randomness from /dev/random. Normally, the kernel will block reads until some randomish events happen (mouse moves, disk reads, etc.). I don't know what the Maemo does for randomness. If all else fails, change libgcrypt to read from /dev/urandom instead; you'll get cryptographic randomness instead of entropic randomness, but in all honesty, that's usually good enough. - Ian From ian at cypherpunks.ca Sun Jul 1 17:25:20 2007 From: ian at cypherpunks.ca (Ian Goldberg) Date: Sun, 1 Jul 2007 17:25:20 -0400 Subject: [OTR-dev] (Better) patch: cleaner account option menu In-Reply-To: <61506.88.113.2.57.1183318546.squirrel@go-nix.ca> References: <61350.88.113.2.57.1183316381.squirrel@go-nix.ca> <61449.88.113.2.57.1183317843.squirrel@go-nix.ca> <61506.88.113.2.57.1183318546.squirrel@go-nix.ca> Message-ID: <20070701212520.GB5757@yoink.cs.uwaterloo.ca> On Sun, Jul 01, 2007 at 10:35:46PM +0300, Gabriel Schulhof wrote: > Hi! > > Forgot to remove item_get_account(). Sorry. Thanks. I'll check it out. - Ian From nix at go-nix.ca Mon Jul 2 00:10:15 2007 From: nix at go-nix.ca (Gabriel Schulhof) Date: Mon, 2 Jul 2007 07:10:15 +0300 (EEST) Subject: [OTR-dev] Hang during key generation In-Reply-To: <20070701212226.GA5757@yoink.cs.uwaterloo.ca> References: <60587.88.113.2.57.1183306216.squirrel@go-nix.ca> <20070701212226.GA5757@yoink.cs.uwaterloo.ca> Message-ID: <60537.88.113.2.57.1183349415.squirrel@go-nix.ca> Hi! On Mon, July 2, 2007 00:22, Ian Goldberg wrote: > It's gathering randomness from /dev/random. Normally, the kernel will > block reads until some randomish events happen (mouse moves, disk reads, > etc.). That's what I figured out later on. I also found that libgcrypt can be passed a progress function pointer that is then called with parameters indicating what libgcrypt needs and what it's doing and how complete it is: void gcry_set_progress_handler (gcry_handler_progress_t CB, void *CB_DATA); where void (*gcry_handler_progress_t) (void *, const char *, int, int, int); I'm thinking about putting a wrapper for this mechanism into libotr, so I can in turn pass a function pointer to libotr and not only make the "Please wait" dialog responsive (by executing while(g_main_context_iteration(NULL, FALSE)); inside the progress handler), but also maybe add a "Cancel" option. However, before I proceed I need to study the code for both pidgin-otr and libotr a little further, because I need to see all the uses pidgin-otr makes of libotr and which of those uses involve long operations. I also need to see just how often libgcrypt calls the progress handler, since libgcrypt itself doesn't do the select() inside a main loop :o( I will try to experiment with these things. If the progress indicator works as advertised, it might even tell what kinds of things are considered sources of randomness on Maemo. Cheers, Gabriel From ian at cypherpunks.ca Sat Jul 7 16:13:25 2007 From: ian at cypherpunks.ca (Ian Goldberg) Date: Sat, 7 Jul 2007 16:13:25 -0400 Subject: [OTR-dev] [Patch] Internationalisation for gaim-otr In-Reply-To: <45CF4F8D.60308@gmx.net> References: <45CF4F8D.60308@gmx.net> Message-ID: <20070707201325.GU5757@yoink.cs.uwaterloo.ca> On Sun, Feb 11, 2007 at 06:17:01PM +0100, Thomas B. wrote: > A few days ago, there was a discussion on otr-users about the > translation of OTR, and I've commited to implement > internationalisation support. Here's the first result: I've attached a > tarball containing a patch with the changes I made to gaim-otr and > also some new files that should go into the new po/ subdirectory. I > was able to compile and run the patched gaim-otr on my Ubuntu 6.10 > system with a Gaim 2.0.0beta6 (compiled from source) as well as on > Windows (see below). Please test it for yourselves and send me results > and comments. So that people are aware: I just i18n'd pidgin-otr (based on this patch). There are still constant strings in libotr, and the plan is still to turn those into enums that the application will be responsible for displaying. That should happen for 4.0.0, but there is likely to be a 3.1.0 pretty soon, with pidgin-otr, but not libotr, i18n'd. - Ian From donny.viszneki at gmail.com Mon Jul 16 23:15:49 2007 From: donny.viszneki at gmail.com (Donny Viszneki) Date: Mon, 16 Jul 2007 23:15:49 -0400 Subject: [OTR-dev] gmail spam Message-ID: <44acbb800707162015g7613ec6fia794ba67eef50afc@mail.gmail.com> Just thought I'd point out that Gmail has begun marking some OTR-dev mailing list messages as spam. The list is at the URL below so you can make sure your spam filter isn't hitting OTR-dev too: http://metascape.afraid.org:13666/~donny/gmail-otr-spam.png From ian at cypherpunks.ca Tue Jul 17 18:15:19 2007 From: ian at cypherpunks.ca (Ian Goldberg) Date: Tue, 17 Jul 2007 18:15:19 -0400 Subject: [OTR-dev] gmail spam In-Reply-To: <44acbb800707162015g7613ec6fia794ba67eef50afc@mail.gmail.com> References: <44acbb800707162015g7613ec6fia794ba67eef50afc@mail.gmail.com> Message-ID: <20070717221519.GV3751@yoink.cs.uwaterloo.ca> On Mon, Jul 16, 2007 at 11:15:49PM -0400, Donny Viszneki wrote: > Just thought I'd point out that Gmail has begun marking some OTR-dev > mailing list messages as spam. The list is at the URL below so you can > make sure your spam filter isn't hitting OTR-dev too: > > http://metascape.afraid.org:13666/~donny/gmail-otr-spam.png I don't use gmail; is there a way to tell why gmail thinks otr-dev is spam? - Ian From nikita at uiuc.edu Tue Jul 17 18:28:44 2007 From: nikita at uiuc.edu (Nikita Borisov) Date: Tue, 17 Jul 2007 17:28:44 -0500 Subject: [OTR-dev] gmail spam In-Reply-To: <20070717221519.GV3751@yoink.cs.uwaterloo.ca> References: <44acbb800707162015g7613ec6fia794ba67eef50afc@mail.gmail.com> <20070717221519.GV3751@yoink.cs.uwaterloo.ca> Message-ID: <16f0378d0707171528l384ff092gc472c65ab5da1557@mail.gmail.com> On 7/17/07, Ian Goldberg wrote: > I don't use gmail; is there a way to tell why gmail thinks otr-dev is > spam? Not really, it's "magic". I think it's personalized based on your incoming mail, though -- otr-dev wasn't marked as spam for me. - Nikita -- Nikita Borisov - http://www.crhc.uiuc.edu/~nikita/ Assistant Professor, Electrical and Computer Engineering Tel: (217) 244-5385, Office: 460 CSL From cactusthesaint at yahoo.com Tue Jul 17 18:34:10 2007 From: cactusthesaint at yahoo.com (Cactus The Saint) Date: Tue, 17 Jul 2007 15:34:10 -0700 (PDT) Subject: [OTR-dev] gmail spam Message-ID: <993168.32745.qm@web55205.mail.re4.yahoo.com> FWIW, Yahoo mail often marks [OTR-dev] as spam as well. ----- Original Message ---- From: Ian Goldberg To: otr-dev at lists.cypherpunks.ca Sent: Tuesday, July 17, 2007 3:15:19 PM Subject: Re: [OTR-dev] gmail spam On Mon, Jul 16, 2007 at 11:15:49PM -0400, Donny Viszneki wrote: > Just thought I'd point out that Gmail has begun marking some OTR-dev > mailing list messages as spam. The list is at the URL below so you can > make sure your spam filter isn't hitting OTR-dev too: > > http://metascape.afraid.org:13666/~donny/gmail-otr-spam.png I don't use gmail; is there a way to tell why gmail thinks otr-dev is spam? - Ian _______________________________________________ OTR-dev mailing list OTR-dev at lists.cypherpunks.ca http://lists.cypherpunks.ca/mailman/listinfo/otr-dev ____________________________________________________________________________________ Never miss an email again! Yahoo! Toolbar alerts you the instant new Mail arrives. http://tools.search.yahoo.com/toolbar/features/mail/ From stpeter at jabber.org Tue Jul 17 18:40:12 2007 From: stpeter at jabber.org (Peter Saint-Andre) Date: Tue, 17 Jul 2007 16:40:12 -0600 Subject: [OTR-dev] gmail spam In-Reply-To: <993168.32745.qm@web55205.mail.re4.yahoo.com> References: <993168.32745.qm@web55205.mail.re4.yahoo.com> Message-ID: <469D454C.1090100@jabber.org> Cactus The Saint wrote: > On Mon, Jul 16, 2007 at 11:15:49PM -0400, Donny Viszneki wrote: >> Just thought I'd point out that Gmail has begun marking some OTR-dev >> mailing list messages as spam. > > FWIW, Yahoo mail often marks [OTR-dev] as spam as well. > The paranoid among us might conclude that perhaps Yahoo and Google don't want people sending encrypted messages through their services. ;-) /psa -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 7354 bytes Desc: S/MIME Cryptographic Signature URL: From aoeuid at gmail.com Tue Jul 17 18:50:03 2007 From: aoeuid at gmail.com (Andri) Date: Wed, 18 Jul 2007 01:50:03 +0300 Subject: [OTR-dev] gmail spam In-Reply-To: <16f0378d0707171528l384ff092gc472c65ab5da1557@mail.gmail.com> References: <44acbb800707162015g7613ec6fia794ba67eef50afc@mail.gmail.com> <20070717221519.GV3751@yoink.cs.uwaterloo.ca> <16f0378d0707171528l384ff092gc472c65ab5da1557@mail.gmail.com> Message-ID: <469D479B.2000902@gmail.com> Nikita Borisov wrote: > On 7/17/07, Ian Goldberg wrote: >> I don't use gmail; is there a way to tell why gmail thinks otr-dev is >> spam? > > Not really, it's "magic". I think it's personalized based on your > incoming mail, though -- otr-dev wasn't marked as spam for me. > > - Nikita I've occasionally found both messages to this list and to the NFS list in my GMails SPAMbox. I'm certain this is because any encryption to personal messages makes it harder for Google to collect private information and design The Matrix in the future ;) And NFS is just in the way of bringing GoogleFS to the masses! Perhaps someone has been actively marking some list-messages as SPAM, and GMail, in its trusting state, applied similar conclusions to the messages of others. Even though the possibility of false-positives is big, it seems like a smart way to design SPAM-filters used by many. Spamrank, if you will. From aoeuid at gmail.com Wed Jul 18 02:58:45 2007 From: aoeuid at gmail.com (Andri) Date: Wed, 18 Jul 2007 09:58:45 +0300 Subject: [OTR-dev] gmail spam In-Reply-To: <44acbb800707172031t3a13c316h3362ead78fe6f763@mail.gmail.com> References: <44acbb800707162015g7613ec6fia794ba67eef50afc@mail.gmail.com> <20070717221519.GV3751@yoink.cs.uwaterloo.ca> <16f0378d0707171528l384ff092gc472c65ab5da1557@mail.gmail.com> <469D479B.2000902@gmail.com> <44acbb800707172031t3a13c316h3362ead78fe6f763@mail.gmail.com> Message-ID: <469DBA25.7090708@gmail.com> I've seen the mentioned lists marked as SPAM long before I heard the news about Hotmail's CAPTCHAs. But SPAM *has* changed its tactics -- I've even seen subjects similar to Bugzilla bugreports now. Like geeks are the perfect target for body-part enlargement ads. Or maybe they were about dating services... didn't check. Would make more sense though :) I've also pressed the "Not spam" button for each misplaced message, hoping that GMail would learn. But who knows -- it's a closed source system :P Donny Viszneki wrote: > Matrix and Skynet aside, I think most email servers are marking spam > more often because Microsoft and Yahoo captchas have recently been > compromised, increasing the amount of total spam out there. It costs > money to filter it all, the most cost effective way has been to > identify abusive email sources, but you can't just blacklist Hotmail > and Yahoo. > > Maybe Gmail and/or Yahoo have a "whitelist" feature? > > On 7/17/07, Andri wrote: >> Nikita Borisov wrote: >> > On 7/17/07, Ian Goldberg wrote: >> >> I don't use gmail; is there a way to tell why gmail thinks otr-dev is >> >> spam? >> > >> > Not really, it's "magic". I think it's personalized based on your >> > incoming mail, though -- otr-dev wasn't marked as spam for me. >> > >> > - Nikita >> >> I've occasionally found both messages to this list and to the NFS list >> in my >> GMails SPAMbox. >> I'm certain this is because any encryption to personal messages makes >> it harder >> for Google to collect private information and design The Matrix in the >> future ;) >> And NFS is just in the way of bringing GoogleFS to the masses! >> >> Perhaps someone has been actively marking some list-messages as SPAM, >> and GMail, >> in its trusting state, applied similar conclusions to the messages of >> others. >> Even though the possibility of false-positives is big, it seems like a >> smart way >> to design SPAM-filters used by many. Spamrank, if you will. >> _______________________________________________ >> OTR-dev mailing list >> OTR-dev at lists.cypherpunks.ca >> http://lists.cypherpunks.ca/mailman/listinfo/otr-dev >> > From bdesham at gmail.com Wed Jul 18 09:46:18 2007 From: bdesham at gmail.com (Benjamin Esham) Date: Wed, 18 Jul 2007 13:46:18 +0000 (UTC) Subject: [OTR-dev] Re: [meta] Can we add this mailing list to Gmane? References: <77D4ED68-E317-4DD5-B135-E1C081E488E8@gmail.com> <20070702032346.GE5757@yoink.cs.uwaterloo.ca> Message-ID: Benjamin Esham wrote: > I've gone ahead and added all three lists. OTR-users and -dev are > "non-public", which means that only list subscribers can post through > Gmane. OTR-announce is "read-only", so that no one can post to it through > Gmane. I'm pleased to announce that otr-users, otr-dev, and otr-announce are now available on Gmane as gmane.comp.security.otr.user, .devel, and .announce, respectively. (This is different from the previous announcement in that the list archives are now available through Gmane as well.) Information on using Gmane can be found at http://www.gmane.org and http://www.gmane.org/faq.php. Please note that, as before, you must be a registered user of the mailing lists in order to post. Enjoy! -- Benjamin D. Esham E-mail/Jabber: bdesham at gmail.com | AIM bdesham128 | PGP D676BB9A "Men never do evil so completely and cheerfully as when they do it from religious conviction." ? Blaise Pascal From gdt at ir.bbn.com Tue Jul 24 14:19:22 2007 From: gdt at ir.bbn.com (Greg Troxel) Date: Tue, 24 Jul 2007 14:19:22 -0400 Subject: [OTR-dev] finished converstations a bad UI choice! Message-ID: I'm writing, perhaps again, about what I consider to be a serious UI bug with finished conversations. Actual scenario: I have a private conversation with Alice. Both of us use gaim and gaim-otr with jabber. Alice's client is probably set to 'require OTR' for me. At least I've had the same behavior on my end when talking to someone else, when I have 'require OTR' set. I shut down my client. This sends a 'finished' message, putting Alice's client in state finished for me. Alice (who doesn't follow otr-dev and understand the nuances of why it's bad to send cleartext when she might expect encrypted) tries to send something, typing a sentence and hitting return. She gets something like 'message not sent; please cancel or restart' and concludes (correctly!) that the IM system is broken. Now, I realize that sending the message in the clear would be a security problem, as she could expect confidentiality and then not get it. So let me be very clear that I'm not asking for that. There are then two cases: OTR is enabled, with automatic initiation, but not required) Here, we know that OTR recently worked with this peer. So choices are 0) send in clear - dangerous, violates user expectations 1) fail (current behavior) 2) try to initiate, and send message if negotatiation is successful OTR is enabled, with automatic initiation, and further is required) Here, there are two choices 0) send in clear - against stated policy, dangerous 1) fail 2) try to initiate, and send message if negotatiation is successful In the required case, note that these are the same options as in a "not private" state. But in "not private", otr-gaim does option 2, which is useful and what the user expects. In the 'not required' case, option 2 seems preferred - a savvy user can always 'end private' if that's what they want. I have no objection to "Conversation is in state finished; trying to initiate private conversation" message. I realize this is work to change. But does anyone really think that the current behavior is useful and reasonable? To me it's gratuitously difficult when there's a better behavior without security problems. From ian at cypherpunks.ca Tue Jul 24 16:11:04 2007 From: ian at cypherpunks.ca (Ian Goldberg) Date: Tue, 24 Jul 2007 16:11:04 -0400 Subject: [OTR-dev] libotr and pidgin-otr 3.1.0-preview1 available Message-ID: <20070724201104.GN23980@thunk.cs.uwaterloo.ca> Boy, has this been a long time coming. See what happens when Real Life gets in the way? Luckily, I was recently able to get part of said life to be working on OTR (along with an additional developer). For the impatient: http://otr.cypherpunks.ca/libotr-3.1.0-preview1.tar.gz http://otr.cypherpunks.ca/pidgin-otr-3.1.0-preview1.tar.gz [Also on sourceforge's cvs.] The major changes: - Added fragmentation support for large messages - Added an option to turn off logging of OTR conversations - Internationalization of the pidgin-otr part (but not yet the libotr part) - Makefile.static builds pidgin-otr.so with libgcrypt.so linked statically to avoid the libgcrypt multiple-clients bug. (At least on Linux; I can't vouch for how well that Makefile will work on other OSes.) And the coolest one: - Added the ability to authenticate your buddies without ever having to see the word "fingerprint", or an obnoxious string of hex chars. The old "verify fingerprint" dialog is still available behind an "Advanced..." button, if needed (for communicating with old clients, say). Anyone want to help with the i18n translations? Here's the pot file: http://otr.cypherpunks.ca/pidgin-otr.pot Please post as to what language you want to take, so we don't duplicate effort. I've got French lined up, and I think Paul offered Dutch? I seem to remember someone offered German? The point of this preview version is mainly for package maintainers to tell me what I've messed up as far as packaging / portability go. The sooner I get feedback in that area, the sooner the "real" 3.1.0 release will be there. Note that the online help files aren't quite ready yet, but will be in place sometime this week. Have fun! - Ian From paul at cypherpunks.ca Wed Jul 25 13:14:29 2007 From: paul at cypherpunks.ca (Paul Wouters) Date: Wed, 25 Jul 2007 13:14:29 -0400 (EDT) Subject: [OTR-dev] libotr and pidgin-otr 3.1.0-preview1 available In-Reply-To: <20070724201104.GN23980@thunk.cs.uwaterloo.ca> References: <20070724201104.GN23980@thunk.cs.uwaterloo.ca> Message-ID: On Tue, 24 Jul 2007, Ian Goldberg wrote: > Anyone want to help with the i18n translations? Here's the pot file: > > http://otr.cypherpunks.ca/pidgin-otr.pot > > Please post as to what language you want to take, so we don't duplicate > effort. I've got French lined up, and I think Paul offered Dutch? > I seem to remember someone offered German? I am covering Dutch, German, Polish and Spanish so far. How should non-ascii text be inputted? Should it use HTML encoding or utf8? (eg should it be ?? or ó ? Paul From ian at cypherpunks.ca Wed Jul 25 14:32:33 2007 From: ian at cypherpunks.ca (Ian Goldberg) Date: Wed, 25 Jul 2007 14:32:33 -0400 Subject: [OTR-dev] libotr and pidgin-otr 3.1.0-preview1 available In-Reply-To: References: <20070724201104.GN23980@thunk.cs.uwaterloo.ca> Message-ID: <20070725183233.GJ5484@thunk.cs.uwaterloo.ca> On Wed, Jul 25, 2007 at 01:14:29PM -0400, Paul Wouters wrote: > On Tue, 24 Jul 2007, Ian Goldberg wrote: > > > Anyone want to help with the i18n translations? Here's the pot file: > > > > http://otr.cypherpunks.ca/pidgin-otr.pot > > > > Please post as to what language you want to take, so we don't duplicate > > effort. I've got French lined up, and I think Paul offered Dutch? > > I seem to remember someone offered German? > > I am covering Dutch, German, Polish and Spanish so far. How should > non-ascii text be inputted? Should it use HTML encoding or utf8? (eg > should it be ?? or ó ? UTF-8. Thanks! - Ian From paul at cypherpunks.ca Wed Jul 25 16:00:37 2007 From: paul at cypherpunks.ca (Paul Wouters) Date: Wed, 25 Jul 2007 16:00:37 -0400 (EDT) Subject: [OTR-dev] libotr and pidgin-otr 3.1.0-preview1 available In-Reply-To: <20070724201104.GN23980@thunk.cs.uwaterloo.ca> References: <20070724201104.GN23980@thunk.cs.uwaterloo.ca> Message-ID: On Tue, 24 Jul 2007, Ian Goldberg wrote: > http://otr.cypherpunks.ca/libotr-3.1.0-preview1.tar.gz Spec file needs some minor tweaks. diff attached. rpmlint then still gives the following error: E: libotr binary-or-shlib-defines-rpath /usr/bin/otr_mackey ['/usr/lib64'] E: libotr binary-or-shlib-defines-rpath /usr/bin/otr_sesskeys ['/usr/lib64'] E: libotr binary-or-shlib-defines-rpath /usr/bin/otr_modify ['/usr/lib64'] E: libotr binary-or-shlib-defines-rpath /usr/bin/otr_remac ['/usr/lib64'] E: libotr binary-or-shlib-defines-rpath /usr/bin/otr_parse ['/usr/lib64'] E: libotr binary-or-shlib-defines-rpath /usr/bin/otr_readforge ['/usr/lib64'] I am not sure how to resolve these.... A build in mock succeeded though, so the above is the only error that needs fixing for this package. > http://otr.cypherpunks.ca/pidgin-otr-3.1.0-preview1.tar.gz This one failed to configure: checking for libgcrypt-config... /usr/bin/libgcrypt-config checking for LIBGCRYPT - version >= 1.2.0... yes checking LIBGCRYPT API version... okay checking for libotr CFLAGS... checking for libotr LIBS... -lotr checking for libotr headers version 3.x >= 3.1.0... found. checking for otrl_message_receiving in -lotr... yes checking for x86_64-redhat-linux-gnu-pkg-config... no checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for EXTRA... configure: error: glib ./configure: line 19127: exit: gtk: numeric argument required ./configure: line 19127: exit: gtk: numeric argument required error: Bad exit status from /var/tmp/rpm-tmp.27228 (%build) I think this is a missing build dependancy which we didn't catch? The configure line used by rpm was: ./configure --build=x86_64-redhat-linux-gnu --host=x86_64-redhat-linux-gnu --target=x86_64-redhat-linux-gnu --program-prefix= --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib64 --libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/usr/com --mandir=/usr/share/man --infodir=/usr/share/info Paul -------------- next part -------------- 3c3 < Version: 3.0.0 --- > Version: 3.1.0 5c5 < License: GPL, LGPL --- > License: GPL and LGPL 12c12 < Requires: libgcrypt >= 1.2.0, libgpg-error --- > Requires: libgcrypt >= 1.2.0, 35c35 < %configure --with-pic --- > %configure --with-pic --disable-rpath 71c71,74 < * Mon Oct 17 2005 Paul Wouters 3.0.0 --- > * Wed Jul 25 2007 Paul Wouters 3.1.0-1 > - Upgraded to current version > > * Mon Oct 17 2005 Paul Wouters 3.0.0-1 81a85 > 83a88 > 85a91 > 88a95 > 90a98 > 92a101 > 94a104 > 96a107 > 98a110 > 100a113 > 102a116 > 104a119 > 108a124 > From paul at cypherpunks.ca Wed Jul 25 16:01:19 2007 From: paul at cypherpunks.ca (Paul Wouters) Date: Wed, 25 Jul 2007 16:01:19 -0400 (EDT) Subject: [OTR-dev] pidgin-otr.nl.po In-Reply-To: <20070724201104.GN23980@thunk.cs.uwaterloo.ca> References: <20070724201104.GN23980@thunk.cs.uwaterloo.ca> Message-ID: On Tue, 24 Jul 2007, Ian Goldberg wrote: Attached is the Dutch translation for gaim-otr. Paul From paul at xelerance.com Wed Jul 25 16:55:11 2007 From: paul at xelerance.com (Paul Wouters) Date: Wed, 25 Jul 2007 16:55:11 -0400 (EDT) Subject: [OTR-dev] pidgin-otr.nl.po In-Reply-To: References: <20070724201104.GN23980@thunk.cs.uwaterloo.ca> Message-ID: On Wed, 25 Jul 2007, Paul Wouters wrote: > Subject: [OTR-dev] pidgin-otr.nl.po > > Attached is the Dutch translation for gaim-otr. Hmm, no attachment found? Trying again... Paul -------------- next part -------------- # SOME DESCRIPTIVE TITLE. # Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER # This file is distributed under the same license as the PACKAGE package. # FIRST AUTHOR , YEAR. # #, fuzzy msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2007-07-24 15:47-0400\n" "PO-Revision-Date: 2007-07-25 12:41+EDT\n" "Last-Translator: Paul Wouters \n" "Language-Team: LANGUAGE \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=CHARSET\n" "Content-Transfer-Encoding: 8bit\n" #: ../gtk-dialog.c:913 ../gtk-dialog.c:2095 msgid "_What's this?" msgstr "Wat betekent dit?" #: ../gtk-dialog.c:924 msgid "_More..." msgstr "Meer..." #. Create the Advanced... button, and left-justify it. This #. * involves adding the button, and a blank label as a spacer, and #. * reordering them so that they're at the beginning. #: ../gtk-dialog.c:980 msgid "Advanced..." msgstr "geavanceerd" #: ../gtk-dialog.c:1025 msgid "Enter secret here" msgstr "Voer de geheime code hier in" #: ../gtk-dialog.c:1030 msgid "This buddy is already authenticated." msgstr "Deze friend is al ge-authentificeerd" #: ../gtk-dialog.c:1049 msgid "" "To authenticate, pick a secret known only to you and your buddy. Enter this " "secret, then wait for your buddy to enter it too. If the secrets don't " "match, then you may be talking to an imposter." msgstr "Om te authoriseren dien je een geheime code te bedenken die alleen " "jij en je vriend kennen. Voer dit geheim in, en wacht op je vriend om " "hetzelfde te doen. Als de geheimen niet overeenkomen, dan kun je te maken " "hebben met een bedrieger." #: ../gtk-dialog.c:1053 msgid "" "If your buddy uses multiple IM accounts or multiple computers, you may have " "to authenticate multiple times. However, as long as they use an account and " "computer that you've seen before, you don't need to authenticate each " "individual conversation." msgstr "Als je vriend meerdere IM accounts of meerdere computers gebruikt, kan " "het zijn dat je meerdere keren moet authenticeren. Zolang je vriend een account " " of een computer gebruikt die je al eerder gezien hebt, hoef je niet elke " " individueel gesprek apart te authenticeren." #: ../gtk-dialog.c:1058 ../gtk-dialog.c:1322 ../gtk-dialog.c:1326 #: ../gtk-dialog.c:1423 ../gtk-dialog.c:1590 ../gtk-dialog.c:1750 #: ../gtk-dialog.c:1850 ../gtk-dialog.c:1935 msgid "?lang=en" msgstr "?lang=nl" #: ../gtk-dialog.c:1059 msgid "Click here for more information about authentication in OTR." msgstr "Klik hier voor meer informatie over OTR authenticatie" #: ../gtk-dialog.c:1063 msgid "" "Authenticating a buddy helps ensure that the person you are talking to is " "who they claim to be." msgstr "Door middel van het authenticeren van een vriend kun je gegarandeerd " "weten dat de persoon waarmee je praat, daadwerkelijk je vriend is." #: ../gtk-dialog.c:1113 msgid "Authenticating Buddy" msgstr "Vriend authenticatie" #: ../gtk-dialog.c:1140 msgid "Authenticating" msgstr "Authenticeren" #: ../gtk-dialog.c:1201 msgid "Generating private key" msgstr "Geheime sleutel aan het genereren" #: ../gtk-dialog.c:1202 msgid "Please wait" msgstr "Een moment a.u.b." #: ../gtk-dialog.c:1210 ../gtk-dialog.c:1627 ../gtk-dialog.c:1664 #: ../gtk-ui.c:175 ../otr-plugin.c:115 ../otr-plugin.c:212 ../ui.c:110 msgid "Unknown" msgstr "" #. Create the Please Wait... dialog #: ../gtk-dialog.c:1213 #, c-format msgid "Generating private key for %s (%s)..." msgstr "Geheime sleutel voor %s (%s) aan het genereren..." #: ../gtk-dialog.c:1258 #, c-format msgid "%s Done." msgstr "%s Klaar" #: ../gtk-dialog.c:1320 #, c-format msgid "" "%s is contacting you from an unrecognized computer. You should authenticate this buddy." msgstr "%s zoekt contact met je vanaf een onherkenbare computer. Je kunt het beste " "deze vriend authenticeren." #: ../gtk-dialog.c:1324 #, c-format msgid "" "%s has not been authenticated yet. You should authenticate this buddy." msgstr "%s is nog niet ge-authenticeerd. Je kunt het beste " "deze vriend authenticeren." #: ../gtk-dialog.c:1365 ../gtk-ui.c:76 msgid "Finished" msgstr "Klaar" #: ../gtk-dialog.c:1366 ../gtk-ui.c:75 msgid "Private" msgstr "Besloten" #: ../gtk-dialog.c:1367 ../gtk-ui.c:74 msgid "Unverified" msgstr "Ongeverificeerde" #: ../gtk-dialog.c:1368 ../gtk-ui.c:73 msgid "Not private" msgstr "Niet besloten" #: ../gtk-dialog.c:1370 msgid "Start a private conversation" msgstr "Start een besloten conversatie" #: ../gtk-dialog.c:1371 msgid "Refresh the private conversation" msgstr "Hernieuw een besloten conversatie" #: ../gtk-dialog.c:1375 msgid "Start _private conversation" msgstr "Start _besloten conversatie" #: ../gtk-dialog.c:1376 msgid "Refresh _private conversation" msgstr "Hernieuw besloten conversatie" #: ../gtk-dialog.c:1555 msgid "I have not" msgstr "ik heb niet" #: ../gtk-dialog.c:1556 msgid "I have" msgstr "ik heb" #: ../gtk-dialog.c:1558 msgid " verified that this is in fact the correct" msgstr "bevestigd of dit daadwerkelijk de correcte" #: ../gtk-dialog.c:1567 #, c-format msgid "fingerprint for %s." msgstr "vingerafdruk is voor %s." #: ../gtk-dialog.c:1579 msgid "" "To verify the fingerprint, contact your buddy via some other " "authenticated channel, such as the telephone or GPG-signed email. Each of " "you should tell your fingerprint to the other." msgstr "" #: ../gtk-dialog.c:1583 msgid "" "If everything matches up, you should indicate in the above dialog that you " "have verified the fingerprint." msgstr "Als alles precies klopt, kun je in het bovenstaande dialoogvenster " "aangeven dat je de vingerafdruk hebt bevestigd." #: ../gtk-dialog.c:1585 msgid "" "If your buddy has more than one IM account, or uses more than one computer, " "he may have multiple fingerprints." msgstr "Als je vriend meerdere IM accounts heeft, of meer dan een computer" "gebruikt, dan kan het zijn dat de vriend meerdere vingerafdrukken heeft." #: ../gtk-dialog.c:1587 msgid "" "However, the only way an imposter could duplicate one of your buddy's " "fingerprints is by stealing information from her/his computer." msgstr "Echter, de enige methode waarop een bedrieger je vriend's " "vingerafdrukken kan namaken, is door geheime informatie te stelen " "van je vriend's computer." #: ../gtk-dialog.c:1591 msgid "Click here for more information about fingerprints." msgstr "Klik hier voor meer informatie over vingerafdrukken" #: ../gtk-dialog.c:1594 msgid "" "A fingerprint is a unique identifier that you should use to " "authenticate your buddy." msgstr "Een vingerafdruk is een unieke herkenbare eigenschap waarmee" "je je vriend kunt authenticeren." #: ../gtk-dialog.c:1616 #, c-format msgid "Verify fingerprint for %s" msgstr "Bevestig de vingerafdruk van %s" #: ../gtk-dialog.c:1620 msgid "[none]" msgstr "[geen]" #: ../gtk-dialog.c:1628 #, c-format msgid "" "Fingerprint for you, %s (%s):\n" "%s\n" "\n" "Purported fingerprint for %s:\n" "%s\n" msgstr "Jouw vingerafdruk, %s (5s):\n" "%s\n" "\n" "Vermeende vingerafdruk van %s:\n" "%s\n" #: ../gtk-dialog.c:1633 ../gtk-ui.c:681 msgid "Verify fingerprint" msgstr "Bevestig vingerafdruk" #: ../gtk-dialog.c:1660 #, c-format msgid "Authenticate %s" msgstr "Authenticeer %s" #: ../gtk-dialog.c:1665 #, c-format msgid "Enter a secret known only to %s and yourself.\n" msgstr "Voer het geheim in dat alleen jij en je vriend %s kennen.\n" #: ../gtk-dialog.c:1668 msgid "Authenticate buddy" msgstr "Authenticeer vriend" #: ../gtk-dialog.c:1700 msgid "An error occurred during authentication." msgstr "Er is een fout opgetreden tijdens de authenticatie" #: ../gtk-dialog.c:1716 msgid "Authentication successful." msgstr "Authenticatie successvol." #: ../gtk-dialog.c:1719 msgid "Authentication failed." msgstr "Authenticatie mislukt." #: ../gtk-dialog.c:1744 #, c-format msgid "Private conversation with %s started.%s" msgstr "Besloten conversatie gestart met %s.%s" #: ../gtk-dialog.c:1748 #, c-format msgid "Unverified conversation with %%s started.%%s" msgstr "Onbeschermde conversatie gestart met %%s.%%s" #. This last case should never happen, since we know #. * we're in ENCRYPTED. #: ../gtk-dialog.c:1756 #, c-format msgid "Not private conversation with %s started.%s" msgstr "Geen besloten conversatie gestart met %s.%s" #: ../gtk-dialog.c:1762 ../gtk-dialog.c:1863 msgid " Warning: using old protocol version 1." msgstr " Waarschuwing: het oude protocol versie 1 is gebruikt." #: ../gtk-dialog.c:1782 #, c-format msgid "Private conversation with %s lost." msgstr "Besloten conversatie met %s verloren." #: ../gtk-dialog.c:1817 #, c-format msgid "" "%s has ended his/her private conversation with you; you should do the same." msgstr "%s heeft de besloten conversatie met jou afgesloten. Jij kunt dit " "het beste nu ook zelf afsluiten." #: ../gtk-dialog.c:1842 #, c-format msgid "Successfully refreshed the private conversation with %s.%s" msgstr "De besloten conversatie met %s is successvol hernieuwd" #: ../gtk-dialog.c:1847 #, c-format msgid "" "Successfully refreshed the unverified conversation with " "%%s.%%s" msgstr "De onbeschermde conversatie met %%s.%%s is met " "success hernieuwd" #. This last case should never happen, since we know #. * we're in ENCRYPTED. #: ../gtk-dialog.c:1856 #, c-format msgid "Successfully refreshed the not private conversation with %s.%s" msgstr "De onbeschermde conversatie met %s.%s is met success hernieuwd. Huh?" #: ../gtk-dialog.c:1883 #, c-format msgid "Attempting to refresh the private conversation with %s..." msgstr "Bezig met het vernieuwen van de beschermde conversatie met %s..." #: ../gtk-dialog.c:1885 #, c-format msgid "Attempting to start a private conversation with %s..." msgstr "Een poging is gestart om een beschermde conversatie te beginnen met %s..." # Paul to Ian: Should/can we really translate these entries here? #: ../gtk-dialog.c:2045 msgid "OTR:" msgstr "OTR:" #: ../gtk-dialog.c:2054 msgid "OTR Messaging" msgstr "OTR Berichtgeving" #: ../gtk-dialog.c:2060 msgid "_End private conversation" msgstr "_Einde beschermde conversatie" #. #. * Don't show the Verify fingerprint menu option any more. You can #. * still get to the dialog through Authenticate connection -> #. * Advanced... #. * #. menuverf = gtk_menu_item_new_with_mnemonic(_("_Verify fingerprint")); #. gtk_menu_shell_append(GTK_MENU_SHELL(menu), menuverf); #. gtk_widget_show(menuverf); #. #: ../gtk-dialog.c:2078 msgid "_Authenticate buddy" msgstr "Authenticeer vriend" #: ../gtk-ui.c:96 #, c-format msgid "Fingerprint: %.80s" msgstr "vingerafdruk %.80s" #: ../gtk-ui.c:100 #, c-format msgid "No key present" msgstr "Geen sleutel aanwezig" #: ../gtk-ui.c:105 #, c-format msgid "No account available" msgstr "Geen account beschikbaar" #: ../gtk-ui.c:165 msgid "Unused" msgstr "Ongebruikt" #: ../gtk-ui.c:171 msgid "Yes" msgstr "Ja" #: ../gtk-ui.c:171 msgid "No" msgstr "Nee" #: ../gtk-ui.c:396 msgid "Enable private messaging" msgstr "Start beschermde conversatie" #: ../gtk-ui.c:398 msgid "Automatically initiate private messaging" msgstr "Automatisch initieren van beschermde berichten" #: ../gtk-ui.c:400 msgid "Require private messaging" msgstr "Alleen beschermde berichten toestaan" #: ../gtk-ui.c:403 msgid "Don't log OTR conversations" msgstr "OTR conversaties niet opslaan" #: ../gtk-ui.c:531 msgid "My private keys" msgstr "Mijn geheime sleutels" #: ../gtk-ui.c:540 msgid "Key for account:" msgstr "Sleutel voor account:" #: ../gtk-ui.c:565 msgid "Generate" msgstr "Genereer" #: ../gtk-ui.c:596 msgid "Default OTR Settings" msgstr "Standaard OTR instellingen" #: ../gtk-ui.c:625 msgid "Screenname" msgstr "Naam" #: ../gtk-ui.c:626 msgid "Status" msgstr "Status" #: ../gtk-ui.c:627 msgid "Verified" msgstr "Geverificeerd" #: ../gtk-ui.c:628 msgid "Fingerprint" msgstr "vingerafdruk" #: ../gtk-ui.c:629 msgid "Account" msgstr "Account" #: ../gtk-ui.c:665 msgid "Start private connection" msgstr "Start besloten verbinding" #: ../gtk-ui.c:673 msgid "End private connection" msgstr "Stop besloten verbinding" #: ../gtk-ui.c:689 msgid "Forget fingerprint" msgstr "Vergeet vingerafdruk" #: ../gtk-ui.c:738 msgid "Config" msgstr "Configuratie" #: ../gtk-ui.c:740 msgid "Known fingerprints" msgstr "Bekende vingerafdrukken" #: ../gtk-ui.c:838 ../otr-plugin.c:577 msgid "OTR Settings" msgstr "OTR Instellingen" #. Set the title #: ../gtk-ui.c:856 #, c-format msgid "OTR Settings for %s" msgstr "OTR Instellingen voor %s" #. Make the cascaded checkboxes #: ../gtk-ui.c:873 msgid "Use default OTR settings for this buddy" msgstr "Gebruik de standaard OTR instellingen voor deze vriend" #: ../otr-plugin.c:113 #, c-format msgid "You are not currently connected to account %s (%s)." msgstr "Je bent op dit moment niet verbonden aan het account %s (%s)." #: ../otr-plugin.c:117 msgid "Not connected" msgstr "Niet verbonden" #: ../otr-plugin.c:161 #, c-format msgid "Out of memory building filenames!\n" msgstr "Te weinig geheugen voor het opbouwen van bestandsnamen!" #: ../otr-plugin.c:167 #, c-format msgid "Could not write private key file\n" msgstr "Kon het geheime sleutel bestand niet schrijven\n" #: ../otr-plugin.c:210 #, c-format msgid "Unknown account %s (%s)." msgstr "Onbekend account %s (%s)." #: ../otr-plugin.c:214 msgid "Unknown account" msgstr "Onbekend account" #: ../otr-plugin.c:953 msgid "Off-the-Record Messaging" msgstr "Off-the-Record Berichtgeving" #: ../otr-plugin.c:954 msgid "Provides private and secure conversations" msgstr "Beschermd en versleuteld gesprekken" #: ../otr-plugin.c:955 msgid "" "Preserves the privacy of IM communications by providing encryption, " "authentication, deniability, and perfect forward secrecy." msgstr "Beschermd de privacy van IM communicatie door middel van " "het gebruik van versleuteling, authenticatie, onken-mogelijkheid en " "'perfect forward secrecy'. #: ../ui.c:108 #, c-format msgid "Account %s (%s) could not be found" msgstr "Account %s (%s) kon niet worden gevonden" #: ../ui.c:112 msgid "Account not found" msgstr "Account niet gevonden" From ian at cypherpunks.ca Thu Jul 26 11:03:03 2007 From: ian at cypherpunks.ca (Ian Goldberg) Date: Thu, 26 Jul 2007 11:03:03 -0400 Subject: [OTR-dev] libotr and pidgin-otr 3.1.0-preview1 available In-Reply-To: <20070724201104.GN23980@thunk.cs.uwaterloo.ca> References: <20070724201104.GN23980@thunk.cs.uwaterloo.ca> Message-ID: <20070726150303.GK24420@thunk.cs.uwaterloo.ca> On Tue, Jul 24, 2007 at 04:11:04PM -0400, Ian Goldberg wrote: > The point of this preview version is mainly for package maintainers to > tell me what I've messed up as far as packaging / portability go. The > sooner I get feedback in that area, the sooner the "real" 3.1.0 release > will be there. To be clear, this preview release should *not* be packaged and distributed by the package maintainers. There's at least one more crash bug to track down, and translations to add, before official packages should be made. But you should try to make the packages yourself, and let me know if anything's not building properly, or something like that. Thanks, - Ian From ian at cypherpunks.ca Thu Jul 26 12:57:42 2007 From: ian at cypherpunks.ca (Ian Goldberg) Date: Thu, 26 Jul 2007 12:57:42 -0400 Subject: [OTR-dev] libotr and pidgin-otr 3.1.0-preview2 available In-Reply-To: <20070724201104.GN23980@thunk.cs.uwaterloo.ca> References: <20070724201104.GN23980@thunk.cs.uwaterloo.ca> Message-ID: <20070726165742.GO24420@thunk.cs.uwaterloo.ca> Fixed (hopefully) a problem with 64-bit systems. [Had an "unsigned int" where we needed a "size_t", d'oh. libotr now compiles cleanly on both 32 and 64 bit arches with "-Wall -pedantic -Werror". ;-) ] http://otr.cypherpunks.ca/libotr-3.1.0-preview2.tar.gz http://otr.cypherpunks.ca/pidgin-otr-3.1.0-preview2.tar.gz - Ian From paul at cypherpunks.ca Thu Jul 26 13:26:25 2007 From: paul at cypherpunks.ca (Paul Wouters) Date: Thu, 26 Jul 2007 13:26:25 -0400 (EDT) Subject: [OTR-dev] libotr and pidgin-otr 3.1.0-preview2 available In-Reply-To: <20070726165742.GO24420@thunk.cs.uwaterloo.ca> References: <20070724201104.GN23980@thunk.cs.uwaterloo.ca> <20070726165742.GO24420@thunk.cs.uwaterloo.ca> Message-ID: On Thu, 26 Jul 2007, Ian Goldberg wrote: > Fixed (hopefully) a problem with 64-bit systems. [Had an "unsigned int" > where we needed a "size_t", d'oh. libotr now compiles cleanly on both > 32 and 64 bit arches with "-Wall -pedantic -Werror". ;-) ] > > http://otr.cypherpunks.ca/libotr-3.1.0-preview2.tar.gz > http://otr.cypherpunks.ca/pidgin-otr-3.1.0-preview2.tar.gz Fedora7 test packages are available at: ftp://ftp.xelerance.com/libotr/binaries ftp://ftp.xelerance.com/pidgin-otr/binaries Paul -- Building and integrating Virtual Private Networks with Openswan: http://www.amazon.com/gp/product/1904811256/104-3099591-2946327?n=283155 From ian at cypherpunks.ca Thu Jul 26 18:55:07 2007 From: ian at cypherpunks.ca (Ian Goldberg) Date: Thu, 26 Jul 2007 18:55:07 -0400 Subject: [OTR-dev] Help with Windows dll? In-Reply-To: <45CF4F8D.60308@gmx.net> References: <45CF4F8D.60308@gmx.net> Message-ID: <20070726225507.GF3751@yoink.cs.uwaterloo.ca> On Sun, Feb 11, 2007 at 06:17:01PM +0100, Thomas B. wrote: > I also wanted to test it under Windows, which was a bit trickier. I > don't know if this can be done in a better way (it's long ago that I > compiled something for Windows), but it worked for me. First, I > followed Ian's instructions to set up a cross-compiling environment > with MinGW under Linux: > http://lists.cypherpunks.ca/pipermail/otr-users/2006-November/000792.html > That worked quite well and enabled me to cross-compile the current CVS > version of gaim-otr. Then, after applying my patch, I needed two extra > steps: > > 1.) The MinGW environment was lacking a libintl.h. The libintl.h from > my system was not suitable, as it belongs to glibc (and the code of > libintl is built into glibc). So I downloaded the gettext package, > cross-compiled it and installed it into /usr/i586-mingw32msvc/, so > that I had a libintl.h and a libintl.a in my MinGW environment. > > 2.) Inside gaim-otr, LOCALEDIR needs to be correctly defined so that > the language files can be found. The tricky thing is that in Win32 > Gaim, the directory containing the locale files is generally only > known at runtime (it depends on where the user has installed Gaim). So > in Gaim's win32dep.h, LOCALEDIR is defined as a function call to > wgaim_locale_dir(). Therefore I included that file in otr-plugin.c, > and placed win32dep.h and the other headers in libgaim/win32 (from the > Gaim source tarball) into /usr/i586-mingw32msvc/include/gaim. > > Then, after making some adjustments to Makefile.mingw, I was able to > cross-compile the patched gaim-otr for Windows with a "make -f > Makefile.mingw". I did all that, and I successfully built a pidgin-otr.dll file, but pidgin (on Windows) won't load it. pidgin -d complains: plugins: C:\Program Files\Pidgin\plugins\pidgin-otr.dll is not loadable: The specified module could not be found. This error message is the output of g_module_error() when g_module_open() fails, but I have no idea why that might be happening. Here's my build line: i586-mingw32msvc-gcc -g -shared -Wl,--enable-auto-image-base otr-plugin.o ui.o dialogs.o gtk-ui.o gtk-dialog.o -o pidgin-otr.dll /usr/i586-mingw32msvc/lib/libotr.a -lgtk-win32-2.0 -lglib-2.0 -lgdk_pixbuf-2.0 -lgobject-2.0 -lpidgin -llibpurple -lgcrypt -lgpg-error -L/usr/i586-mingw32msvc/lib -lintl If you'd like to see the dll itself, you can find it at http://otr.cypherpunks.ca/binaries/windows/pidgin-otr-3.1-preview2.zip The source is what's currently checked into CVS, which is negligibly different from the 3.1.0-preview2 I posted this morning. Any hints would be appreciated. I know approximately nothing about Windows. ;-) Thanks, - Ian From mgentry at ieee.org Thu Jul 26 19:33:48 2007 From: mgentry at ieee.org (Martin Gentry) Date: Thu, 26 Jul 2007 19:33:48 -0400 Subject: [OTR-dev] Help with Windows dll? References: <45CF4F8D.60308@gmx.net> <20070726225507.GF3751@yoink.cs.uwaterloo.ca> Message-ID: <001101c7cfdd$7136fe60$9800a8c0@IndustryNext.local> ----- Original Message ----- From: "Ian Goldberg" To: "Thomas B." Cc: Sent: Thursday, July 26, 2007 6:55 PM Subject: [OTR-dev] Help with Windows dll? > On Sun, Feb 11, 2007 at 06:17:01PM +0100, Thomas B. wrote: >> I also wanted to test it under Windows, which was a bit trickier. I >> don't know if this can be done in a better way (it's long ago that I >> compiled something for Windows), but it worked for me. First, I >> followed Ian's instructions to set up a cross-compiling environment >> with MinGW under Linux: >> http://lists.cypherpunks.ca/pipermail/otr-users/2006-November/000792.html >> That worked quite well and enabled me to cross-compile the current CVS >> version of gaim-otr. Then, after applying my patch, I needed two extra >> steps: >> >> 1.) The MinGW environment was lacking a libintl.h. The libintl.h from >> my system was not suitable, as it belongs to glibc (and the code of >> libintl is built into glibc). So I downloaded the gettext package, >> cross-compiled it and installed it into /usr/i586-mingw32msvc/, so >> that I had a libintl.h and a libintl.a in my MinGW environment. >> >> 2.) Inside gaim-otr, LOCALEDIR needs to be correctly defined so that >> the language files can be found. The tricky thing is that in Win32 >> Gaim, the directory containing the locale files is generally only >> known at runtime (it depends on where the user has installed Gaim). So >> in Gaim's win32dep.h, LOCALEDIR is defined as a function call to >> wgaim_locale_dir(). Therefore I included that file in otr-plugin.c, >> and placed win32dep.h and the other headers in libgaim/win32 (from the >> Gaim source tarball) into /usr/i586-mingw32msvc/include/gaim. >> >> Then, after making some adjustments to Makefile.mingw, I was able to >> cross-compile the patched gaim-otr for Windows with a "make -f >> Makefile.mingw". > > I did all that, and I successfully built a pidgin-otr.dll file, but > pidgin (on Windows) won't load it. pidgin -d complains: > > plugins: C:\Program Files\Pidgin\plugins\pidgin-otr.dll is not > loadable: The specified module could not be found. > > This error message is the output of g_module_error() when > g_module_open() fails, but I have no idea why that might be happening. > > Here's my build line: > > i586-mingw32msvc-gcc -g -shared -Wl,--enable-auto-image-base > otr-plugin.o ui.o dialogs.o gtk-ui.o gtk-dialog.o -o pidgin-otr.dll > /usr/i586-mingw32msvc/lib/libotr.a -lgtk-win32-2.0 -lglib-2.0 > -lgdk_pixbuf-2.0 -lgobject-2.0 -lpidgin -llibpurple -lgcrypt -lgpg-error > -L/usr/i586-mingw32msvc/lib -lintl > > If you'd like to see the dll itself, you can find it at > > http://otr.cypherpunks.ca/binaries/windows/pidgin-otr-3.1-preview2.zip > > The source is what's currently checked into CVS, which is negligibly > different from the 3.1.0-preview2 I posted this morning. > > Any hints would be appreciated. I know approximately nothing about > Windows. ;-) I know this might not really help much since I don't offhand know how to remedy the problem, but the dll you built wants a libintl-8.dll to be available whereas the GTK+ runtime that got installed when I just installed pidgin on a Windows box includes intl.dll, not libintl-8.dll. -martin From ian at cypherpunks.ca Thu Jul 26 21:09:15 2007 From: ian at cypherpunks.ca (Ian Goldberg) Date: Thu, 26 Jul 2007 21:09:15 -0400 Subject: [OTR-dev] Help with Windows dll? In-Reply-To: <001101c7cfdd$7136fe60$9800a8c0@IndustryNext.local> References: <45CF4F8D.60308@gmx.net> <20070726225507.GF3751@yoink.cs.uwaterloo.ca> <001101c7cfdd$7136fe60$9800a8c0@IndustryNext.local> Message-ID: <20070727010915.GG3751@yoink.cs.uwaterloo.ca> On Thu, Jul 26, 2007 at 07:33:48PM -0400, Martin Gentry wrote: > I know this might not really help much since I don't offhand know how to > remedy the problem, but the dll you built wants a libintl-8.dll to be > available whereas the GTK+ runtime that got installed when I just installed > pidgin on a Windows box includes intl.dll, not libintl-8.dll. Thanks, that helped a lot. I statically linked libintl and libiconv, and now I have a working pidgin-otr.dll again (and it works in Dutch, too!). Out of curiosity, what do you use to figure out what .dlls a given .dll requires? Thanks so much, - Ian From mgentry at ieee.org Thu Jul 26 22:38:44 2007 From: mgentry at ieee.org (Martin Gentry) Date: Thu, 26 Jul 2007 22:38:44 -0400 Subject: [OTR-dev] Help with Windows dll? In-Reply-To: <20070727010915.GG3751@yoink.cs.uwaterloo.ca> References: <45CF4F8D.60308@gmx.net> <20070726225507.GF3751@yoink.cs.uwaterloo.ca> <001101c7cfdd$7136fe60$9800a8c0@IndustryNext.local> <20070727010915.GG3751@yoink.cs.uwaterloo.ca> Message-ID: <51f9d0440707261938t1372eb9cwab7bc3306d8c4c37@mail.gmail.com> On 7/26/07, Ian Goldberg wrote: > > Thanks, that helped a lot. I statically linked libintl and libiconv, > and now I have a working pidgin-otr.dll again (and it works in Dutch, > too!). > > Out of curiosity, what do you use to figure out what .dlls a given .dll > requires? Dependency walker - http://www.dependencywalker.com/. Not sure if there are any non-Windows tools that will do the same thing. -martin -------------- next part -------------- An HTML attachment was scrubbed... URL: From gdt at ir.bbn.com Fri Jul 27 19:51:25 2007 From: gdt at ir.bbn.com (Greg Troxel) Date: Fri, 27 Jul 2007 19:51:25 -0400 Subject: [OTR-dev] libotr and pidgin-otr 3.1.0-preview2 available In-Reply-To: <20070726165742.GO24420@thunk.cs.uwaterloo.ca> (Ian Goldberg's message of "Thu, 26 Jul 2007 12:57:42 -0400") References: <20070724201104.GN23980@thunk.cs.uwaterloo.ca> <20070726165742.GO24420@thunk.cs.uwaterloo.ca> Message-ID: I don't mean to rant, but I'm trying to package pidgin-otr and having a harder time than seems necessary. I'm experienced enough at packaging that I suspect others are too. 1) at http://www.cypherpunks.ca/otr/ it says that there is OTR plugin for Pidgin (formerly known as gaim) and the file is http://www.cypherpunks.ca/otr/gaim-otr-3.0.0.tar.gz But this file is a plugin for gaim (1.5), not for pidgin (which to me implies 2.0). The headline should indicate clearly that this is for gaim 1.5.X. 2) There is no obvious way to find out the list of files available for download. Simply putting them all in http://www.cypherpunks.ca/otr/download/ and enabling indexing would help a lot. 3) It seems that pidgin has been out for a while, so it never occured to me that there is no released otr plugin based on the beta one that's been around for ever. If this is really the case the top-level web page should explain it - I expected to find pidgin-otr-3.0.0 and haven't been able to. 4) I found Ian's message about preview2, and downloaded it. It would be good to use 3.1.0a2 to follow normal conventions for prerelease software, and to have the directory name match the version name, so that packaging software that assumes it will match won't need adjusting. Right now 3.1.0-preview2 unpacks into 3.1.0. 5) pidgin-otr-3.1.0 seems to need libotr-3.1.0. While this might really be necessary, it would be really nice to decouple gui issues from core protocol issues, and to only depend on released libraries - even for unreleased plugins. It's awkward to test pidgin-otr-3.1.0 while not breaking gaim-otr-3.0.0 on the same system. (I'd hope that 3.1.0 is API and ABI compatible, but you'll forgive me for not being confident in this given all of the above.) I really appreciate all the work that's gone into OTR, and I use it daily. Sorry if I'm sounding cranky, but a bit more care in making things packaging friendly and being careful to avoid confusion would make it more likely that more people can get OTR more easily. The good news is that after updating libotr (which only needed a version change and a single new .h), and adjusting the former gaim-otr package for pidgin-otr (naming changes only), the plugin works. This is on NetBSD-current on i386 with pretty recent gnome/gtk/glib/etc and pidgin 2.0.1. Just to be clear, this is a full test of the plugin as built by the packaging system, and my only real issues were 4 and 5 above, both quite minor. Greg From gdt at ir.bbn.com Fri Jul 27 19:56:39 2007 From: gdt at ir.bbn.com (Greg Troxel) Date: Fri, 27 Jul 2007 19:56:39 -0400 Subject: [OTR-dev] libotr major version bump? Message-ID: Was this really necessary? Upgrading to 3.1.0 from 3.0.0 went from 2.0 to 3.0 in ELF shlib numbering, and I see nothing in NEWS that indicates why - just things that look like they might have new calls, vs changing the signature of existing calls. So the gaim-otr for gaim 1.5 was broken by this. NEWS really should say clearly which procedures had an interface change, so that users of the library can update their code. Rebuilding gaim-otr seems to fix the problem, though, so there seems not to have been an API change. From ian at cypherpunks.ca Sat Jul 28 14:14:40 2007 From: ian at cypherpunks.ca (Ian Goldberg) Date: Sat, 28 Jul 2007 14:14:40 -0400 Subject: [OTR-dev] libotr major version bump? In-Reply-To: References: Message-ID: <20070728181440.GO3751@yoink.cs.uwaterloo.ca> On Fri, Jul 27, 2007 at 07:56:39PM -0400, Greg Troxel wrote: > Was this really necessary? Upgrading to 3.1.0 from 3.0.0 went from 2.0 > to 3.0 in ELF shlib numbering, and I see nothing in NEWS that indicates > why - just things that look like they might have new calls, vs changing > the signature of existing calls. So the gaim-otr for gaim 1.5 was > broken by this. NEWS really should say clearly which procedures had an > interface change, so that users of the library can update their code. > > Rebuilding gaim-otr seems to fix the problem, though, so there seems not > to have been an API change. That's weird. When I build libotr-3.1.0, I get a "libotr.so.2.1.0", as expected, since the API and ABI are indeed back-compatible. libotr's configure.ac indicates: LIBOTR_LIBTOOL_VERSION="3:0:1" which specifies current=3, revision=0, age=1, so you get 2.1.0 out of that. What version number is libtool using for you? libotr's UPDATING file contains the information about how users of libotr can update their code for the new version. - Ian From ian at cypherpunks.ca Sat Jul 28 14:23:59 2007 From: ian at cypherpunks.ca (Ian Goldberg) Date: Sat, 28 Jul 2007 14:23:59 -0400 Subject: [OTR-dev] libotr and pidgin-otr 3.1.0-preview2 available In-Reply-To: References: <20070724201104.GN23980@thunk.cs.uwaterloo.ca> <20070726165742.GO24420@thunk.cs.uwaterloo.ca> Message-ID: <20070728182359.GP3751@yoink.cs.uwaterloo.ca> On Fri, Jul 27, 2007 at 07:51:25PM -0400, Greg Troxel wrote: > I don't mean to rant, but I'm trying to package pidgin-otr and having a > harder time than seems necessary. I'm experienced enough at packaging > that I suspect others are too. > > 1) at http://www.cypherpunks.ca/otr/ it says that there is > > OTR plugin for Pidgin (formerly known as gaim) > > and the file is http://www.cypherpunks.ca/otr/gaim-otr-3.0.0.tar.gz But > this file is a plugin for gaim (1.5), not for pidgin (which to me > implies 2.0). The headline should indicate clearly that this is for > gaim 1.5.X. We're just waiting for the final release version of 3.1.0 to be ready, which looks like Aug 1 plus or minus a day or two. All that's left is some tidying of some of the documentation. At that point, the old versions will come off the website. > 2) There is no obvious way to find out the list of files available for > download. Simply putting them all in > http://www.cypherpunks.ca/otr/download/ and enabling indexing would help > a lot. As a rule, the webserver's indexing is off, but you make a good point, and I'll ponder this. > 3) It seems that pidgin has been out for a while, so it never occured to > me that there is no released otr plugin based on the beta one that's > been around for ever. If this is really the case the top-level web page > should explain it - I expected to find pidgin-otr-3.0.0 and haven't been > able to. As above, pidgin-otr-3.1.0 will appear next week. > 4) I found Ian's message about preview2, and downloaded it. It would be > good to use 3.1.0a2 to follow normal conventions for prerelease > software, and to have the directory name match the version name, so that > packaging software that assumes it will match won't need adjusting. > Right now 3.1.0-preview2 unpacks into 3.1.0. I did that sort of on purpose; -preview2 isn't meant to be an alpha release. It's meant to be something which structurally will be identical to the upcoming release. That way, packagers can see if there's something broken that I'd need to fix before the 3.1.0 actual release. > 5) pidgin-otr-3.1.0 seems to need libotr-3.1.0. While this might really > be necessary, it would be really nice to decouple gui issues from core > protocol issues, and to only depend on released libraries - even for > unreleased plugins. It's awkward to test pidgin-otr-3.1.0 while not > breaking gaim-otr-3.0.0 on the same system. (I'd hope that 3.1.0 is API > and ABI compatible, but you'll forgive me for not being confident in > this given all of the above.) Indeed, installing libotr-3.1.0 will not break an existing gaim-otr-3.0.0. pidgin-otr-3.1.0 naturally requires libotr-3.1.0, since it uses the library's new features. > name and pointing pkgsrc at the unpacked location> > > > I really appreciate all the work that's gone into OTR, and I use it > daily. Sorry if I'm sounding cranky, but a bit more care in making > things packaging friendly and being careful to avoid confusion would > make it more likely that more people can get OTR more easily. > > > The good news is that after updating libotr (which only needed a version > change and a single new .h), and adjusting the former gaim-otr package > for pidgin-otr (naming changes only), the plugin works. This is on > NetBSD-current on i386 with pretty recent gnome/gtk/glib/etc and pidgin > 2.0.1. Just to be clear, this is a full test of the plugin as built by > the packaging system, and my only real issues were 4 and 5 above, both > quite minor. So when pidgin-otr-3.1.0 and libotr-3.1.0 get released for real next week, they'll build cleanly on NetBSD? That's good to know. Thanks! - Ian From gdt at ir.bbn.com Sun Jul 29 07:10:44 2007 From: gdt at ir.bbn.com (Greg Troxel) Date: Sun, 29 Jul 2007 07:10:44 -0400 Subject: [OTR-dev] libotr and pidgin-otr 3.1.0-preview2 available In-Reply-To: <20070728182359.GP3751@yoink.cs.uwaterloo.ca> (Ian Goldberg's message of "Sat, 28 Jul 2007 14:23:59 -0400") References: <20070724201104.GN23980@thunk.cs.uwaterloo.ca> <20070726165742.GO24420@thunk.cs.uwaterloo.ca> <20070728182359.GP3751@yoink.cs.uwaterloo.ca> Message-ID: Ian Goldberg writes: > On Fri, Jul 27, 2007 at 07:51:25PM -0400, Greg Troxel wrote: >> I don't mean to rant, but I'm trying to package pidgin-otr and having a >> harder time than seems necessary. I'm experienced enough at packaging >> that I suspect others are too. >> >> 1) at http://www.cypherpunks.ca/otr/ it says that there is >> >> OTR plugin for Pidgin (formerly known as gaim) >> >> and the file is http://www.cypherpunks.ca/otr/gaim-otr-3.0.0.tar.gz But >> this file is a plugin for gaim (1.5), not for pidgin (which to me >> implies 2.0). The headline should indicate clearly that this is for >> gaim 1.5.X. > > We're just waiting for the final release version of 3.1.0 to be ready, > which looks like Aug 1 plus or minus a day or two. All that's left is > some tidying of some of the documentation. At that point, the old > versions will come off the website. It's fine that 3.1.0 isn't out, but my point that the current gaim 1.5 plugin is mislabeled as pidgin remains. Plus, I think that the gaim 1.5 plugins should remain available until it's reasonable to tell people that they're being completely ridiculous to be running 1.5. Given that 2.0 has been out only a short time, I don't think that's happened yet. >> 3) It seems that pidgin has been out for a while, so it never occured to >> me that there is no released otr plugin based on the beta one that's >> been around for ever. If this is really the case the top-level web page >> should explain it - I expected to find pidgin-otr-3.0.0 and haven't been >> able to. > > As above, pidgin-otr-3.1.0 will appear next week. OK, but please keep in mind that visitors to the web site are not aware of your announced-on-the-list plans, and that the web site should clearly and correctly explain the status of the world at all times. A simple "These files are for gaim 1.5. Support for pidgin 2.0 has not been released and is expected soon." would do wonders. >> 4) I found Ian's message about preview2, and downloaded it. It would be >> good to use 3.1.0a2 to follow normal conventions for prerelease >> software, and to have the directory name match the version name, so that >> packaging software that assumes it will match won't need adjusting. >> Right now 3.1.0-preview2 unpacks into 3.1.0. > > I did that sort of on purpose; -preview2 isn't meant to be an alpha > release. It's meant to be something which structurally will be > identical to the upcoming release. That way, packagers can see if > there's something broken that I'd need to fix before the 3.1.0 actual > release. My point is that it isn't structurally identical, because releases unpack into directories that match the file name, and this doesn't. But I suspect that you did 'make dist', and then just renamed it. I realize that not renaming it is no good either... >> 5) pidgin-otr-3.1.0 seems to need libotr-3.1.0. While this might really >> be necessary, it would be really nice to decouple gui issues from core >> protocol issues, and to only depend on released libraries - even for >> unreleased plugins. It's awkward to test pidgin-otr-3.1.0 while not >> breaking gaim-otr-3.0.0 on the same system. (I'd hope that 3.1.0 is API >> and ABI compatible, but you'll forgive me for not being confident in >> this given all of the above.) > > Indeed, installing libotr-3.1.0 will not break an existing > gaim-otr-3.0.0. pidgin-otr-3.1.0 naturally requires libotr-3.1.0, since > it uses the library's new features. So I guess my point is that it would have been nice to have pidgin-otr-3.0.0 that worked with the old libotr. Because of this it was harder to test. > So when pidgin-otr-3.1.0 and libotr-3.1.0 get released for real next > week, they'll build cleanly on NetBSD? That's good to know. Yes, except for the shlib version issue, which I'll follow up separately on. I have packages ready to commit to pkgsrc once I remove previewN, update checksums, and remove the line to make it build in a directory other than the one implied by the distfile. From gdt at ir.bbn.com Sun Jul 29 07:34:33 2007 From: gdt at ir.bbn.com (Greg Troxel) Date: Sun, 29 Jul 2007 07:34:33 -0400 Subject: [OTR-dev] libotr major version bump? In-Reply-To: <20070728181440.GO3751@yoink.cs.uwaterloo.ca> (Ian Goldberg's message of "Sat, 28 Jul 2007 14:14:40 -0400") References: <20070728181440.GO3751@yoink.cs.uwaterloo.ca> Message-ID: Ian Goldberg writes: > That's weird. When I build libotr-3.1.0, I get a "libotr.so.2.1.0", as > expected, since the API and ABI are indeed back-compatible. > > libotr's configure.ac indicates: > > LIBOTR_LIBTOOL_VERSION="3:0:1" > > which specifies current=3, revision=0, age=1, so you get 2.1.0 out of > that. > > What version number is libtool using for you? In config.status: s, at LIBOTR_LIBTOOL_VERSION@,3:0:1,;t t and this is passed to libtool, but it makes so.3.0 poblano gdt 22 /usr/pkgsrc/chat/libotr/work/libotr-3.1.0/src > gmake /bin/sh ../libtool --tag=CC --mode=link cc -O2 -I/usr/pkg/include -I/usr/include -L/usr/pkg/lib -Wl,-R/usr/pkg/lib -L/usr/lib -Wl,-R/usr/lib -o libotr.la -rpath /usr/pkg/lib -version-info 3:0:1 -L/usr/pkg/lib -Wl,-R/usr/pkg/lib -lgcrypt -Wl,-R/usr/pkg/lib -L/usr/pkg/lib -lgpg-error privkey.lo context.lo proto.lo b64.lo dh.lo mem.lo message.lo userstate.lo tlv.lo auth.lo sm.lo cc -shared .libs/privkey.o .libs/context.o .libs/proto.o .libs/b64.o .libs/dh.o .libs/mem.o .libs/message.o .libs/userstate.o .libs/tlv.o .libs/auth.o .libs/sm.o -Wl,--rpath -Wl,/usr/pkg/lib -Wl,--rpath -Wl,/usr/pkg/lib -L/usr/pkg/lib -L/usr/lib /usr/pkg/lib/libgcrypt.so /usr/pkg/lib/libgpg-error.so -Wl,-R/usr/pkg/lib -Wl,-R/usr/lib -Wl,-R/usr/pkg/lib -Wl,-R/usr/pkg/lib -Wl,-soname -Wl,libotr.so.3 -o .libs/libotr.so.3.0 (cd .libs && rm -f libotr.so.3 && ln -s libotr.so.3.0 libotr.so.3) (cd .libs && rm -f libotr.so && ln -s libotr.so.3.0 libotr.so) ar cru .libs/libotr.a privkey.o context.o proto.o b64.o dh.o mem.o message.o userstate.o tlv.o auth.o sm.o ranlib .libs/libotr.a creating libotr.la (cd .libs && rm -f libotr.la && ln -s ../libotr.la libotr.la) I have libtool 1.5.22, but I'm 99% sure that the above runs the libtool that was generated by you at 'make dist' time. So I read the pkgsrc documentation and added USE_LIBTOOL=yes, so that the included libtool script would get overwritten with one that's been fixed for all the platforms pkgsrc runs on. Then I get the right shlib number. -rwxr-xr-x 1 root wheel 74300 Jul 29 07:32 /usr/pkg/lib/libotr.so.2.1.0 I don't understand this - I think it means that just building libotr not with pkgsrc will get the wrong version. I can remove the libtool override, add -x to libtool, and send that if you want to look, but I don't understand libtool innards. > libotr's UPDATING file contains the information about how users of > libotr can update their code for the new version. Thanks - I see you've been quite careful about upgrading issues. From gdt at ir.bbn.com Sun Jul 29 08:02:30 2007 From: gdt at ir.bbn.com (Greg Troxel) Date: Sun, 29 Jul 2007 08:02:30 -0400 Subject: [OTR-dev] libotr and pidgin-otr 3.1.0-preview2 available In-Reply-To: <20070726165742.GO24420@thunk.cs.uwaterloo.ca> (Ian Goldberg's message of "Thu, 26 Jul 2007 12:57:42 -0400") References: <20070724201104.GN23980@thunk.cs.uwaterloo.ca> <20070726165742.GO24420@thunk.cs.uwaterloo.ca> Message-ID: http://otr.cypherpunks.ca/pidgin-otr-3.1.0-preview2.tar.gz During the install, I get errors about nl.gmo. See build log appended. I don't understand how this is supposed to work. BUILD LOG => Required installed package digest>=20010302: digest-20070703 found => Required installed package checkperms>=1.1: checkperms-1.7 found => Checksum SHA1 OK for pidgin-otr-3.1.0-preview2.tar.gz => Checksum RMD160 OK for pidgin-otr-3.1.0-preview2.tar.gz ===> Installing dependencies for pidgin-otr-3.1.0a2 => Required installed package intltool>=0.35: intltool-0.35.5 found => Required installed package perl>=5.0: perl-5.8.8nb4 found => Required installed package pkg-config>=0.19: pkg-config-0.21nb1 found => Required installed package x11-links>=0.25: x11-links-0.31 found => Required installed package randrproto>=1.2.0: randrproto-1.2.1 found => Required installed package renderproto>=0.9.1: renderproto-0.9.2 found => Required installed package fixesproto>=3.0.0: fixesproto-4.0 found => Required installed package inputproto>=1.4: inputproto-1.4.2 found => Required installed package pidgin>=2.0.1nb1: pidgin-2.0.1nb1 found => Required installed package libotr>=3.0.0: libotr-3.1.0 found => Required installed package libgcrypt>=1.2.0: libgcrypt-1.2.4 found => Required installed package gtk2+>=2.4.0: gtk2+-2.10.14 found => Required installed package glib2>=2.4.0: glib2-2.12.13 found ===> Overriding tools for pidgin-otr-3.1.0a2 ===> Extracting for pidgin-otr-3.1.0a2 ===> Patching for pidgin-otr-3.1.0a2 ===> Creating toolchain wrappers for pidgin-otr-3.1.0a2 src=/usr/pkg/lib/pkgconfig/fixesproto.pc dst=/usr/home/gdt/NetBSD-current/pkgsrc/chat/pidgin-otr/work/.buildlink/lib/pkgconfig/fixesext.pc; /bin/mkdir -p /usr/home/gdt/NetBSD-current/pkgsrc/chat/pidgin-otr/work/.buildlink/lib/pkgconfig; if test -f ${src}; then /bin/ln -sf ${src} ${dst}; fi ===> Configuring for pidgin-otr-3.1.0a2 => Checking for portability problems in extracted files => Modifying GNU configure scripts to avoid --recheck => Replacing config-guess with pkgsrc versions => Replacing config-sub with pkgsrc versions => Replacing install-sh with pkgsrc version configure: WARNING: If you wanted to set the --build type, don't use --host. If a cross compiler is detected then cross compile mode will be used. checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel checking whether build environment is sane... yes checking for gawk... /usr/bin/awk checking whether make sets $(MAKE)... yes checking for i386--netbsdelf-strip... no checking for strip... strip checking for i386--netbsdelf-gcc... cc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether cc accepts -g... yes checking for cc option to accept ANSI C... none needed checking for style of include used by make... GNU checking dependency style of cc... gcc3 checking build system type... i386-unknown-netbsdelf4.99.24 checking host system type... i386--netbsdelf checking for a sed that does not truncate output... /usr/home/gdt/NetBSD-current/pkgsrc/chat/pidgin-otr/work/.tools/bin/sed checking for egrep... grep -E checking for ld used by cc... /usr/home/gdt/NetBSD-current/pkgsrc/chat/pidgin-otr/work/.wrapper/bin/ld checking if the linker (/usr/home/gdt/NetBSD-current/pkgsrc/chat/pidgin-otr/work/.wrapper/bin/ld) is GNU ld... yes checking for /usr/home/gdt/NetBSD-current/pkgsrc/chat/pidgin-otr/work/.wrapper/bin/ld option to reload object files... -r checking for BSD-compatible nm... nm checking whether ln -s works... yes checking how to recognise dependent libraries... match_pattern /lib[^/]+(\.so|_pic\.a)$ checking how to run the C preprocessor... cc -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking for i386--netbsdelf-g++... c++ checking whether we are using the GNU C++ compiler... no checking whether c++ accepts -g... no checking dependency style of c++... none checking how to run the C++ preprocessor... cpp checking for i386--netbsdelf-g77... f77 checking whether we are using the GNU Fortran 77 compiler... no checking whether f77 accepts -g... no checking the maximum length of command line arguments... 196608 checking command to parse nm output from cc object... ok checking for objdir... .libs checking for i386--netbsdelf-ar... no checking for ar... ar checking for i386--netbsdelf-ranlib... no checking for ranlib... ranlib checking for i386--netbsdelf-strip... strip checking if cc supports -fno-rtti -fno-exceptions... no checking for cc option to produce PIC... -fPIC checking if cc PIC flag -fPIC works... yes checking if cc static flag -static works... yes checking if cc supports -c -o file.o... yes checking whether the cc linker (/usr/home/gdt/NetBSD-current/pkgsrc/chat/pidgin-otr/work/.wrapper/bin/ld) supports shared libraries... yes checking whether -lc should be explicitly linked in... yes checking dynamic linker characteristics... NetBSD ld.elf_so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... no configure: creating libtool appending configuration tag "CXX" to libtool checking whether the c++ linker (/usr/home/gdt/NetBSD-current/pkgsrc/chat/pidgin-otr/work/.wrapper/bin/ld) supports shared libraries... ERROR: To use this compiler, you have to add c++ to ERROR: USE_LANGUAGES in the package Makefile. yes libtool.m4: error: problem compiling CXX test program checking for c++ option to produce PIC... checking if c++ static flag works... no checking if c++ supports -c -o file.o... no checking whether the c++ linker (/usr/home/gdt/NetBSD-current/pkgsrc/chat/pidgin-otr/work/.wrapper/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... ERROR: To use this compiler, you have to add c++ to ERROR: USE_LANGUAGES in the package Makefile. NetBSD ld.elf_so checking how to hardcode library paths into programs... unsupported appending configuration tag "F77" to libtool checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... no checking for f77 option to produce PIC... -fPIC checking if f77 PIC flag -fPIC works... no checking if f77 static flag -static works... no checking if f77 supports -c -o file.o... no checking whether the f77 linker (/usr/home/gdt/NetBSD-current/pkgsrc/chat/pidgin-otr/work/.wrapper/bin/ld) supports shared libraries... ERROR: To use this compiler, you have to add fortran to ERROR: USE_LANGUAGES in the package Makefile. yes checking dynamic linker characteristics... ERROR: To use this compiler, you have to add fortran to ERROR: USE_LANGUAGES in the package Makefile. ERROR: To use this compiler, you have to add fortran to ERROR: USE_LANGUAGES in the package Makefile. NetBSD ld.elf_so checking how to hardcode library paths into programs... immediate checking for libgcrypt-config... /usr/pkg/bin/libgcrypt-config checking for LIBGCRYPT - version >= 1.2.0... yes checking LIBGCRYPT API version... okay checking for libotr CFLAGS... checking for libotr LIBS... -lotr checking for libotr headers version 3.x >= 3.1.0... found. checking for otrl_message_receiving in -lotr... yes checking pkg-config is at least version 0.9.0... yes checking for EXTRA... yes checking for perl... /usr/pkg/bin/perl checking for XML::Parser... ok checking for iconv... /usr/bin/iconv checking for msgfmt... /usr/bin/msgfmt checking for msgmerge... /usr/bin/msgmerge checking for xgettext... /usr/bin/xgettext checking locale.h usability... yes checking locale.h presence... yes checking for locale.h... yes checking for LC_MESSAGES... yes checking libintl.h usability... yes checking libintl.h presence... yes checking for libintl.h... yes checking for ngettext in libc... no checking for bindtextdomain in -lintl... yes checking for ngettext in -lintl... yes checking for dgettext in -lintl... yes checking for bind_textdomain_codeset... yes checking for msgfmt... /usr/bin/msgfmt checking for dcgettext... yes checking for gmsgfmt... /usr/bin/msgfmt checking for xgettext... /usr/bin/xgettext checking for catalogs to be installed... nl configure: creating ./config.status config.status: creating Makefile config.status: creating po/Makefile.in config.status: creating config.h config.status: executing depfiles commands config.status: executing intltool commands config.status: executing default-1 commands config.status: executing po/stamp-it commands => Overriding intltool. WARNING: *** Please consider adding c++ to USE_LANGUAGES in the package Makefile. WARNING: *** Please consider adding fortran to USE_LANGUAGES in the package Makefile. ===> Building for pidgin-otr-3.1.0a2 --- all --- /usr/bin/make all-recursive --- all-recursive --- Making all in po --- otr-plugin.lo --- --- ui.lo --- --- dialogs.lo --- --- gtk-ui.lo --- --- otr-plugin.lo --- if /bin/sh ./libtool --tag=CC --mode=compile cc -DHAVE_CONFIG_H -I. -I. -I. -I/usr/pkg/include -I/usr/include -I/usr/pkg/include/freetype2 -I/usr/X11R6/include -I/usr/pkg/include -I/usr/pkg/include -O2 -DXTHREADS -I/usr/pkg/include/glib/glib-2.0 -I/usr/pkg/lib/glib-2.0/include -I/usr/pkg/include/gtk-2.0 -I/usr/pkg/lib/gtk-2.0/include -I/usr/pkg/include/atk-1.0 -I/usr/pkg/include/cairo -I/usr/pkg/include/pango-1.0 -I/usr/pkg/include -I/usr/X11R6/include -I/usr/pkg/include/freetype2 -I/usr/pkg/include/libpng12 -I/usr/pkg/include/pidgin -I/usr/pkg/include/libpurple -DUSING_GTK -DPURPLE_PLUGINS -DPIDGIN_OTR_VERSION=\"3.1.0\" -DLOCALEDIR=\"/usr/pkg/share/locale\" -O2 -I/usr/pkg/include -I/usr/include -I/usr/pkg/include/freetype2 -I/usr/X11R6/include -MT otr-plugin.lo -MD -MP -MF ".deps/otr-plugin.Tpo" -c -o otr-plugin.lo otr-plugin.c; then mv -f ".deps/otr-plugin.Tpo" ".deps/otr-plugin.Plo"; else rm -f ".deps/otr-plugin.Tpo"; exit 1; fi --- ui.lo --- if /bin/sh ./libtool --tag=CC --mode=compile cc -DHAVE_CONFIG_H -I. -I. -I. -I/usr/pkg/include -I/usr/include -I/usr/pkg/include/freetype2 -I/usr/X11R6/include -I/usr/pkg/include -I/usr/pkg/include -O2 -DXTHREADS -I/usr/pkg/include/glib/glib-2.0 -I/usr/pkg/lib/glib-2.0/include -I/usr/pkg/include/gtk-2.0 -I/usr/pkg/lib/gtk-2.0/include -I/usr/pkg/include/atk-1.0 -I/usr/pkg/include/cairo -I/usr/pkg/include/pango-1.0 -I/usr/pkg/include -I/usr/X11R6/include -I/usr/pkg/include/freetype2 -I/usr/pkg/include/libpng12 -I/usr/pkg/include/pidgin -I/usr/pkg/include/libpurple -DUSING_GTK -DPURPLE_PLUGINS -DPIDGIN_OTR_VERSION=\"3.1.0\" -DLOCALEDIR=\"/usr/pkg/share/locale\" -O2 -I/usr/pkg/include -I/usr/include -I/usr/pkg/include/freetype2 -I/usr/X11R6/include -MT ui.lo -MD -MP -MF ".deps/ui.Tpo" -c -o ui.lo ui.c; then mv -f ".deps/ui.Tpo" ".deps/ui.Plo"; else rm -f ".deps/ui.Tpo"; exit 1; fi --- dialogs.lo --- if /bin/sh ./libtool --tag=CC --mode=compile cc -DHAVE_CONFIG_H -I. -I. -I. -I/usr/pkg/include -I/usr/include -I/usr/pkg/include/freetype2 -I/usr/X11R6/include -I/usr/pkg/include -I/usr/pkg/include -O2 -DXTHREADS -I/usr/pkg/include/glib/glib-2.0 -I/usr/pkg/lib/glib-2.0/include -I/usr/pkg/include/gtk-2.0 -I/usr/pkg/lib/gtk-2.0/include -I/usr/pkg/include/atk-1.0 -I/usr/pkg/include/cairo -I/usr/pkg/include/pango-1.0 -I/usr/pkg/include -I/usr/X11R6/include -I/usr/pkg/include/freetype2 -I/usr/pkg/include/libpng12 -I/usr/pkg/include/pidgin -I/usr/pkg/include/libpurple -DUSING_GTK -DPURPLE_PLUGINS -DPIDGIN_OTR_VERSION=\"3.1.0\" -DLOCALEDIR=\"/usr/pkg/share/locale\" -O2 -I/usr/pkg/include -I/usr/include -I/usr/pkg/include/freetype2 -I/usr/X11R6/include -MT dialogs.lo -MD -MP -MF ".deps/dialogs.Tpo" -c -o dialogs.lo dialogs.c; then mv -f ".deps/dialogs.Tpo" ".deps/dialogs.Plo"; else rm -f ".deps/dialogs.Tpo"; exit 1; fi --- gtk-ui.lo --- if /bin/sh ./libtool --tag=CC --mode=compile cc -DHAVE_CONFIG_H -I. -I. -I. -I/usr/pkg/include -I/usr/include -I/usr/pkg/include/freetype2 -I/usr/X11R6/include -I/usr/pkg/include -I/usr/pkg/include -O2 -DXTHREADS -I/usr/pkg/include/glib/glib-2.0 -I/usr/pkg/lib/glib-2.0/include -I/usr/pkg/include/gtk-2.0 -I/usr/pkg/lib/gtk-2.0/include -I/usr/pkg/include/atk-1.0 -I/usr/pkg/include/cairo -I/usr/pkg/include/pango-1.0 -I/usr/pkg/include -I/usr/X11R6/include -I/usr/pkg/include/freetype2 -I/usr/pkg/include/libpng12 -I/usr/pkg/include/pidgin -I/usr/pkg/include/libpurple -DUSING_GTK -DPURPLE_PLUGINS -DPIDGIN_OTR_VERSION=\"3.1.0\" -DLOCALEDIR=\"/usr/pkg/share/locale\" -O2 -I/usr/pkg/include -I/usr/include -I/usr/pkg/include/freetype2 -I/usr/X11R6/include -MT gtk-ui.lo -MD -MP -MF ".deps/gtk-ui.Tpo" -c -o gtk-ui.lo gtk-ui.c; then mv -f ".deps/gtk-ui.Tpo" ".deps/gtk-ui.Plo"; else rm -f ".deps/gtk-ui.Tpo"; exit 1; fi mkdir .libs cc -DHAVE_CONFIG_H -I. -I. -I. -I/usr/pkg/include -I/usr/include -I/usr/pkg/include/freetype2 -I/usr/X11R6/include -I/usr/pkg/include -I/usr/pkg/include -O2 -DXTHREADS -I/usr/pkg/include/glib/glib-2.0 -I/usr/pkg/lib/glib-2.0/include -I/usr/pkg/include/gtk-2.0 -I/usr/pkg/lib/gtk-2.0/include -I/usr/pkg/include/atk-1.0 -I/usr/pkg/include/cairo -I/usr/pkg/include/pango-1.0 -I/usr/pkg/include -I/usr/X11R6/include -I/usr/pkg/include/freetype2 -I/usr/pkg/include/libpng12 -I/usr/pkg/include/pidgin -I/usr/pkg/include/libpurple -DUSING_GTK -DPURPLE_PLUGINS -DPIDGIN_OTR_VERSION=\"3.1.0\" -DLOCALEDIR=\"/usr/pkg/share/locale\" -O2 -I/usr/pkg/include -I/usr/include -I/usr/pkg/include/freetype2 -I/usr/X11R6/include -MT gtk-ui.lo -MD -MP -MF .deps/gtk-ui.Tpo -c gtk-ui.c -fPIC -DPIC -o .libs/gtk-ui.o --- dialogs.lo --- cc -DHAVE_CONFIG_H -I. -I. -I. -I/usr/pkg/include -I/usr/include -I/usr/pkg/include/freetype2 -I/usr/X11R6/include -I/usr/pkg/include -I/usr/pkg/include -O2 -DXTHREADS -I/usr/pkg/include/glib/glib-2.0 -I/usr/pkg/lib/glib-2.0/include -I/usr/pkg/include/gtk-2.0 -I/usr/pkg/lib/gtk-2.0/include -I/usr/pkg/include/atk-1.0 -I/usr/pkg/include/cairo -I/usr/pkg/include/pango-1.0 -I/usr/pkg/include -I/usr/X11R6/include -I/usr/pkg/include/freetype2 -I/usr/pkg/include/libpng12 -I/usr/pkg/include/pidgin -I/usr/pkg/include/libpurple -DUSING_GTK -DPURPLE_PLUGINS -DPIDGIN_OTR_VERSION=\"3.1.0\" -DLOCALEDIR=\"/usr/pkg/share/locale\" -O2 -I/usr/pkg/include -I/usr/include -I/usr/pkg/include/freetype2 -I/usr/X11R6/include -MT dialogs.lo -MD -MP -MF .deps/dialogs.Tpo -c dialogs.c -fPIC -DPIC -o .libs/dialogs.o --- otr-plugin.lo --- cc -DHAVE_CONFIG_H -I. -I. -I. -I/usr/pkg/include -I/usr/include -I/usr/pkg/include/freetype2 -I/usr/X11R6/include -I/usr/pkg/include -I/usr/pkg/include -O2 -DXTHREADS -I/usr/pkg/include/glib/glib-2.0 -I/usr/pkg/lib/glib-2.0/include -I/usr/pkg/include/gtk-2.0 -I/usr/pkg/lib/gtk-2.0/include -I/usr/pkg/include/atk-1.0 -I/usr/pkg/include/cairo -I/usr/pkg/include/pango-1.0 -I/usr/pkg/include -I/usr/X11R6/include -I/usr/pkg/include/freetype2 -I/usr/pkg/include/libpng12 -I/usr/pkg/include/pidgin -I/usr/pkg/include/libpurple -DUSING_GTK -DPURPLE_PLUGINS -DPIDGIN_OTR_VERSION=\"3.1.0\" -DLOCALEDIR=\"/usr/pkg/share/locale\" -O2 -I/usr/pkg/include -I/usr/include -I/usr/pkg/include/freetype2 -I/usr/X11R6/include -MT otr-plugin.lo -MD -MP -MF .deps/otr-plugin.Tpo -c otr-plugin.c -fPIC -DPIC -o .libs/otr-plugin.o --- ui.lo --- cc -DHAVE_CONFIG_H -I. -I. -I. -I/usr/pkg/include -I/usr/include -I/usr/pkg/include/freetype2 -I/usr/X11R6/include -I/usr/pkg/include -I/usr/pkg/include -O2 -DXTHREADS -I/usr/pkg/include/glib/glib-2.0 -I/usr/pkg/lib/glib-2.0/include -I/usr/pkg/include/gtk-2.0 -I/usr/pkg/lib/gtk-2.0/include -I/usr/pkg/include/atk-1.0 -I/usr/pkg/include/cairo -I/usr/pkg/include/pango-1.0 -I/usr/pkg/include -I/usr/X11R6/include -I/usr/pkg/include/freetype2 -I/usr/pkg/include/libpng12 -I/usr/pkg/include/pidgin -I/usr/pkg/include/libpurple -DUSING_GTK -DPURPLE_PLUGINS -DPIDGIN_OTR_VERSION=\"3.1.0\" -DLOCALEDIR=\"/usr/pkg/share/locale\" -O2 -I/usr/pkg/include -I/usr/include -I/usr/pkg/include/freetype2 -I/usr/X11R6/include -MT ui.lo -MD -MP -MF .deps/ui.Tpo -c ui.c -fPIC -DPIC -o .libs/ui.o --- gtk-dialog.lo --- if /bin/sh ./libtool --tag=CC --mode=compile cc -DHAVE_CONFIG_H -I. -I. -I. -I/usr/pkg/include -I/usr/include -I/usr/pkg/include/freetype2 -I/usr/X11R6/include -I/usr/pkg/include -I/usr/pkg/include -O2 -DXTHREADS -I/usr/pkg/include/glib/glib-2.0 -I/usr/pkg/lib/glib-2.0/include -I/usr/pkg/include/gtk-2.0 -I/usr/pkg/lib/gtk-2.0/include -I/usr/pkg/include/atk-1.0 -I/usr/pkg/include/cairo -I/usr/pkg/include/pango-1.0 -I/usr/pkg/include -I/usr/X11R6/include -I/usr/pkg/include/freetype2 -I/usr/pkg/include/libpng12 -I/usr/pkg/include/pidgin -I/usr/pkg/include/libpurple -DUSING_GTK -DPURPLE_PLUGINS -DPIDGIN_OTR_VERSION=\"3.1.0\" -DLOCALEDIR=\"/usr/pkg/share/locale\" -O2 -I/usr/pkg/include -I/usr/include -I/usr/pkg/include/freetype2 -I/usr/X11R6/include -MT gtk-dialog.lo -MD -MP -MF ".deps/gtk-dialog.Tpo" -c -o gtk-dialog.lo gtk-dialog.c; then mv -f ".deps/gtk-dialog.Tpo" ".deps/gtk-dialog.Plo"; else rm -f ".deps/gtk-dialog.Tpo"; exit 1; fi cc -DHAVE_CONFIG_H -I. -I. -I. -I/usr/pkg/include -I/usr/include -I/usr/pkg/include/freetype2 -I/usr/X11R6/include -I/usr/pkg/include -I/usr/pkg/include -O2 -DXTHREADS -I/usr/pkg/include/glib/glib-2.0 -I/usr/pkg/lib/glib-2.0/include -I/usr/pkg/include/gtk-2.0 -I/usr/pkg/lib/gtk-2.0/include -I/usr/pkg/include/atk-1.0 -I/usr/pkg/include/cairo -I/usr/pkg/include/pango-1.0 -I/usr/pkg/include -I/usr/X11R6/include -I/usr/pkg/include/freetype2 -I/usr/pkg/include/libpng12 -I/usr/pkg/include/pidgin -I/usr/pkg/include/libpurple -DUSING_GTK -DPURPLE_PLUGINS -DPIDGIN_OTR_VERSION=\"3.1.0\" -DLOCALEDIR=\"/usr/pkg/share/locale\" -O2 -I/usr/pkg/include -I/usr/include -I/usr/pkg/include/freetype2 -I/usr/X11R6/include -MT gtk-dialog.lo -MD -MP -MF .deps/gtk-dialog.Tpo -c gtk-dialog.c -fPIC -DPIC -o .libs/gtk-dialog.o --- pidgin-otr.la --- /bin/sh ./libtool --tag=CC --mode=link cc -I/usr/pkg/include -I/usr/pkg/include -O2 -DXTHREADS -I/usr/pkg/include/glib/glib-2.0 -I/usr/pkg/lib/glib-2.0/include -I/usr/pkg/include/gtk-2.0 -I/usr/pkg/lib/gtk-2.0/include -I/usr/pkg/include/atk-1.0 -I/usr/pkg/include/cairo -I/usr/pkg/include/pango-1.0 -I/usr/pkg/include -I/usr/X11R6/include -I/usr/pkg/include/freetype2 -I/usr/pkg/include/libpng12 -I/usr/pkg/include/pidgin -I/usr/pkg/include/libpurple -DUSING_GTK -DPURPLE_PLUGINS -DPIDGIN_OTR_VERSION=\"3.1.0\" -DLOCALEDIR=\"/usr/pkg/share/locale\" -O2 -I/usr/pkg/include -I/usr/include -I/usr/pkg/include/freetype2 -I/usr/X11R6/include -L/usr/pkg/lib -Wl,-R/usr/pkg/lib -L/usr/lib -Wl,-R/usr/lib -L/usr/X11R6/lib -Wl,-R/usr/X11R6/lib -o pidgin-otr.la -rpath /usr/pkg/lib/pidgin -module -avoid-version -L/usr/pkg/lib -Wl,-R/usr/pkg/lib -lgcrypt -Wl,-R/usr/pkg/lib -L/usr/pkg/lib -lgpg-error -lotr otr-plugin.lo ui.lo dialogs.lo gtk-ui.lo gtk-dialog.lo cc -shared .libs/otr-plugin.o .libs/ui.o .libs/dialogs.o .libs/gtk-ui.o .libs/gtk-dialog.o -Wl,--rpath -Wl,/usr/pkg/lib -Wl,--rpath -Wl,/usr/pkg/lib -L/usr/pkg/lib -L/usr/lib -L/usr/X11R6/lib /usr/pkg/lib/libgcrypt.so /usr/pkg/lib/libgpg-error.so /usr/pkg/lib/libotr.so -Wl,-R/usr/pkg/lib -Wl,-R/usr/lib -Wl,-R/usr/X11R6/lib -Wl,-R/usr/pkg/lib -Wl,-R/usr/pkg/lib -Wl,-soname -Wl,pidgin-otr.so -o .libs/pidgin-otr.so creating pidgin-otr.la (cd .libs && rm -f pidgin-otr.la && ln -s ../pidgin-otr.la pidgin-otr.la) *** Please use pkgtools/verifypc to sanity check dependencies. => Unwrapping files-to-be-installed. INSTALL LOG => Required installed package digest>=20010302: digest-20070703 found => Required installed package checkperms>=1.1: checkperms-1.7 found ===> Replacing for pidgin-otr-3.1.0a2 WARNING: experimental target - DATA LOSS MAY OCCUR. Creating binary package: pidgin-otr-3.1.0a2 Creating package /usr/home/gdt/NetBSD-current/pkgsrc/chat/pidgin-otr/work/pidgin-otr-3.1.0a2.tgz Registering depends: pidgin>=2.0.1nb1 libotr>=3.0.0 libgcrypt>=1.2.0 gtk2+>=2.4.0 glib2>=2.4.0. Registering conflicts:. => Preserving existing +REQUIRED_BY file. ===> Deinstalling for pidgin-otr-3.1.0a2 Running /usr/sbin/pkg_delete -K /var/db/pkg pidgin-otr-3.1.0a2 ===> Installing for pidgin-otr-3.1.0a2 => Generating pre-install file lists Making install in po /usr/home/gdt/NetBSD-current/pkgsrc/chat/pidgin-otr/work/pidgin-otr-3.1.0/install-sh -d /usr/pkg/share/locale if test -n ""; then linguas=""; else linguas="nl"; fi; for lang in $linguas; do dir=/usr/pkg/share/locale/$lang/LC_MESSAGES; /usr/home/gdt/NetBSD-current/pkgsrc/chat/pidgin-otr/work/pidgin-otr-3.1.0/install-sh -d $dir; if test -r $lang.gmo; then /usr/bin/install -c -o root -g wheel -m 444 $lang.gmo $dir/pidgin-otr.mo; echo "installing $lang.gmo as $dir/pidgin-otr.mo"; else /usr/bin/install -c -o root -g wheel -m 444 ./$lang.gmo $dir/pidgin-otr.mo; echo "installing ./$lang.gmo as" "$dir/pidgin-otr.mo"; fi; if test -r $lang.gmo.m; then /usr/bin/install -c -o root -g wheel -m 444 $lang.gmo.m $dir/pidgin-otr.mo.m; echo "installing $lang.gmo.m as $dir/pidgin-otr.mo.m"; else if test -r ./$lang.gmo.m ; then /usr/bin/install -c -o root -g wheel -m 444 ./$lang.gmo.m $dir/pidgin-otr.mo.m; echo "installing ./$lang.gmo.m as" "$dir/pidgin-otr.mo.m"; else true; fi; fi; done install: ./nl.gmo: stat: No such file or directory installing ./nl.gmo as /usr/pkg/share/locale/nl/LC_MESSAGES/pidgin-otr.mo test -z "/usr/pkg/lib/pidgin" || /usr/home/gdt/NetBSD-current/pkgsrc/chat/pidgin-otr/work/pidgin-otr-3.1.0/install-sh -d "/usr/pkg/lib/pidgin" /bin/sh ./libtool --mode=install /usr/bin/install -c -o root -g wheel 'pidgin-otr.la' '/usr/pkg/lib/pidgin/pidgin-otr.la' /usr/bin/install -c -o root -g wheel .libs/pidgin-otr.so /usr/pkg/lib/pidgin/pidgin-otr.so /usr/bin/install -c -o root -g wheel .libs/pidgin-otr.lai /usr/pkg/lib/pidgin/pidgin-otr.la ---------------------------------------------------------------------- Libraries have been installed in: /usr/pkg/lib/pidgin If you ever happen to want to link against installed libraries in a given directory, LIBDIR, you must either use libtool, and specify the full pathname of the library, or use the `-LLIBDIR' flag during linking and do at least one of the following: - add LIBDIR to the `LD_LIBRARY_PATH' environment variable during execution - add LIBDIR to the `LD_RUN_PATH' environment variable during linking - use the `-Wl,--rpath -Wl,LIBDIR' linker flag - have your system administrator add LIBDIR to `/etc/ld.so.conf' See any operating system documentation about shared libraries for more information, such as the ld(1) and ld.so(8) manual pages. ---------------------------------------------------------------------- => Automatic manual page handling => Generating post-install file lists => Registering installation for pidgin-otr-3.1.0a2 pidgin-otr-3.1.0a2 requires installed package glib2-2.12.13 pidgin-otr-3.1.0a2 requires installed package gtk2+-2.10.14 pidgin-otr-3.1.0a2 requires installed package libgcrypt-1.2.4 pidgin-otr-3.1.0a2 requires installed package libotr-3.1.0 pidgin-otr-3.1.0a2 requires installed package pidgin-2.0.1nb1 => Checking file-check results for pidgin-otr-3.1.0a2 => Checking file permissions in pidgin-otr-3.1.0a2 => Checking for missing run-time search paths in pidgin-otr-3.1.0a2 => Checking for work-directory references in pidgin-otr-3.1.0a2 => Fixing @pkgdep entries in dependent packages. From ian at cypherpunks.ca Sun Jul 29 11:14:20 2007 From: ian at cypherpunks.ca (Ian Goldberg) Date: Sun, 29 Jul 2007 11:14:20 -0400 Subject: [OTR-dev] libotr major version bump? In-Reply-To: References: <20070728181440.GO3751@yoink.cs.uwaterloo.ca> Message-ID: <20070729151420.GT3751@yoink.cs.uwaterloo.ca> On Sun, Jul 29, 2007 at 07:34:33AM -0400, Greg Troxel wrote: > Ian Goldberg writes: > > > That's weird. When I build libotr-3.1.0, I get a "libotr.so.2.1.0", as > > expected, since the API and ABI are indeed back-compatible. > > > > libotr's configure.ac indicates: > > > > LIBOTR_LIBTOOL_VERSION="3:0:1" > > > > which specifies current=3, revision=0, age=1, so you get 2.1.0 out of > > that. > > > > What version number is libtool using for you? > > In config.status: > > s, at LIBOTR_LIBTOOL_VERSION@,3:0:1,;t t > > > and this is passed to libtool, but it makes so.3.0 > > > poblano gdt 22 /usr/pkgsrc/chat/libotr/work/libotr-3.1.0/src > gmake > /bin/sh ../libtool --tag=CC --mode=link cc -O2 -I/usr/pkg/include -I/usr/include -L/usr/pkg/lib -Wl,-R/usr/pkg/lib -L/usr/lib -Wl,-R/usr/lib -o libotr.la -rpath /usr/pkg/lib -version-info 3:0:1 -L/usr/pkg/lib -Wl,-R/usr/pkg/lib -lgcrypt -Wl,-R/usr/pkg/lib -L/usr/pkg/lib -lgpg-error privkey.lo context.lo proto.lo b64.lo dh.lo mem.lo message.lo userstate.lo tlv.lo auth.lo sm.lo > cc -shared .libs/privkey.o .libs/context.o .libs/proto.o .libs/b64.o .libs/dh.o .libs/mem.o .libs/message.o .libs/userstate.o .libs/tlv.o .libs/auth.o .libs/sm.o -Wl,--rpath -Wl,/usr/pkg/lib -Wl,--rpath -Wl,/usr/pkg/lib -L/usr/pkg/lib -L/usr/lib /usr/pkg/lib/libgcrypt.so /usr/pkg/lib/libgpg-error.so -Wl,-R/usr/pkg/lib -Wl,-R/usr/lib -Wl,-R/usr/pkg/lib -Wl,-R/usr/pkg/lib -Wl,-soname -Wl,libotr.so.3 -o .libs/libotr.so.3.0 > (cd .libs && rm -f libotr.so.3 && ln -s libotr.so.3.0 libotr.so.3) > (cd .libs && rm -f libotr.so && ln -s libotr.so.3.0 libotr.so) > ar cru .libs/libotr.a privkey.o context.o proto.o b64.o dh.o mem.o message.o userstate.o tlv.o auth.o sm.o > ranlib .libs/libotr.a > creating libotr.la > (cd .libs && rm -f libotr.la && ln -s ../libotr.la libotr.la) > > I have libtool 1.5.22, but I'm 99% sure that the above runs the libtool > that was generated by you at 'make dist' time. I also have 1.5.22: $ libtool --version ltmain.sh (GNU libtool) 1.5.22 Debian 1.5.22-2 (1.1220.2.365 2005/12/18 22:14:06) Copyright (C) 2005 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. > So I read the pkgsrc documentation and added USE_LIBTOOL=yes, so that > the included libtool script would get overwritten with one that's been > fixed for all the platforms pkgsrc runs on. Then I get the right shlib > number. > > -rwxr-xr-x 1 root wheel 74300 Jul 29 07:32 /usr/pkg/lib/libotr.so.2.1.0 > > I don't understand this - I think it means that just building libotr not > with pkgsrc will get the wrong version. I can remove the libtool > override, add -x to libtool, and send that if you want to look, but I > don't understand libtool innards. I don't either, unfortunately. But it probably wouldn't hurt. > > libotr's UPDATING file contains the information about how users of > > libotr can update their code for the new version. > > Thanks - I see you've been quite careful about upgrading issues. Yeah. Our plans for the next version will almost certainly require an API change, but we wanted to make this version back-compatible. - Ian From ian at cypherpunks.ca Sun Jul 29 11:22:33 2007 From: ian at cypherpunks.ca (Ian Goldberg) Date: Sun, 29 Jul 2007 11:22:33 -0400 Subject: [OTR-dev] libotr and pidgin-otr 3.1.0-preview2 available In-Reply-To: References: <20070724201104.GN23980@thunk.cs.uwaterloo.ca> <20070726165742.GO24420@thunk.cs.uwaterloo.ca> Message-ID: <20070729152233.GU3751@yoink.cs.uwaterloo.ca> On Sun, Jul 29, 2007 at 08:02:30AM -0400, Greg Troxel wrote: > http://otr.cypherpunks.ca/pidgin-otr-3.1.0-preview2.tar.gz > > During the install, I get errors about nl.gmo. See build log appended. > I don't understand how this is supposed to work. > > BUILD LOG > > ===> Building for pidgin-otr-3.1.0a2 > --- all --- > /usr/bin/make all-recursive > --- all-recursive --- > Making all in po > --- otr-plugin.lo --- This isn't working right; the Makefile in po should have built nl.gmo here, using msgfmt. My output: Making all in po make[2]: Entering directory `/home/iang/uw/research/otr/sf/gaim-otr/po' file=`echo nl | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file nl.po make[2]: Leaving directory `/home/iang/uw/research/otr/sf/gaim-otr/po' Can you see what's going on in po/Makefile? > INSTALL LOG > > install: ./nl.gmo: stat: No such file or directory > installing ./nl.gmo as /usr/pkg/share/locale/nl/LC_MESSAGES/pidgin-otr.mo Then of course it fails to install it, since it didn't build. Thanks, - Ian From nix at go-nix.ca Sun Jul 29 12:37:02 2007 From: nix at go-nix.ca (Gabriel Schulhof) Date: Sun, 29 Jul 2007 19:37:02 +0300 Subject: [OTR-dev] A few UI patches Message-ID: <1185727022.30144.43.camel@idefix.go-nix.ca> Hi! I maintain a port of pidgin and pidgin-otr for Internet tablets. From a UI point of view, this means a mouse that cannot move but only click and drag, no right-click (but there's tap-and-hold), and no keyboard (except on-screen via GTK input methods). I have created a few UI patches for pidgin-otr. My main motivation is, of course, to make pidgin-otr usable on Internet tablets, however, I believe that some of my modifications are useful/good-looking enough to be considered for pidgin-otr on the desktop. I have lightly tested these patches both on the desktop and on the Internet tablet. The patches are available in the directory at ftp://go-nix.ca/incoming/pidgin-otr-patches/ Brief per-patch explanations: otr-button.diff: - Replace the button that goes into the conversation window with a GtkFrame containing two buttons: The original button on top, and a button labelled "Actions..." below it. The original button's behaviour is unchanged. The "Actions..." button causes the right-click menu to be popped up. In this sense, it behaves a little bit like a GtkOptionMenu. otr-clist-to-treeview.diff: - Remove the deprecated GtkCList widget and replace it with a GtkTreeView. This change allows for several UI "spruce-ups": - You can use pixbufs (same as those used on the button) to illustrate the current status for each fingerprint in the list (instead of mere text like "Private", "Not private", etc.) - You can use checkboxes to indicate whether the fingerprint is verified (again, instead of mere text like "Yes" and "No") To make it possible to use the same pixbufs in both the button and the tree view, I had to move the xpm static data from gtk-dialogs.c to gtk-ui.c and create a function that converts the static data to a GdkPixbuf. The otr_icon function then uses this new function (whose prototype is in gtk-ui.h, now included from gtk-dialog.h) to create the GtkImage as before. A side effect of this is that these pixbufs can now be used to make the four "Verify fingerprint", "Start private connection", etc. buttons look better by putting an image on them. I used the following images: "Start private connection" TRUST_PRIVATE "End private connection" TRUST_FINISHED "Verify fingerprint" GTK_STOCK_YES "Forget fingerprint" GTK_STOCK_DELETE otr-explanation-via-imhtml.diff: - Replace the GtkExpander-within-GtkExpander arrangement with only the outer GtkExpander, and render the inner GtkExpander as a link inside GtkIMHTML markup. IOW, there is now only one expander containing a scrolled window with a GtkIMHTML inside. The IMHTML widget contains the initial explanation, plus a link labelled "+ Explain further". When clicked, the url-clicked handler deletes all text starting with the "+" and up to the end of the GtkIMHTML and replaces it with a link labelled "- Hide explanation" and the longer explanation. URLs in the longer explanation are opened in the Web browser via purple_notify_uri as before. When the user clicks "- Hide explanation" it toggles back to "+ Explain further". Caveat: The long explanation causes the imhtml to scroll to the end. There is code in place to put "- Hide explanation" and the beginning of the long explanation to the top of the imhtml when the user clicks "+ Explain further". This code works in 2.0.2, but there has been a regression since then whereby pidgin seems to ignore the GTK_IMHTML_NO_SCROLL flag in the gtk_imhtml_append_text call. I posted a bug about it: http://developer.pidgin.im/ticket/2315 otr-generate-key-via-thread.diff: - Do not freeze Pidgin while generating a key. GLib provides several preprocessor directives which can bracket code that uses threads so that, if compiled, it's very, very likely to also work at runtime. pidgin-otr already has a mechanism for blocking the generate() function so that it only returns after the key is done. Unfortunately, the key is generated on the main thread, blocking the GMain event handling code. I have pushed the function onto a new GThread. I use the main loop to tell the main thread that generation is complete in the following way: The new GThread adds an idle handler to the main context and quits. The idle handler, which runs in the main thread, toggles a boolean variable and removes itself from the list of sources. The boolean variable then unblocks the code as before. The upshot is that Pidgin remains responsive while a key is being generated. Caveat: - The user can quit Pidgin while a key is being generated. This causes a segfault. Not a typical use case though, I would think. - Cannot start a private conversation while a key is being generated because gcrypt fails with some assertion otr-pidgin-frames-and-spacings: - Make the plugin configure dialog look more like Pidgin's own preferences dialog. I have replaced the GtkFrame widgets used to enclose the various groups of settings with pidgin_make_frame. I have also replaced numerous hard-coded border widths and spacings with Pidgin's #defined spacing and border width values PIDGIN_HIG_BORDER, PIDGIN_HIG_CAT_SPACE, and PIDGIN_HIG_BOX_SPACE. In addition to the above changes, I have, in some places changed the arrangement of widgets a little bit (cleaning things up, perhaps). For example, instead of a GtkHBox with two empty labels with the aim of centering a widget between them, I used a GtkAlignment. I have created a demo of my changes: http://www.youtube.com/watch?v=zPtnlqEZPeY Please let me know what you think! Gabriel From mail at scottellis.com.au Mon Jul 30 20:24:50 2007 From: mail at scottellis.com.au (Scott Ellis) Date: Tue, 31 Jul 2007 10:24:50 +1000 Subject: [OTR-dev] add_appdata not called (3.1)? Message-ID: <96e269140707301724k61097756n80cfadf37e6ea941@mail.gmail.com> Hi All, FYI - Just upgraded to libotr 3.1, and it seems that the 'add_appdata' callback isn't functioning any longer. Scott -------------- next part -------------- An HTML attachment was scrubbed... URL: From ian at cypherpunks.ca Mon Jul 30 21:12:14 2007 From: ian at cypherpunks.ca (Ian Goldberg) Date: Mon, 30 Jul 2007 21:12:14 -0400 Subject: [OTR-dev] add_appdata not called (3.1)? In-Reply-To: <96e269140707301724k61097756n80cfadf37e6ea941@mail.gmail.com> References: <96e269140707301724k61097756n80cfadf37e6ea941@mail.gmail.com> Message-ID: <20070731011214.GD3751@yoink.cs.uwaterloo.ca> On Tue, Jul 31, 2007 at 10:24:50AM +1000, Scott Ellis wrote: > Hi All, > > FYI - Just upgraded to libotr 3.1, and it seems that the 'add_appdata' > callback isn't functioning any longer. Huh. It looks like it's still being called. Can you be more specific? otrl_message_sending and otrl_message_receiving each call otrl_context_find with the add_appdata parameter, and that routine hasn't changed in over two years. Thanks, - Ian From mail at scottellis.com.au Mon Jul 30 22:03:34 2007 From: mail at scottellis.com.au (Scott Ellis) Date: Tue, 31 Jul 2007 12:03:34 +1000 Subject: [OTR-dev] add_appdata not called (3.1)? In-Reply-To: <20070731011214.GD3751@yoink.cs.uwaterloo.ca> References: <96e269140707301724k61097756n80cfadf37e6ea941@mail.gmail.com> <20070731011214.GD3751@yoink.cs.uwaterloo.ca> Message-ID: <96e269140707301903i330cddectc4a9edbde4bb2ba3@mail.gmail.com> you're completely correct - i didn't reallise it was also being called by the 'read fingerprints' function. sorry. On 7/31/07, Ian Goldberg wrote: > > On Tue, Jul 31, 2007 at 10:24:50AM +1000, Scott Ellis wrote: > > Hi All, > > > > FYI - Just upgraded to libotr 3.1, and it seems that the 'add_appdata' > > callback isn't functioning any longer. > > Huh. It looks like it's still being called. Can you be more specific? > > otrl_message_sending and otrl_message_receiving each call > otrl_context_find with the add_appdata parameter, and that routine > hasn't changed in over two years. > > Thanks, > > - Ian > _______________________________________________ > OTR-dev mailing list > OTR-dev at lists.cypherpunks.ca > http://lists.cypherpunks.ca/mailman/listinfo/otr-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul at cypherpunks.ca Tue Jul 31 13:58:21 2007 From: paul at cypherpunks.ca (Paul Wouters) Date: Tue, 31 Jul 2007 13:58:21 -0400 (EDT) Subject: [OTR-dev] Slovak translation by Milan Plzik Message-ID: Attached is the Slovak translation for pidgin-otr Paul -------------- next part -------------- # SOME DESCRIPTIVE TITLE. # Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER # This file is distributed under the same license as the PACKAGE package. # FIRST AUTHOR , YEAR. # #, fuzzy msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2007-07-24 15:47-0400\n" "PO-Revision-Date: 2007-07-31 19:48+0200\n" "Last-Translator: Milan Plzik \n" "Language-Team: Slovak \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf8\n" "Content-Transfer-Encoding: 8bit\n" #: ../gtk-dialog.c:913 ../gtk-dialog.c:2095 msgid "_What's this?" msgstr "??o je _toto?" #: ../gtk-dialog.c:924 msgid "_More..." msgstr "_Viac..." #. Create the Advanced... button, and left-justify it. This #. * involves adding the button, and a blank label as a spacer, and #. * reordering them so that they're at the beginning. #: ../gtk-dialog.c:980 msgid "Advanced..." msgstr "Roz????ren??..." #: ../gtk-dialog.c:1025 msgid "Enter secret here" msgstr "" #: ../gtk-dialog.c:1030 msgid "This buddy is already authenticated." msgstr "Tento priate?? u?? je autentifikovan??." #: ../gtk-dialog.c:1049 msgid "" "To authenticate, pick a secret known only to you and your buddy. Enter this " "secret, then wait for your buddy to enter it too. If the secrets don't " "match, then you may be talking to an imposter." msgstr "" "Na autentifik??ciu pou??ite heslo, ktor?? pozn??te iba Vy a priate??. Zadajte toto " "heslo a po??kajte, k??m ho zad?? aj priate??. Ak sa hesl?? nezhoduj??, je riziko, " "??e sa rozpr??vate s podvodn??kom." #: ../gtk-dialog.c:1053 msgid "" "If your buddy uses multiple IM accounts or multiple computers, you may have " "to authenticate multiple times. However, as long as they use an account and " "computer that you've seen before, you don't need to authenticate each " "individual conversation." msgstr "" "Ak V???? priate?? pou????va viacero IM kont alebo viacero po????ta??ov, mo??no ho " "budete musiet autentifikova?? viackr??t. Av??ak, pokia?? pou????va konto a po????ta??, " "ktor?? ste u?? videli, netreba autentifikova?? ka??d?? rozhovor." #: ../gtk-dialog.c:1058 ../gtk-dialog.c:1322 ../gtk-dialog.c:1326 #: ../gtk-dialog.c:1423 ../gtk-dialog.c:1590 ../gtk-dialog.c:1750 #: ../gtk-dialog.c:1850 ../gtk-dialog.c:1935 msgid "?lang=en" msgstr "?lang=sk" #: ../gtk-dialog.c:1059 msgid "Click here for more information about authentication in OTR." msgstr "Kliknite sem pre viac inform??ci?? o autentifik??cii v OTR." #: ../gtk-dialog.c:1063 msgid "" "Authenticating a buddy helps ensure that the person you are talking to is " "who they claim to be." msgstr "" "Autentifik??cia priate??a pom??ha zabezpe??i??, ??e osoba, s ktorou sa rozpr??vate, " "je skuto??ne t??, za ktor?? sa vyd??va." #: ../gtk-dialog.c:1113 msgid "Authenticating Buddy" msgstr "Autentifikujem priate??a." #: ../gtk-dialog.c:1140 msgid "Authenticating" msgstr "Autentifikujem" #: ../gtk-dialog.c:1201 msgid "Generating private key" msgstr "Generujem s??kromn?? k??????" #: ../gtk-dialog.c:1202 msgid "Please wait" msgstr "Pros??m ??akajte" #: ../gtk-dialog.c:1210 ../gtk-dialog.c:1627 ../gtk-dialog.c:1664 #: ../gtk-ui.c:175 ../otr-plugin.c:115 ../otr-plugin.c:212 ../ui.c:110 msgid "Unknown" msgstr "Nezn??my" #. Create the Please Wait... dialog #: ../gtk-dialog.c:1213 #, c-format msgid "Generating private key for %s (%s)..." msgstr "Generujem s??kromn?? k?????? pre %s (%s)..." #: ../gtk-dialog.c:1258 #, c-format msgid "%s Done." msgstr "%s Dokon??en??." #: ../gtk-dialog.c:1320 #, c-format msgid "" "%s is contacting you from an unrecognized computer. You should authenticate this buddy." msgstr "" "%s v??s kontaktuje z nezn??meho po????ta??a. Tohto priate??a by ste mali autentifikova??." #: ../gtk-dialog.c:1324 #, c-format msgid "" "%s has not been authenticated yet. You should authenticate this buddy." msgstr "" "%s e??te nebol autentifikovan??. Tohto priate??a by ste mali " "autentifikova??." #: ../gtk-dialog.c:1365 ../gtk-ui.c:76 msgid "Finished" msgstr "Dokon??en??" #: ../gtk-dialog.c:1366 ../gtk-ui.c:75 msgid "Private" msgstr "S??kromn??" #: ../gtk-dialog.c:1367 ../gtk-ui.c:74 msgid "Unverified" msgstr "Neoveren??" #: ../gtk-dialog.c:1368 ../gtk-ui.c:73 msgid "Not private" msgstr "Nes??kromn??" #: ../gtk-dialog.c:1370 msgid "Start a private conversation" msgstr "Za??a?? s??kromn?? rozhovor" #: ../gtk-dialog.c:1371 msgid "Refresh the private conversation" msgstr "Obnovi?? s??kromn?? rozhovor" #: ../gtk-dialog.c:1375 msgid "Start _private conversation" msgstr "Za??a?? _s??kromn?? rozhovor" #: ../gtk-dialog.c:1376 msgid "Refresh _private conversation" msgstr "Obnovi?? _s??kromn?? rozhovor" #: ../gtk-dialog.c:1555 msgid "I have not" msgstr "Neoveril som," #: ../gtk-dialog.c:1556 msgid "I have" msgstr "Overil som," #: ../gtk-dialog.c:1558 msgid " verified that this is in fact the correct" msgstr " ??e toto je ten spr??vny" #: ../gtk-dialog.c:1567 #, c-format msgid "fingerprint for %s." msgstr "odtla??ok prsta pre %s." #: ../gtk-dialog.c:1579 msgid "" "To verify the fingerprint, contact your buddy via some other " "authenticated channel, such as the telephone or GPG-signed email. Each of " "you should tell your fingerprint to the other." msgstr "" "Na overenie odtla??ku prsta kontaktujte V????ho priate??a pomocou in??ho " "autentifikovan??ho kan??lu, ako napr??klad telef??n alebo e-mail podp??san?? " "pomocou GPG. Obaja by ste si mali navz??jom poveda?? odtla??ky prstov." #: ../gtk-dialog.c:1583 msgid "" "If everything matches up, you should indicate in the above dialog that you " "have verified the fingerprint." msgstr "" "Ak sa v??etko zhoduje, mali by ste v dial??gu vy????ie ozna??i??, ??e ste " "skontrolovali odtla??ok prsta." #: ../gtk-dialog.c:1585 msgid "" "If your buddy has more than one IM account, or uses more than one computer, " "he may have multiple fingerprints." msgstr "" "Ak V???? priate?? m?? viac ako jedno IM konto, alebo pou????va viac ako jeden " "po????ta??, m????e ma?? viacero odtla??kov prstov." #: ../gtk-dialog.c:1587 msgid "" "However, the only way an imposter could duplicate one of your buddy's " "fingerprints is by stealing information from her/his computer." msgstr "" "Jedin?? sp??sob, ako mohol podvodn??k duplikova?? jeden z odtla??kov prstov V????ho " "priate??a, je ukradn???? inform??cie z jej/jeho po????ta??a." #: ../gtk-dialog.c:1591 msgid "Click here for more information about fingerprints." msgstr "Kliknite sem pre viac inform??ci?? o odtla??koch prstov." #: ../gtk-dialog.c:1594 msgid "" "A fingerprint is a unique identifier that you should use to " "authenticate your buddy." msgstr "" "Odtla??ok prsta je jednozna??n?? identifik??tor, ktor?? by ste mali pou??i?? " "na autentifikovanie V????ho priate??a." #: ../gtk-dialog.c:1616 #, c-format msgid "Verify fingerprint for %s" msgstr "Skontrolujte odtla??ok prsta pre %s" #: ../gtk-dialog.c:1620 msgid "[none]" msgstr "[??iaden]" #: ../gtk-dialog.c:1628 #, c-format msgid "" "Fingerprint for you, %s (%s):\n" "%s\n" "\n" "Purported fingerprint for %s:\n" "%s\n" msgstr "" "Odtla??ok pre V??s, %s (%s):\n" "%s\n" "\n" "??dajn?? odtla??ok pre %s:\n" "%s\n" #: ../gtk-dialog.c:1633 ../gtk-ui.c:681 msgid "Verify fingerprint" msgstr "Skontrolujte odtla??ok" #: ../gtk-dialog.c:1660 #, c-format msgid "Authenticate %s" msgstr "Autentifikujte %s" #: ../gtk-dialog.c:1665 #, c-format msgid "Enter a secret known only to %s and yourself.\n" msgstr "Zadajte heslo zn??me iba %s a V??m.\n" #: ../gtk-dialog.c:1668 msgid "Authenticate buddy" msgstr "Autentifikujte priate??a" #: ../gtk-dialog.c:1700 msgid "An error occurred during authentication." msgstr "Nastala chyba pri autentifik??cii." #: ../gtk-dialog.c:1716 msgid "Authentication successful." msgstr "Autentifik??cia bola ??spe??n??" #: ../gtk-dialog.c:1719 msgid "Authentication failed." msgstr "Autentifik??cia zlyhala" #: ../gtk-dialog.c:1744 #, c-format msgid "Private conversation with %s started.%s" msgstr "S??kromn?? rozhovor s %s za??al.%s" #: ../gtk-dialog.c:1748 #, c-format msgid "Unverified conversation with %%s started.%%s" msgstr "Neoveren?? rozhovor s %%s za??al.%%s" #. This last case should never happen, since we know #. * we're in ENCRYPTED. #: ../gtk-dialog.c:1756 #, c-format msgid "Not private conversation with %s started.%s" msgstr "Nes??kromn?? rozhovor s %s za??al.%s" #: ../gtk-dialog.c:1762 ../gtk-dialog.c:1863 msgid " Warning: using old protocol version 1." msgstr " Varovanie: pou??vam star?? protokol verzie 1." #: ../gtk-dialog.c:1782 #, c-format msgid "Private conversation with %s lost." msgstr "S??kromn?? rozhovor s %s straten??." #: ../gtk-dialog.c:1817 #, c-format msgid "" "%s has ended his/her private conversation with you; you should do the same." msgstr "" "%s ukon??il(-a) svoj s??kromn?? rozhovor s Vami; mali by ste spravi?? to ist??." #: ../gtk-dialog.c:1842 #, c-format msgid "Successfully refreshed the private conversation with %s.%s" msgstr "S??kromn?? rozhovor s %s ??spe??ne obnoven??.%s" #: ../gtk-dialog.c:1847 #, c-format msgid "" "Successfully refreshed the unverified conversation with " "%%s.%%s" msgstr "" "Neoveren?? rozhovor s %%s ??spe??ne obnoven??.%%s" #. This last case should never happen, since we know #. * we're in ENCRYPTED. #: ../gtk-dialog.c:1856 #, c-format msgid "Successfully refreshed the not private conversation with %s.%s" msgstr "Nes??kromn?? rozhovor s %s ??spe??ne obnoven??.%s" #: ../gtk-dialog.c:1883 #, c-format msgid "Attempting to refresh the private conversation with %s..." msgstr "Pok????am sa obnovi?? s??kromn?? rozhovor s %s..." #: ../gtk-dialog.c:1885 #, c-format msgid "Attempting to start a private conversation with %s..." msgstr "Pok????am sa za??a?? s??kromn?? rozhovor s %s..." #: ../gtk-dialog.c:2045 msgid "OTR:" msgstr "OTR:" #: ../gtk-dialog.c:2054 msgid "OTR Messaging" msgstr "OTR odosielanie spr??v" #: ../gtk-dialog.c:2060 msgid "_End private conversation" msgstr "_Ukon??i?? s??kromn?? rozhovor" #. #. * Don't show the Verify fingerprint menu option any more. You can #. * still get to the dialog through Authenticate connection -> #. * Advanced... #. * #. menuverf = gtk_menu_item_new_with_mnemonic(_("_Verify fingerprint")); #. gtk_menu_shell_append(GTK_MENU_SHELL(menu), menuverf); #. gtk_widget_show(menuverf); #. #: ../gtk-dialog.c:2078 msgid "_Authenticate buddy" msgstr "_Autentifikova?? priate??a" #: ../gtk-ui.c:96 #, c-format msgid "Fingerprint: %.80s" msgstr "Odtla??ok prsta: %.80s" #: ../gtk-ui.c:100 #, c-format msgid "No key present" msgstr "Nie je dostupn?? ??iaden k??????" #: ../gtk-ui.c:105 #, c-format msgid "No account available" msgstr "Nie je dostupn?? ??iadne konto" #: ../gtk-ui.c:165 msgid "Unused" msgstr "Nepou??it??" #: ../gtk-ui.c:171 msgid "Yes" msgstr "??no" #: ../gtk-ui.c:171 msgid "No" msgstr "Nie" #: ../gtk-ui.c:396 msgid "Enable private messaging" msgstr "Zapn???? s??kromn?? odosielanie spr??v" #: ../gtk-ui.c:398 msgid "Automatically initiate private messaging" msgstr "Automaticky iniciova?? s??kromn?? odosielanie spr??v" #: ../gtk-ui.c:400 msgid "Require private messaging" msgstr "Vy??adova?? s??kromn?? odosielanie spr??v" #: ../gtk-ui.c:403 msgid "Don't log OTR conversations" msgstr "Nezaznamen??va?? OTR rozhovory" #: ../gtk-ui.c:531 msgid "My private keys" msgstr "Moje s??kromn?? k??????e" #: ../gtk-ui.c:540 msgid "Key for account:" msgstr "K?????? pre konto:" #: ../gtk-ui.c:565 msgid "Generate" msgstr "Generuj" #: ../gtk-ui.c:596 msgid "Default OTR Settings" msgstr "??tandardn?? nastavenia OTR" #: ../gtk-ui.c:625 msgid "Screenname" msgstr "Pou????vate??sk?? meno" #: ../gtk-ui.c:626 msgid "Status" msgstr "Stav" #: ../gtk-ui.c:627 msgid "Verified" msgstr "Overen??" #: ../gtk-ui.c:628 msgid "Fingerprint" msgstr "Odtla??ok prsta" #: ../gtk-ui.c:629 msgid "Account" msgstr "Konto" #: ../gtk-ui.c:665 msgid "Start private connection" msgstr "Za??a?? s??kromn?? rozhovor" #: ../gtk-ui.c:673 msgid "End private connection" msgstr "Ukon??i?? s??kromn?? rozhovor" #: ../gtk-ui.c:689 msgid "Forget fingerprint" msgstr "Zabudn???? odtla??ok prsta" #: ../gtk-ui.c:738 msgid "Config" msgstr "Nastavi??" #: ../gtk-ui.c:740 msgid "Known fingerprints" msgstr "Zn??me odtla??ky prstov" #: ../gtk-ui.c:838 ../otr-plugin.c:577 msgid "OTR Settings" msgstr "Nastavenia OTR" #. Set the title #: ../gtk-ui.c:856 #, c-format msgid "OTR Settings for %s" msgstr "OTR nastavenia pre %s" #. Make the cascaded checkboxes #: ../gtk-ui.c:873 msgid "Use default OTR settings for this buddy" msgstr "Pre tohto priate??a pou??i?? ??tandardn?? nastavenia" #: ../otr-plugin.c:113 #, c-format msgid "You are not currently connected to account %s (%s)." msgstr "Moment??lne nie ste pripojen??(-??) ku kontu %s (%s)." #: ../otr-plugin.c:117 msgid "Not connected" msgstr "Nepripojen??" #: ../otr-plugin.c:161 #, c-format msgid "Out of memory building filenames!\n" msgstr "Nedostatok pam??te pri vytv??ran?? mien s??borov" #: ../otr-plugin.c:167 #, c-format msgid "Could not write private key file\n" msgstr "Nemohol som zap??sa?? s??bor so s??kromn??m k??????om\n" #: ../otr-plugin.c:210 #, c-format msgid "Unknown account %s (%s)." msgstr "Nezn??me konto %s (%s)." #: ../otr-plugin.c:214 msgid "Unknown account" msgstr "Nezn??me konto" #: ../otr-plugin.c:953 msgid "Off-the-Record Messaging" msgstr "Utajen?? posielanie spr??v" #: ../otr-plugin.c:954 msgid "Provides private and secure conversations" msgstr "Umo????uje s??kromn?? a bezpe??n?? rozhovory" #: ../otr-plugin.c:955 msgid "" "Preserves the privacy of IM communications by providing encryption, " "authentication, deniability, and perfect forward secrecy." msgstr "" "Zachov??va s??kromie IM rozhovorov pou??it??m ??ifrovania, autentifik??cie, " "poprete??nosti a dokonal??ho dopredn??ho zabezpe??enia." #: ../ui.c:108 #, c-format msgid "Account %s (%s) could not be found" msgstr "Konto %s (%s) nemohlo by?? n??jden??" #: ../ui.c:112 msgid "Account not found" msgstr "Konto nen??jden??" From ian at cypherpunks.ca Tue Jul 31 17:54:48 2007 From: ian at cypherpunks.ca (Ian Goldberg) Date: Tue, 31 Jul 2007 17:54:48 -0400 Subject: [OTR-dev] Slovak translation by Milan Plzik In-Reply-To: References: Message-ID: <20070731215448.GE3751@yoink.cs.uwaterloo.ca> On Tue, Jul 31, 2007 at 01:58:21PM -0400, Paul Wouters wrote: > > Attached is the Slovak translation for pidgin-otr Thanks; checked in. > #: ../gtk-dialog.c:1025 > msgid "Enter secret here" > msgstr "" Should there not be a translation for this one? - Ian From paul at cypherpunks.ca Tue Jul 31 23:53:03 2007 From: paul at cypherpunks.ca (Paul Wouters) Date: Tue, 31 Jul 2007 23:53:03 -0400 (EDT) Subject: [OTR-dev] Slovak translation by Milan Plzik In-Reply-To: <20070731215448.GE3751@yoink.cs.uwaterloo.ca> References: <20070731215448.GE3751@yoink.cs.uwaterloo.ca> Message-ID: On Tue, 31 Jul 2007, Ian Goldberg wrote: > On Tue, Jul 31, 2007 at 01:58:21PM -0400, Paul Wouters wrote: > > > > Attached is the Slovak translation for pidgin-otr > > Thanks; checked in. > > > #: ../gtk-dialog.c:1025 > > msgid "Enter secret here" > > msgstr "" > > Should there not be a translation for this one? Darn. I even double checked it, and still missed one :( Milan: can you give us translation for the above sentence? Paul