On Mon, Oct 01, 2012 at 05:35:06PM +, Jacob Appelbaum wrote:
Thibaut VARENE:
On Mon, Oct 1, 2012 at 7:24 PM, Paul Wouters p...@cypherpunks.ca wrote:
On Mon, 1 Oct 2012, Thibaut VARENE wrote:
I'm about to upload pidgin-otr 4.0.0 to debian unstable, and it
debian already ships
Hi,
I'm about to upload pidgin-otr 4.0.0 to debian unstable, and it
appears the calls exit() issue has moved to pidgin-otr. I don't know
enough of pidgin plugin system to know whether this is a false
positive or not, but I thought I might blow the whistle anyway...
HTH
Thibaut
X: pidgin-otr:
On Mon, 1 Oct 2012, Thibaut VARENE wrote:
I'm about to upload pidgin-otr 4.0.0 to debian unstable, and it
debian already ships libotr-4? Did they add a libotr3 package? Did
other OTR software get ported to 4.x already? Or will it just break?
Interested, because I hadn't yet uploaded libotr3,
On Mon, Oct 1, 2012 at 7:24 PM, Paul Wouters p...@cypherpunks.ca wrote:
On Mon, 1 Oct 2012, Thibaut VARENE wrote:
I'm about to upload pidgin-otr 4.0.0 to debian unstable, and it
debian already ships libotr-4? Did they add a libotr3 package? Did
libotr5, per soname.
other OTR software get
Thibaut VARENE:
On Mon, Oct 1, 2012 at 7:24 PM, Paul Wouters p...@cypherpunks.ca wrote:
On Mon, 1 Oct 2012, Thibaut VARENE wrote:
I'm about to upload pidgin-otr 4.0.0 to debian unstable, and it
debian already ships libotr-4? Did they add a libotr3 package? Did
libotr5, per soname.
I looked at the -S output. Basically, I built each way, and then did:
rm auth.lo auth.o
gmake -n | sed -e 's/ -c / -S /' | sh
which put the source in auth.o (and then the link failed).
Compilation with -O1/-O2 and with/without the gcc hardening are at:
Ian Goldberg i...@cypherpunks.ca writes:
On Mon, Sep 03, 2012 at 06:40:08PM -0400, Greg Troxel wrote:
Ian Goldberg i...@cypherpunks.ca writes:
OK, then I guess the thing to do is just to turn off hardening for that
build environment? [I believe the hardening is only actually enabled
On Mon, Sep 03, 2012 at 07:40:54PM -0400, Greg Troxel wrote:
I'll look into this more; probably when libotr is really released and I
update - then I can point people to it easily.
OK. My plan is to release it for real tomorrow morning.
It would be really nice to have a test case run with
On Sun, Sep 02, 2012 at 10:27:04AM -0400, Greg Troxel wrote:
Ian Goldberg i...@cypherpunks.ca writes:
On Sun, Sep 02, 2012 at 09:38:21AM -0400, Greg Troxel wrote:
Ian Goldberg i...@cypherpunks.ca writes:
Can you confirm that the 1.5.0 in pkgsrc already has the above patch
One of my paranoid friends showed up, and the new library did not work.
I did 'start private' and got a malformed message. I then changed
settings to 'default' (vs 'always') and then to 'never', but still was
not able to interoperate, even with OTR disabled (the other person
probably is setup
On Sat, Sep 1, 2012 at 6:22 PM, Ian Goldberg i...@cypherpunks.ca wrote:
On Sat, Sep 01, 2012 at 11:55:33AM -0400, Greg Troxel wrote:
Ian Goldberg i...@cypherpunks.ca writes:
This looks a lot like one of you is logged in more than once. Could
this possibly be the case? (If the other
On Fri, Aug 31, 2012 at 2:09 AM, Ian Goldberg i...@cypherpunks.ca wrote:
On Thu, Aug 30, 2012 at 06:33:48PM -0400, Paul Wouters wrote:
On Thu, 30 Aug 2012, Ian Goldberg wrote:
So 7 clients use it, so I am not going to assume all of these can fix
their code within a few days.
Indeed not.
On Fri, Aug 31, 2012 at 2:14 PM, Ian Goldberg i...@cypherpunks.ca wrote:
On Fri, Aug 31, 2012 at 12:43:58PM +0200, Thibaut VARENE wrote:
Yes, I will send patches to the maintainers of these to change their
Require: libotr to Require: libotr 4. The libotr3 package will supply
libotr 4,
On Fri, Aug 31, 2012 at 03:38:59PM +0200, Thibaut VARENE wrote:
I plan to build the test releases of 4.0.0 today, including the patch to
fix the exit() issue, and an extremely minor remove whitespace at the
ends of a handful of lines source cleanup patch.
They're built.
[Rearranging...]
On Thu, Aug 30, 2012 at 01:55:16PM -0400, Greg Troxel wrote:
(Sorry if I sound cranky; I'm not really trying to complain about how
things are, just to point out that the questions I'm asking are the key
questions one needs to have answered to decide what to do, and that they
Ian Goldberg i...@cypherpunks.ca writes:
Oh, they're good questions. I guess my lack of experience with pkgsrc
(and *bsd in general) is showing. :-p
Perhaps, but I don't think my questions are bsd-specific - it's more
about any system that has to manage lots of software maintained by third
On Wed, 29 Aug 2012, Ian Goldberg wrote:
Indeed, that's what Thibaut noticed, and I sent a patch to correct
already.
Oh, did not realise it was the same issue...
I'm looking at providing libotr3 and libotr packages, as I don't think
all the apps will port their code to the new library in
On Thu, 30 Aug 2012, Ian Goldberg wrote:
Depending on how it's packaged, the runtime packages may be disjoint
(the shared lib has a different name in each version), but the -dev
package (with the header files) has the same filenames, so you'd be
limited to installing one -dev package at a time.
On Thu, Aug 30, 2012 at 05:02:57PM -0400, Paul Wouters wrote:
In Fedora/EPEL libort is used by:
[paul@thinkpad ~]$ repoquery -qa --whatrequires libotr
bitlbee-otr-0:3.0.4-3.fc17.x86_64
bitlbee-otr-0:3.0.5-1.fc17.x86_64
climm-0:0.7.1-4.fc17.x86_64
irssi-otr-0:0.3-5.fc17.x86_64
On Thu, 30 Aug 2012, Ian Goldberg wrote:
So 7 clients use it, so I am not going to assume all of these can fix
their code within a few days.
Indeed not. They can continue to depend on the old version of libotr.
(Your libotr3 package, if I understand it? But does that mean you have
to change
On Thu, Aug 30, 2012 at 06:33:48PM -0400, Paul Wouters wrote:
On Thu, 30 Aug 2012, Ian Goldberg wrote:
So 7 clients use it, so I am not going to assume all of these can fix
their code within a few days.
Indeed not. They can continue to depend on the old version of libotr.
(Your libotr3
On Wed, Aug 29, 2012 at 03:40:19PM -0400, Paul Wouters wrote:
On Mon, 27 Aug 2012, Ian Goldberg wrote:
OK, 4.0.0-rc3 is ready.
**Please give it a try, and give feedback!**
So far, seems good.
I noticed a warning, which is not new to libotr-4, but might be good
to look at:
On Tue, Aug 28, 2012 at 2:24 AM, Ian Goldberg i...@cypherpunks.ca wrote:
Indeed, otrl_init(ver_major, ver_minor, ver_sub) calls exit(1) if the
passed version numbers are incompatible with the library's actual
version.
Seeing as how it's intended to be called from this macro:
#define
Thibaut VARENE vare...@debian.org writes:
On Tue, Aug 28, 2012 at 2:16 AM, Greg Troxel g...@ir.bbn.com wrote:
In pkgsrc, libotr is simply libotr.
Two questions:
will just libotr.pc be installed, but with the new versions? If so, I
don't see any reason to call this libotr5, but
Thibaut VARENE vare...@debian.org writes:
On Tue, Aug 28, 2012 at 2:16 AM, Greg Troxel g...@ir.bbn.com wrote:
In pkgsrc, libotr is simply libotr.
Two questions:
will just libotr.pc be installed, but with the new versions? If so, I
don't see any reason to call this libotr5, but
25 matches
Mail list logo
