Re: RFS: jabbin

2007-01-28 Thread Damyan Ivanov
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

- -=| Andrew Donnellan, 27.01.2007 23:03 |=-
 SSL is required for use with Google Talk, so unfortunately I don't
 think it can be removed without making it mostly useless. However I
 think that it uses QCA for that.

SSL is implemented also by GNU TLS...
You may point upstream to this implementation to avoid SSL licensing
problems.

Just an idea.


dam
- --
Damyan Ivanov   Modular Software Systems
[EMAIL PROTECTED]
phone +359(2)928-2611, 929-3993  fax +359(2)920-0994
mobile +359(88)856-6067  [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFvHynHqjlqpcl9jsRAskEAJ9C6retdwoBv8mLfjL0VWjCsIZ9TACeICSD
QE55LeVRKA2+l89bhKL/7ns=
=S7M3
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: RFS: jabbin

2007-01-28 Thread Andrew Donnellan

On 1/28/07, Damyan Ivanov [EMAIL PROTECTED] wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

- -=| Andrew Donnellan, 27.01.2007 23:03 |=-
 SSL is required for use with Google Talk, so unfortunately I don't
 think it can be removed without making it mostly useless. However I
 think that it uses QCA for that.

SSL is implemented also by GNU TLS...
You may point upstream to this implementation to avoid SSL licensing
problems.


Yes, I know that, I just don't have enough experience with using
GNUTLS or OpenSSL to port it myself.

Psi is in the archive, and it uses qca-tls.
--
Andrew Donnellan
ajdlinuxATgmailDOTcom (primary)ajdlinuxATexemailDOTcomDOTau (secure)
http://andrewdonnellan.com http://ajdlinux.wordpress.com
[EMAIL PROTECTED] hkp://subkeys.pgp.net 0x5D4C0C58
   http://linux.org.auhttp://debian.org
   Get free rewards - http://ezyrewards.com/?id=23484


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: RFS: jabbin

2007-01-27 Thread Bernhard R. Link
* Andrew Donnellan [EMAIL PROTECTED] [070126 12:07]:
 * As it contains so much stuff, I'm a bit lost what code is actually
   used. But the resulting binaries might be indistributeable, as the
   main program is GPL with exceptions for qt and stuff only accessed
   via qt or qca, while it also seems to be used at other parts which
   look like they might also be used more directly. (libjingle, xmlsec)
   If nothing bad happens, some note in the source package that nothing
   bad happens and why would be nice.
 
 Sorry, I don't understand what you're saying here.

If a program contains code that is only available under GPL, GPL
requests for all the program being available under GPL without
additional restrictions. OpenSSL has multiple such additional
restrictions (like 'Products derived from this software may not be
called OpenSSL[...]' or 'All advertising materials mentioning
features or use of this software must display the following
acknowledgment: [...]'), so a program with GPL-only code linking[1]
with OpenSSL is not distributeable at all.

So a GPL program linking with OpenSSL is not possible, but a
GPL and additional permissions to allow that program can link
with OpenSSL. But that of course needs two things, namely
1) all GPL code included having that additional permission
2) the conditions for this permission have to be matched.

1) should be no problem if your debian/copyright is correct and list
all licenses.

2) the license listed there for the main program gives the following
additional (over GPL) permissions:

|   As a special exception, the copyright holder(s) give permission to link
|   this program with the Qt Library (commercial or non-commercial edition),
|   and distribute the resulting executable, without including the source
|   code for the Qt library in the source distribution.

This clearly gives no permission for linking with OpenSSL, so lets look
at the next paragraph:

|   As a special exception, the copyright holder(s) give permission to link
|   this program with any other library, and distribute the resulting
|   executable, without including the source code for the library in the
|   source distribution, provided that the library interfaces with this
|   program only via the following plugin interfaces:
|
| 1. The Qt Plugin APIs, only as authored by Trolltech
| 2. The QCA Plugin API, only as authored by Justin Karneges

That seems to be the clause intended to allow linking to OpenSSL,
but only when it is only linked via a Qt or QCA plugin.

But e.g. /3party/libjingle/talk/base/ssladapter.cc does
#include openssl/[...], which indicated that it might be intended
to be linked with openSSL and might be done so when building a package.
In this case it looks like that file is only used in the windows build,
so it most likely no problem. But having for each of those files to think
about why it causes no problem, makes it quite some work for a sponsor.
If your source package included a short explaination for each such file
why it is no problem, you would help a sponsor quite a lot to sponsor it.
(and I guess FTP-masters, too, when they have to look at it)

While all files including openssl headers seem to be not used under Linux
(at least when looking as shallow at it as I did), what puzzles me more is
unix:LIBS += -lssl in voip.pri. Perhaps the easiest way is to just remove
it. If nothing breaks then it can just be removed, if something breaks one
has to look what part is using ssl.

If something is mixing GPL and OpenSSL code there mainly three possibilities:

1) rewriting to not use OpenSSL but e.g. gnutls
2) rewriting to use it in a way allowed by your permissions (i.e. over qca)
3) get additional permissions from all copyright holders in code with not
enough permissions.

Hochachtungsvoll,
Bernhard R. Link

[1] What the actual status of this affairs is, is a bit disbuted,
as the program does not contain most of the code of the library,
but the library was used when creating it, header[2] files have been
used when compiling and so on. And since it is disputed and no
judge has yet decided, and noone was confident enough in this being
no problem to offer take over all possible costs of all Debian users
if a judge decides the other way, the only safe way is to assume
this is undistributeable, whether or not one believes that to be the
way copyright should work.

[2] which may include algorithmic or inline stuff, but even without
exceptions for interface stuff might not be enough to allow this.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: RFS: jabbin

2007-01-27 Thread Andrew Donnellan

On 1/27/07, Bernhard R. Link [EMAIL PROTECTED] wrote:

If a program contains code that is only available under GPL, GPL
requests for all the program being available under GPL without
additional restrictions. OpenSSL has multiple such additional
restrictions (like 'Products derived from this software may not be
called OpenSSL[...]' or 'All advertising materials mentioning
features or use of this software must display the following
acknowledgment: [...]'), so a program with GPL-only code linking[1]
with OpenSSL is not distributeable at all.

So a GPL program linking with OpenSSL is not possible, but a
GPL and additional permissions to allow that program can link
with OpenSSL. But that of course needs two things, namely
1) all GPL code included having that additional permission
2) the conditions for this permission have to be matched.


Understood. I wasn't aware that OpenSSL was used.



1) should be no problem if your debian/copyright is correct and list
all licenses.

2) the license listed there for the main program gives the following
additional (over GPL) permissions:

|   As a special exception, the copyright holder(s) give permission to link
|   this program with the Qt Library (commercial or non-commercial edition),
|   and distribute the resulting executable, without including the source
|   code for the Qt library in the source distribution.

This clearly gives no permission for linking with OpenSSL, so lets look
at the next paragraph:

|   As a special exception, the copyright holder(s) give permission to link
|   this program with any other library, and distribute the resulting
|   executable, without including the source code for the library in the
|   source distribution, provided that the library interfaces with this
|   program only via the following plugin interfaces:
|
| 1. The Qt Plugin APIs, only as authored by Trolltech
| 2. The QCA Plugin API, only as authored by Justin Karneges

That seems to be the clause intended to allow linking to OpenSSL,
but only when it is only linked via a Qt or QCA plugin.


I'll have to look into the actual linking process and where it is
linked, as well as how libjingle is used.



But e.g. /3party/libjingle/talk/base/ssladapter.cc does
#include openssl/[...], which indicated that it might be intended
to be linked with openSSL and might be done so when building a package.
In this case it looks like that file is only used in the windows build,
so it most likely no problem. But having for each of those files to think
about why it causes no problem, makes it quite some work for a sponsor.
If your source package included a short explaination for each such file
why it is no problem, you would help a sponsor quite a lot to sponsor it.
(and I guess FTP-masters, too, when they have to look at it)


I'll document all licenses.



While all files including openssl headers seem to be not used under Linux
(at least when looking as shallow at it as I did), what puzzles me more is
unix:LIBS += -lssl in voip.pri. Perhaps the easiest way is to just remove
it. If nothing breaks then it can just be removed, if something breaks one
has to look what part is using ssl.


SSL is required for use with Google Talk, so unfortunately I don't
think it can be removed without making it mostly useless. However I
think that it uses QCA for that.



If something is mixing GPL and OpenSSL code there mainly three
possibilities:

1) rewriting to not use OpenSSL but e.g. gnutls
2) rewriting to use it in a way allowed by your permissions (i.e. over qca)


I believe the critical SSL stuff is done using QCA. The SSL files in
libjingle may be extraneous. I'll check what you said about the
voip.pri file linking directly to libssl.


3) get additional permissions from all copyright holders in code with not
enough permissions.


May be quite difficult considering that means the whole of Psi upstream...

Thanks,
--
Andrew Donnellan
ajdlinuxATgmailDOTcom (primary)ajdlinuxATexemailDOTcomDOTau (secure)
http://andrewdonnellan.com http://ajdlinux.wordpress.com
[EMAIL PROTECTED] hkp://subkeys.pgp.net 0x5D4C0C58
   http://linux.org.auhttp://debian.org
   Get free rewards - http://ezyrewards.com/?id=23484


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: RFS: jabbin

2007-01-26 Thread Andrew Donnellan

Ping. Anyone want to review or sponsor?

On 1/26/07, Andrew Donnellan [EMAIL PROTECTED] wrote:

Dear mentors,

I am looking for a sponsor for my package jabbin.

* Package name: jabbin
  Version : 2.1~20070126.svn.r115-1
  Upstream Author : Stefano Grini [EMAIL PROTECTED]
* URL : http://jabbin.com
* License : GPL
  Section : net

This version should fix the problems with non-x86 compilation.
Unfortunately debian/changelog is a bit disorganised and things are in
the wrong place, that will be fixed later.

It builds these binary packages:
jabbin - Jabber client supporting Jingle and VoIP

The package is lintian clean.

The package can be found on mentors.debian.net:
- URL: http://mentors.debian.net/debian/pool/main/j/jabbin
- Source repository: deb-src http://mentors.debian.net/debian unstable
main contrib non-free
- dget
http://mentors.debian.net/debian/pool/main/j/jabbin/jabbin_2.1~20070126.svn.r115-1.dsc

I would be glad if someone uploaded this package for me.

Kind regards
 Andrew Donnellan

--
Andrew Donnellan
ajdlinuxATgmailDOTcom (primary)ajdlinuxATexemailDOTcomDOTau (secure)
http://andrewdonnellan.com http://ajdlinux.wordpress.com
[EMAIL PROTECTED] hkp://subkeys.pgp.net 0x5D4C0C58
http://linux.org.auhttp://debian.org
Get free rewards - http://ezyrewards.com/?id=23484




--
Andrew Donnellan
ajdlinuxATgmailDOTcom (primary)ajdlinuxATexemailDOTcomDOTau (secure)
http://andrewdonnellan.com http://ajdlinux.wordpress.com
[EMAIL PROTECTED] hkp://subkeys.pgp.net 0x5D4C0C58
   http://linux.org.auhttp://debian.org
   Get free rewards - http://ezyrewards.com/?id=23484


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: RFS: jabbin

2007-01-26 Thread Bernhard R. Link
* Andrew Donnellan [EMAIL PROTECTED] [070125 23:51]:
 I am looking for a sponsor for my package jabbin.
 
 * Package name: jabbin
  Version : 2.1~20070126.svn.r115-1
  Upstream Author : Stefano Grini [EMAIL PROTECTED]
 * URL : http://jabbin.com
 * License : GPL
  Section : net
 
 This version should fix the problems with non-x86 compilation.
 Unfortunately debian/changelog is a bit disorganised and things are in
 the wrong place, that will be fixed later.
 
 It builds these binary packages:
 jabbin - Jabber client supporting Jingle and VoIP
 
 The package is lintian clean.
 
 The package can be found on mentors.debian.net:
 - URL: http://mentors.debian.net/debian/pool/main/j/jabbin
 - Source repository: deb-src http://mentors.debian.net/debian unstable
 main contrib non-free
 - dget 
 http://mentors.debian.net/debian/pool/main/j/jabbin/jabbin_2.1~20070126.svn.r115-1.dsc
 
 I would be glad if someone uploaded this package for me.

I've no audio on my unstable boxes, so I'm unable to test (and thus to
sponsor) the package, but some things I noticed:

* As is is a snapshot, telling which command was used to generate it would
  be nice, so the non-svn savy of us can more easily verify that it is
  genuine. (If it was downloaded from somewhere, please give the link to
  that, as the link in the debian/copyright is no archive)

* if you generate the .tar yourself anyway, you could let out the
  3party stuff. Otherwise it would be nice to note somewhere how
  you have made sure that the Debian versions have been used instead
  of statically using the shipped stuff. Or at least how the stuff
  it includes is different from the Debian versions that using it
  instead of the installed versions could possibly excused.

* As it contains so much stuff, I'm a bit lost what code is actually
  used. But the resulting binaries might be indistributeable, as the
  main program is GPL with exceptions for qt and stuff only accessed
  via qt or qca, while it also seems to be used at other parts which
  look like they might also be used more directly. (libjingle, xmlsec)
  If nothing bad happens, some note in the source package that nothing
  bad happens and why would be nice.

Hochachtungsvoll,
Bernhard R. Link
-- 
Never contain programs so few bugs, as when no debugging tools are available!
Niklaus Wirth


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: RFS: jabbin

2007-01-26 Thread Andrew Donnellan

On 1/26/07, Bernhard R. Link [EMAIL PROTECTED] wrote:


I've no audio on my unstable boxes, so I'm unable to test (and thus to
sponsor) the package, but some things I noticed:

* As is is a snapshot, telling which command was used to generate it would
  be nice, so the non-svn savy of us can more easily verify that it is
  genuine. (If it was downloaded from somewhere, please give the link to
  that, as the link in the debian/copyright is no archive)


It's using a script stored in upstream's SVN repo
(https://jabbin.svn.sourceforge.net/svnroot/jabbin/trunk/) called
admin/debian.sh. If you want to see how the building is done then just
look there. It essentially strips out the .svn directories and the
administrivia stuff.



* if you generate the .tar yourself anyway, you could let out the
  3party stuff. Otherwise it would be nice to note somewhere how
  you have made sure that the Debian versions have been used instead
  of statically using the shipped stuff. Or at least how the stuff
  it includes is different from the Debian versions that using it
  instead of the installed versions could possibly excused.


I'm going to have to look into this: upstream says modifications were
made at least to libjingle, in my first RFS in August someone tried
and said it didn't work. I'll have to investigate.



* As it contains so much stuff, I'm a bit lost what code is actually
  used. But the resulting binaries might be indistributeable, as the
  main program is GPL with exceptions for qt and stuff only accessed
  via qt or qca, while it also seems to be used at other parts which
  look like they might also be used more directly. (libjingle, xmlsec)
  If nothing bad happens, some note in the source package that nothing
  bad happens and why would be nice.


Sorry, I don't understand what you're saying here.

--
Andrew Donnellan
ajdlinuxATgmailDOTcom (primary)ajdlinuxATexemailDOTcomDOTau (secure)
http://andrewdonnellan.com http://ajdlinux.wordpress.com
[EMAIL PROTECTED] hkp://subkeys.pgp.net 0x5D4C0C58
   http://linux.org.auhttp://debian.org
   Get free rewards - http://ezyrewards.com/?id=23484


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: RFS: jabbin

2007-01-23 Thread Yavor Doganov
В Tue, 23 Jan 2007 18:29:33 +1100, Andrew Donnellan написа:

 Could someone who has a ppc system try this version?

It still fails to build:

../voip/stun.cpp:681:7: error: #error Need some way to seed the random number 
generator
../voip/stun.cpp:722: warning: unused parameter 'input'
../voip/stun.cpp:722: warning: unused parameter 'length'
../voip/stun.cpp:722: warning: unused parameter 'key'
../voip/stun.cpp:722: warning: unused parameter 'sizeKey'
make[2]: *** [.obj/stun.o] Error 1

I can send you off-list the full sbuild log, if you want.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: RFS: jabbin

2007-01-23 Thread Andrew Donnellan

On 1/23/07, Yavor Doganov [EMAIL PROTECTED] wrote:

В Tue, 23 Jan 2007 18:29:33 +1100, Andrew Donnellan написа:

 Could someone who has a ppc system try this version?

It still fails to build:

../voip/stun.cpp:681:7: error: #error Need some way to seed the random
number generator
../voip/stun.cpp:722: warning: unused parameter 'input'
../voip/stun.cpp:722: warning: unused parameter 'length'
../voip/stun.cpp:722: warning: unused parameter 'key'
../voip/stun.cpp:722: warning: unused parameter 'sizeKey'
make[2]: *** [.obj/stun.o] Error 1


I don't need the full log, I just need to know whether it builds or not.

I'll have a look at the patches that were suggested earlier - I may
apply them upstream as I have access to their repo.

I'm also going to prepare a new version very soon.
--
Andrew Donnellan
ajdlinuxATgmailDOTcom (primary)ajdlinuxATexemailDOTcomDOTau (secure)
http://andrewdonnellan.com http://ajdlinux.wordpress.com
[EMAIL PROTECTED] hkp://subkeys.pgp.net 0x5D4C0C58
   http://linux.org.auhttp://debian.org
   Get free rewards - http://ezyrewards.com/?id=23484


Re: RFS: jabbin

2007-01-23 Thread Thijs Kinkhorst
On Tue, 2007-01-23 at 19:46 +1100, Andrew Donnellan wrote:
 I'll have a look at the patches that were suggested earlier - I may
 apply them upstream as I have access to their repo.
 
 I'm also going to prepare a new version very soon.

Just to let you know - your package looks very good otherwise.


Thijs


signature.asc
Description: This is a digitally signed message part


Re: RFS: jabbin

2007-01-23 Thread Andrew Donnellan

On 1/23/07, Thijs Kinkhorst [EMAIL PROTECTED] wrote:

Just to let you know - your package looks very good otherwise.


Thanks :)

I'm going to apply the patch provided by Francesco Pedrini at [0], as
a Debian specific patch until it can be sorted out upstream.

[0] http://lists.debian.org/debian-mentors/2006/08/msg00302.html

--
Andrew Donnellan
ajdlinuxATgmailDOTcom (primary)ajdlinuxATexemailDOTcomDOTau (secure)
http://andrewdonnellan.com http://ajdlinux.wordpress.com
[EMAIL PROTECTED] hkp://subkeys.pgp.net 0x5D4C0C58
   http://linux.org.auhttp://debian.org
   Get free rewards - http://ezyrewards.com/?id=23484


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: RFS: jabbin

2007-01-23 Thread Damyan Ivanov
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

- -=| Andrew Donnellan, 23.01.2007 10:46 |=-
 I'll have a look at the patches that were suggested earlier - I may
 apply them upstream as I have access to their repo.
 
 I'm also going to prepare a new version very soon.

While there, could you consider removing jabbin.1 in debian/rules' clean
target? It seems confusing to me to ship both the .xml source and the
resulting .1 in the .diff, considering that the .1 is automatically built.


dam
- --
Damyan Ivanov   Modular Software Systems
[EMAIL PROTECTED]
phone +359(2)928-2611, 929-3993  fax +359(2)920-0994
mobile +359(88)856-6067 [EMAIL PROTECTED]/Gaim
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFtdDWHqjlqpcl9jsRAiicAKCmEo07UN+9nHXAp7zjhlAHYcHtnwCghbl/
99JrH1Bk2eRDVwAgH9L69bM=
=Cw6Z
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: RFS: jabbin

2007-01-23 Thread Andrew Donnellan

On 1/23/07, Damyan Ivanov [EMAIL PROTECTED] wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

- -=| Andrew Donnellan, 23.01.2007 10:46 |=-
 I'll have a look at the patches that were suggested earlier - I may
 apply them upstream as I have access to their repo.

 I'm also going to prepare a new version very soon.

While there, could you consider removing jabbin.1 in debian/rules' clean
target? It seems confusing to me to ship both the .xml source and the
resulting .1 in the .diff, considering that the .1 is automatically built.


Ugh. Fixing in next version.

--
Andrew Donnellan
ajdlinuxATgmailDOTcom (primary)ajdlinuxATexemailDOTcomDOTau (secure)
http://andrewdonnellan.com http://ajdlinux.wordpress.com
[EMAIL PROTECTED] hkp://subkeys.pgp.net 0x5D4C0C58
   http://linux.org.auhttp://debian.org
   Get free rewards - http://ezyrewards.com/?id=23484


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: RFS: jabbin

2007-01-22 Thread Andrew Donnellan

On 1/23/07, Andrew Donnellan [EMAIL PROTECTED] wrote:

Dear mentors,

I am looking for a sponsor for my package jabbin.

* Package name: jabbin
  Version : 2.1~20070123.svn.r91-1
  Upstream Author : Stefano Grini et al. [EMAIL PROTECTED]
* URL : http://jabbin.com
* License : GPL
  Section : net


When I first sent the original RFS last year someone pointed out a bug
that causes it to FTBFS on powerpc and possibly others, to do with
seeding the random number generator. Could someone who has a ppc
system try this version?
--
Andrew Donnellan
ajdlinuxATgmailDOTcom (primary)ajdlinuxATexemailDOTcomDOTau (secure)
http://andrewdonnellan.com http://ajdlinux.wordpress.com
[EMAIL PROTECTED] hkp://subkeys.pgp.net 0x5D4C0C58
   http://linux.org.auhttp://debian.org
   Get free rewards - http://ezyrewards.com/?id=23484


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: RFS: jabbin

2006-10-04 Thread Andrew Donnellan

Ping. Any more comments?

On 9/4/06, Andrew Donnellan [EMAIL PROTECTED] wrote:

On 9/4/06, Tzafrir Cohen [EMAIL PROTECTED] wrote:
 On Tue, Aug 15, 2006 at 01:43:32AM +, Andrew Donnellan wrote:
  Is anyone interested in sponsoring this package? I'm happy to fix any
  problems and I'm in close contact with upstream.
 
  (VoIP team cc'd, maybe this would interest you guys)

 I'm playing with it right now. It seems to basically work with my hybris
 Sarge build (I reduced the required debhelper version to 4, reduced
 compat to 4, and removed the build dep on libxss-dev).

 However Jabbin is basically a fork of PSI. How does it compare with the
 main app? Is there really a point in both?

I don't know :)

The dev is working on a new interface and is also planning video
support over jingle, also SIP support planned.

andrew



 The package's description should refer to PSI: at the moment it uses
 PSI's config (at least for me).

 There is a Jingle branch for Psi: http://psi-im.org/wiki/Jingle_branch
 http://psi-im.org/wiki/Jingle_branch#Debian_Testing.2FUnstable

 --
 Tzafrir Cohen sip:[EMAIL PROTECTED]
 icq#16849755  iax:[EMAIL PROTECTED]
 +972-50-7952406  jabber:[EMAIL PROTECTED]
 [EMAIL PROTECTED] http://www.xorcom.com



--
Andrew Donnellan
http://andrewdonnellan.com
http://ajdlinux.blogspot.com
Jabber - [EMAIL PROTECTED]
GPG - hkp://subkeys.pgp.net 0x5D4C0C58
---
Member of Linux Australia - http://linux.org.au
Debian user - http://debian.org
Get free rewards - http://ezyrewards.com/?id=23484
OpenNIC user - http://www.opennic.unrated.net




--
Andrew Donnellan
-- Email - ajdlinuxATgmailDOTcom (primary)
-- Email - ajdlinuxATexemailDOTcomDOTau (secure)
http://andrewdonnellan.com
http://ajdlinux.wordpress.com
Jabber - [EMAIL PROTECTED]
GPG - hkp://subkeys.pgp.net 0x5D4C0C58
---
Member of Linux Australia - http://linux.org.au
Debian user - http://debian.org
Get free rewards - http://ezyrewards.com/?id=23484
OpenNIC user - http://www.opennic.unrated.net


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: RFS: jabbin

2006-09-03 Thread Andrew Donnellan

On 9/4/06, Tzafrir Cohen [EMAIL PROTECTED] wrote:

On Tue, Aug 15, 2006 at 01:43:32AM +, Andrew Donnellan wrote:
 Is anyone interested in sponsoring this package? I'm happy to fix any
 problems and I'm in close contact with upstream.

 (VoIP team cc'd, maybe this would interest you guys)

I'm playing with it right now. It seems to basically work with my hybris
Sarge build (I reduced the required debhelper version to 4, reduced
compat to 4, and removed the build dep on libxss-dev).

However Jabbin is basically a fork of PSI. How does it compare with the
main app? Is there really a point in both?


I don't know :)

The dev is working on a new interface and is also planning video
support over jingle, also SIP support planned.

andrew




The package's description should refer to PSI: at the moment it uses
PSI's config (at least for me).

There is a Jingle branch for Psi: http://psi-im.org/wiki/Jingle_branch
http://psi-im.org/wiki/Jingle_branch#Debian_Testing.2FUnstable

--
Tzafrir Cohen sip:[EMAIL PROTECTED]
icq#16849755  iax:[EMAIL PROTECTED]
+972-50-7952406  jabber:[EMAIL PROTECTED]
[EMAIL PROTECTED] http://www.xorcom.com




--
Andrew Donnellan
http://andrewdonnellan.com
http://ajdlinux.blogspot.com
Jabber - [EMAIL PROTECTED]
GPG - hkp://subkeys.pgp.net 0x5D4C0C58
---
Member of Linux Australia - http://linux.org.au
Debian user - http://debian.org
Get free rewards - http://ezyrewards.com/?id=23484
OpenNIC user - http://www.opennic.unrated.net


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: RFS: jabbin

2006-08-29 Thread Andrew Donnellan

On 8/25/06, Hubert Chan [EMAIL PROTECTED] wrote:

| +#elif defined( __MACH__ )|| defined( __GNUC__ )
|int fd=open(/dev/random,O_RDONLY);
|read(fd,tick,sizeof(tick));
|closesocket(fd);

Err, I don't think that __GNUC__ actually guarantees the presence of
/dev/random.  So this patch does not seem to be correct.

(Although /dev/random, if you have it, is probably a better source of
randomness than rdtsc, or gethrtime.)


So what would be the alternative? Would we have to use a makefile hack
(e.g. test for the existence of /dev/random and set a compile flag) or
something to figure out what random seed we should use?

Also would it be OK to include this as a Debian patch, esp. because at
the moment Debian doesn't have any non-glibc ports?



| -#else
| -# error Need some way to seed the random number generator
| -#endif
| +#endif

If it really does need a proper random seed, then you should not be
getting rid of the compilation error.  It may compile correctly, but it
will not work as intended.


I do wonder what it needs the proper random seed for though.

If anyone can come up with a solution I'll be grateful.

--
Andrew Donnellan
http://andrewdonnellan.com
http://ajdlinux.blogspot.com
Jabber - [EMAIL PROTECTED]
GPG - hkp://subkeys.pgp.net 0x5D4C0C58
---
Member of Linux Australia - http://linux.org.au
Debian user - http://debian.org
Get free rewards - http://ezyrewards.com/?id=23484
OpenNIC user - http://www.opennic.unrated.net


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: RFS: jabbin

2006-08-29 Thread George Danchev
On Tuesday 29 August 2006 12:33, Andrew Donnellan wrote:
--cut--
  If it really does need a proper random seed, then you should not be
  getting rid of the compilation error.  It may compile correctly, but it
  will not work as intended.

 I do wonder what it needs the proper random seed for though.

 If anyone can come up with a solution I'll be grateful.

Probably investigating gnupg sources could give some clues wrt random seed 
handling.

-- 
pub 4096R/0E4BD0AB 2003-03-18 people.fccf.net/danchev/key pgp.mit.edu
fingerprint 1AE7 7C66 0A26 5BFF DF22 5D55 1C57 0C89 0E4B D0AB 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: RFS: jabbin

2006-08-29 Thread Andrew Donnellan

On 8/29/06, George Danchev [EMAIL PROTECTED] wrote:

On Tuesday 29 August 2006 12:33, Andrew Donnellan wrote:
--cut--
  If it really does need a proper random seed, then you should not be
  getting rid of the compilation error.  It may compile correctly, but it
  will not work as intended.

 I do wonder what it needs the proper random seed for though.

 If anyone can come up with a solution I'll be grateful.

Probably investigating gnupg sources could give some clues wrt random seed
handling.


Thanks for the pointer, I'll check them out.

andrew



--
pub 4096R/0E4BD0AB 2003-03-18 people.fccf.net/danchev/key pgp.mit.edu
fingerprint 1AE7 7C66 0A26 5BFF DF22 5D55 1C57 0C89 0E4B D0AB


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
[EMAIL PROTECTED]





--
Andrew Donnellan
http://andrewdonnellan.com
http://ajdlinux.blogspot.com
Jabber - [EMAIL PROTECTED]
GPG - hkp://subkeys.pgp.net 0x5D4C0C58
---
Member of Linux Australia - http://linux.org.au
Debian user - http://debian.org
Get free rewards - http://ezyrewards.com/?id=23484
OpenNIC user - http://www.opennic.unrated.net


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: RFS: jabbin

2006-08-29 Thread Kapil Hari Paranjape
Hello,

On Tue, 29 Aug 2006, Andrew Donnellan wrote:
 On 8/25/06, Hubert Chan [EMAIL PROTECTED] wrote:
 Err, I don't think that __GNUC__ actually guarantees the presence of
 /dev/random.  So this patch does not seem to be correct.
 
 (Although /dev/random, if you have it, is probably a better source of
 randomness than rdtsc, or gethrtime.)
 
 So what would be the alternative? Would we have to use a makefile hack
 (e.g. test for the existence of /dev/random and set a compile flag) or
 something to figure out what random seed we should use?

Unless you need cryptographically secure random-ness (which is
unlikely since this is a test suite) any pseudo-random generator
should be adequate as a source of randomness. So you could use (for
example) some post-header portion of a gzipped file. Of course, this
gives you deterministic random-ness which sounds like an
oxymoron---but isn't according to recent results in Complexity!

Regards,

Kapil.
--


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: RFS: jabbin

2006-08-29 Thread Hubert Chan

 Hello,
 On Tue, 29 Aug 2006, Andrew Donnellan wrote:

 On 8/25/06, Hubert Chan [EMAIL PROTECTED] wrote:
 So what would be the alternative? Would we have to use a makefile hack
 (e.g. test for the existence of /dev/random and set a compile flag) or
 something to figure out what random seed we should use?

Usually, you would do a test in ./configure.

 Unless you need cryptographically secure random-ness (which is
 unlikely since this is a test suite) any pseudo-random generator
 should be adequate as a source of randomness. So you could use (for
 example) some post-header portion of a gzipped file. Of course, this
 gives you deterministic random-ness which sounds like an
 oxymoron---but isn't according to recent results in Complexity!

I haven't actually looked at the source.  If this is just a test suite,
and it isn't actually used for anything important, then it may be
sufficient to just use the output of time(2).  I really don't know why
they're using rdtsc as a source of randomness...

It's probably not a good idea to use a portion of a known file, since
then your seed is completely deterministic, and you lose the advantage
of setting a seed.

 Also would it be OK to include this as a Debian patch, esp. because at
 the moment Debian doesn't have any non-glibc ports?

IMHO, if you include this as a Debian-only patch, then it would be best
to get rid of the whole #if section, and put in the this should work
for all Debian ports code, instead of having an #if test that tests the
wrong thing.  But that's just IMHO.

But I think that upstream probably would want to have a more general
fix.  And IMHO, we should always try to come up with general fixes,
instead of just Debian-specific fixes.

-- 
Hubert Chan - email  Jabber: [EMAIL PROTECTED] - http://www.uhoreg.ca/
PGP/GnuPG key: 1024D/124B61FA   (Key available at wwwkeys.pgp.net)
Fingerprint: 96C5 012F 5F74 A5F7 1FF7  5291 AF29 C719 124B 61FA


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: RFS: jabbin

2006-08-29 Thread Andrew Donnellan

On 8/30/06, Hubert Chan [EMAIL PROTECTED] wrote:


 Hello,
 On Tue, 29 Aug 2006, Andrew Donnellan wrote:

 On 8/25/06, Hubert Chan [EMAIL PROTECTED] wrote:
 So what would be the alternative? Would we have to use a makefile hack
 (e.g. test for the existence of /dev/random and set a compile flag) or
 something to figure out what random seed we should use?

Usually, you would do a test in ./configure.

 Unless you need cryptographically secure random-ness (which is
 unlikely since this is a test suite) any pseudo-random generator
 should be adequate as a source of randomness. So you could use (for
 example) some post-header portion of a gzipped file. Of course, this
 gives you deterministic random-ness which sounds like an
 oxymoron---but isn't according to recent results in Complexity!

I haven't actually looked at the source.  If this is just a test suite,
and it isn't actually used for anything important, then it may be
sufficient to just use the output of time(2).  I really don't know why
they're using rdtsc as a source of randomness...


Being among some STUN code makes me think the randomness may actually
be used for some encryption or as some sort of UID.



It's probably not a good idea to use a portion of a known file, since
then your seed is completely deterministic, and you lose the advantage
of setting a seed.

 Also would it be OK to include this as a Debian patch, esp. because at
 the moment Debian doesn't have any non-glibc ports?

IMHO, if you include this as a Debian-only patch, then it would be best
to get rid of the whole #if section, and put in the this should work
for all Debian ports code, instead of having an #if test that tests the
wrong thing.  But that's just IMHO.

But I think that upstream probably would want to have a more general
fix.  And IMHO, we should always try to come up with general fixes,
instead of just Debian-specific fixes.


Well it seems that unless someone else can come up with a fix this is
what I'll have to do. A configure fix would be nice but I don't have
the time to do it.

andrew

--
Andrew Donnellan
http://andrewdonnellan.com
http://ajdlinux.blogspot.com
Jabber - [EMAIL PROTECTED]
GPG - hkp://subkeys.pgp.net 0x5D4C0C58
---
Member of Linux Australia - http://linux.org.au
Debian user - http://debian.org
Get free rewards - http://ezyrewards.com/?id=23484
OpenNIC user - http://www.opennic.unrated.net


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: RFS: jabbin

2006-08-24 Thread Andrew Donnellan

I've found the relevant piece of code:

#if defined(WIN32)
 volatile unsigned int lowtick=0,hightick=0;
 __asm
{
   rdtsc
  mov lowtick, eax
  mov hightick, edx
  }
 tick = hightick;
 tick = 32;
 tick |= lowtick;
#elif defined(__GNUC__)  ( defined(__i686__) || defined(__i386__) )
 asm(rdtsc : =A (tick));
#elif defined (__SUNPRO_CC) || defined( __sparc__ ) 
 tick = gethrtime();
#elif defined(__MACH__)
 int fd=open(/dev/random,O_RDONLY);
 read(fd,tick,sizeof(tick));
 closesocket(fd);
#else
# error Need some way to seed the random number generator
#endif
 int seed = int(tick);
#ifdef WIN32
 srand(seed);
#else
 srandom(seed);
#endif
  }

Does anyone know what the appropriate code for PowerPC would be?

On 8/24/06, Andrew Donnellan [EMAIL PROTECTED] wrote:

On 8/24/06, Francesco Pedrini [EMAIL PROTECTED] wrote:
On Sunday 06 August 2006 06:40, Andrew Donnellan wrote:
  I am looking for a sponsor for my package jabbin.
 
  * Package name: jabbin
Version : 2.0beta2-2
Upstream Author : Stefano Grini [EMAIL PROTECTED]/Jabbin
  Team http://jabbin.com
  * URL : http://jabbin.com
  * License : GPL
Section : net
 
  It builds these binary packages:
  jabbin - Jabber IM client with VoIP support

 I've tried to build jabbin on my iBook (ppc), but it FTBFS with

 g++ -c -pipe -O0 -g3 -Wall -W -g -D_REENTRANT  -DHAVE_XSS -DPOSIX -DJINGLE
-DQCA_STATIC -DOSSL_097 -DXMPP_TEST -DQT_THREAD_SUPPORT -DQT_SHARED
-DQT_TABLET_SUPPORT -I/usr/share/qt3/mkspecs/default -I.
-I../3party/libjingle -I../voip -I../3party/jrtplib -I../voip/portaudio
-Icutestuff/util -Icutestuff/network -Itools/trayicon -Itools/idle
-Itools/systemwatch -Itools/mac_dock -Itools/zip -Itools/dirwatch
-Itools/openpgp -Itools/globalaccel -Itools/advwidget -I../3party/qca
-I../iris/libidn -I../iris/include -I../iris/xmpp-core -I../iris/xmpp-im
-I../iris/jabber -Ilibpsi/iconset -Ilibpsi/psiwidgets -Ilibpsi/psipng
-I/usr/include/qt3 -I/usr/X11R6/include -I.ui/ -I. -Ioptions -I.moc/ -o
.obj/stun.o ../voip/stun.cpp
 ../voip/stun.cpp:681:7: error: #error Need some way to seed the random
 number generator

This must be an error generated in an #ifdef or something. As I can't
hack C++ I'll just report it to upstream.

andrew


 ../voip/stun.cpp:722: warning: unused parameter 'input'
 ../voip/stun.cpp:722: warning: unused parameter 'length'
 ../voip/stun.cpp:722: warning: unused parameter 'key'
 ../voip/stun.cpp:722: warning: unused parameter 'sizeKey'
 make[2]: *** [.obj/stun.o] Error 1
 make[2]: Leaving directory `/tmp/buildd/jabbin-2.0beta2a/src'
 make[1]: *** [sub-src] Error 2
 make[1]: Leaving directory `/tmp/buildd/jabbin-2.0beta2a'
 make: *** [build-stamp] Error 2

 HTH

 Francesco.


 --
 :wq


 --
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact
[EMAIL PROTECTED]






--
Andrew Donnellan
http://andrewdonnellan.com
http://ajdlinux.blogspot.com
Jabber - [EMAIL PROTECTED]
GPG - hkp://subkeys.pgp.net 0x5D4C0C58
---
Member of Linux Australia - http://linux.org.au
Debian user - http://debian.org
Get free rewards - http://ezyrewards.com/?id=23484
OpenNIC user - http://www.opennic.unrated.net


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: RFS: jabbin

2006-08-24 Thread Andrew Donnellan

OK, here's an update.

I've reported the PPC bug to upstream who are now working on it, and
I've prepared a new version which has some packaging probs fixed and
the ~ version number as suggested. Here's a new RFS.

Dear mentors,

I am looking for a sponsor for my package jabbin.

* Package name: jabbin
 Version : 2.0~beta2a-2
 Upstream Author : Stefano Grini [EMAIL PROTECTED]
* URL : http://jabbin.com
* License : GPL
 Section : net

It builds these binary packages:
jabbin - Jabber IM client with VoIP support

NOTE ON LINTIAN CLEANLINESS: the main error is the ~ in the version name.

The package can be found on mentors.debian.net:
- URL: http://mentors.debian.net/debian/pool/main/j/jabbin
- Source repository: deb-src http://mentors.debian.net/debian unstable
main contrib non-free
- dget 
http://mentors.debian.net/debian/pool/main/j/jabbin/jabbin_2.0~beta2a-2.dsc

I would be glad if someone uploaded this package for me.

Kind regards
Andrew Donnellan

On 8/24/06, Andrew Donnellan [EMAIL PROTECTED] wrote:

I've found the relevant piece of code:

#if defined(WIN32)
  volatile unsigned int lowtick=0,hightick=0;
  __asm
 {
rdtsc
   mov lowtick, eax
   mov hightick, edx
   }
  tick = hightick;
  tick = 32;
  tick |= lowtick;
#elif defined(__GNUC__)  ( defined(__i686__) || defined(__i386__) )
  asm(rdtsc : =A (tick));
#elif defined (__SUNPRO_CC) || defined( __sparc__ ) 
  tick = gethrtime();
#elif defined(__MACH__)
  int fd=open(/dev/random,O_RDONLY);
  read(fd,tick,sizeof(tick));
  closesocket(fd);
#else
# error Need some way to seed the random number generator
#endif
  int seed = int(tick);
#ifdef WIN32
  srand(seed);
#else
  srandom(seed);
#endif
   }

Does anyone know what the appropriate code for PowerPC would be?

On 8/24/06, Andrew Donnellan [EMAIL PROTECTED] wrote:
 On 8/24/06, Francesco Pedrini [EMAIL PROTECTED] wrote:
 On Sunday 06 August 2006 06:40, Andrew Donnellan wrote:
   I am looking for a sponsor for my package jabbin.
  
   * Package name: jabbin
 Version : 2.0beta2-2
 Upstream Author : Stefano Grini [EMAIL PROTECTED]/Jabbin
   Team http://jabbin.com
   * URL : http://jabbin.com
   * License : GPL
 Section : net
  
   It builds these binary packages:
   jabbin - Jabber IM client with VoIP support
 
  I've tried to build jabbin on my iBook (ppc), but it FTBFS with
 
  g++ -c -pipe -O0 -g3 -Wall -W -g -D_REENTRANT  -DHAVE_XSS -DPOSIX
-DJINGLE
 -DQCA_STATIC -DOSSL_097 -DXMPP_TEST -DQT_THREAD_SUPPORT -DQT_SHARED
 -DQT_TABLET_SUPPORT -I/usr/share/qt3/mkspecs/default -I.
 -I../3party/libjingle -I../voip -I../3party/jrtplib -I../voip/portaudio
 -Icutestuff/util -Icutestuff/network -Itools/trayicon -Itools/idle
 -Itools/systemwatch -Itools/mac_dock -Itools/zip -Itools/dirwatch
 -Itools/openpgp -Itools/globalaccel -Itools/advwidget -I../3party/qca
 -I../iris/libidn -I../iris/include -I../iris/xmpp-core -I../iris/xmpp-im
 -I../iris/jabber -Ilibpsi/iconset -Ilibpsi/psiwidgets -Ilibpsi/psipng
 -I/usr/include/qt3 -I/usr/X11R6/include -I.ui/ -I. -Ioptions -I.moc/ -o
 .obj/stun.o ../voip/stun.cpp
  ../voip/stun.cpp:681:7: error: #error Need some way to seed the random
  number generator

 This must be an error generated in an #ifdef or something. As I can't
 hack C++ I'll just report it to upstream.

 andrew


  ../voip/stun.cpp:722: warning: unused parameter 'input'
  ../voip/stun.cpp:722: warning: unused parameter 'length'
  ../voip/stun.cpp:722: warning: unused parameter 'key'
  ../voip/stun.cpp:722: warning: unused parameter 'sizeKey'
  make[2]: *** [.obj/stun.o] Error 1
  make[2]: Leaving directory `/tmp/buildd/jabbin-2.0beta2a/src'
  make[1]: *** [sub-src] Error 2
  make[1]: Leaving directory `/tmp/buildd/jabbin-2.0beta2a'
  make: *** [build-stamp] Error 2
 
  HTH
 
  Francesco.
 
 
  --
  :wq
 
 
  --
  To UNSUBSCRIBE, email to [EMAIL PROTECTED]
  with a subject of unsubscribe. Trouble? Contact
 [EMAIL PROTECTED]
 
 



--
Andrew Donnellan
http://andrewdonnellan.com
http://ajdlinux.blogspot.com
Jabber - [EMAIL PROTECTED]
GPG - hkp://subkeys.pgp.net 0x5D4C0C58
---
Member of Linux Australia - http://linux.org.au
Debian user - http://debian.org
Get free rewards - http://ezyrewards.com/?id=23484
OpenNIC user - http://www.opennic.unrated.net




--
Andrew Donnellan
http://andrewdonnellan.com
http://ajdlinux.blogspot.com
Jabber - [EMAIL PROTECTED]
GPG - hkp://subkeys.pgp.net 0x5D4C0C58
---
Member of Linux Australia - http://linux.org.au
Debian user - http://debian.org
Get free rewards - http://ezyrewards.com/?id=23484
OpenNIC user - http://www.opennic.unrated.net


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: RFS: jabbin

2006-08-24 Thread Francesco Pedrini
On Thursday 24 August 2006 09:45, Andrew Donnellan wrote:
 I've found the relevant piece of code:
[SNIP]
 #elif defined(__GNUC__)  ( defined(__i686__) || defined(__i386__) )
   asm(rdtsc : =A (tick));
 #elif defined (__SUNPRO_CC) || defined( __sparc__ )
   tick = gethrtime();
 #elif defined(__MACH__)
   int fd=open(/dev/random,O_RDONLY);
   read(fd,tick,sizeof(tick));
   closesocket(fd);
 #else
 # error Need some way to seed the random number generator
 #endif
[SNIP]

 Does anyone know what the appropriate code for PowerPC would be?

The attached patch should fix the compilation on *all* non linux-x86 
archs, without breaking the supported archs.

please test it on other archs, i've tested only on linux-x86 and 
linux-ppc.


Regards
Francesco

-- 
:wq
--- /tmp/jabbin-2.0beta2a/voip/stun.cpp	2006-08-10 12:09:57.0 +0200
+++ jabbin-2.0beta2a/voip/stun.cpp	2006-08-25 00:58:44.0 +0200
@@ -669,17 +669,13 @@
   tick = hightick;
   tick = 32;
   tick |= lowtick;
-#elif defined(__GNUC__)  ( defined(__i686__) || defined(__i386__) )
-  asm(rdtsc : =A (tick));
 #elif defined (__SUNPRO_CC) || defined( __sparc__ )	
   tick = gethrtime();
-#elif defined(__MACH__) 
+#elif defined( __MACH__ )|| defined( __GNUC__ ) 
   int fd=open(/dev/random,O_RDONLY);
   read(fd,tick,sizeof(tick));
   closesocket(fd);
-#else
-# error Need some way to seed the random number generator 
-#endif 
+#endif
   int seed = int(tick);
 #ifdef WIN32
   srand(seed);


pgpfouvEcBNi4.pgp
Description: PGP signature


Re: RFS: jabbin

2006-08-24 Thread Hubert Chan
On Fri, 25 Aug 2006 01:03:52 +0200, Francesco Pedrini [EMAIL PROTECTED] said:

 On Thursday 24 August 2006 09:45, Andrew Donnellan wrote:
 I've found the relevant piece of code:
 [...]
 Does anyone know what the appropriate code for PowerPC would be?

 The attached patch should fix the compilation on *all* non linux-x86
 archs, without breaking the supported archs.

,
| --- /tmp/jabbin-2.0beta2a/voip/stun.cpp   2006-08-10 12:09:57.0 
+0200
| +++ jabbin-2.0beta2a/voip/stun.cpp2006-08-25 00:58:44.0 +0200
| @@ -669,17 +669,13 @@
|tick = hightick;
|tick = 32;
|tick |= lowtick;
| -#elif defined(__GNUC__)  ( defined(__i686__) || defined(__i386__) )
| -  asm(rdtsc : =A (tick));
|  #elif defined (__SUNPRO_CC) || defined( __sparc__ )  
|tick = gethrtime();
| -#elif defined(__MACH__) 
| +#elif defined( __MACH__ )|| defined( __GNUC__ ) 
|int fd=open(/dev/random,O_RDONLY);
|read(fd,tick,sizeof(tick));
|closesocket(fd);

Err, I don't think that __GNUC__ actually guarantees the presence of
/dev/random.  So this patch does not seem to be correct.

(Although /dev/random, if you have it, is probably a better source of
randomness than rdtsc, or gethrtime.)

| -#else
| -# error Need some way to seed the random number generator 
| -#endif 
| +#endif

If it really does need a proper random seed, then you should not be
getting rid of the compilation error.  It may compile correctly, but it
will not work as intended.

|int seed = int(tick);
|  #ifdef WIN32
|srand(seed);
`


-- 
Hubert Chan - email  Jabber: [EMAIL PROTECTED] - http://www.uhoreg.ca/
PGP/GnuPG key: 1024D/124B61FA   (Key available at wwwkeys.pgp.net)
Fingerprint: 96C5 012F 5F74 A5F7 1FF7  5291 AF29 C719 124B 61FA


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: RFS: jabbin

2006-08-23 Thread Francesco Pedrini
On Sunday 06 August 2006 06:40, Andrew Donnellan wrote:
 I am looking for a sponsor for my package jabbin.

 * Package name: jabbin
   Version : 2.0beta2-2
   Upstream Author : Stefano Grini [EMAIL PROTECTED]/Jabbin
 Team http://jabbin.com
 * URL : http://jabbin.com
 * License : GPL
   Section : net

 It builds these binary packages:
 jabbin - Jabber IM client with VoIP support

I've tried to build jabbin on my iBook (ppc), but it FTBFS with 

g++ -c -pipe -O0 -g3 -Wall -W -g -D_REENTRANT  -DHAVE_XSS -DPOSIX -DJINGLE 
-DQCA_STATIC -DOSSL_097 -DXMPP_TEST -DQT_THREAD_SUPPORT -DQT_SHARED 
-DQT_TABLET_SUPPORT -I/usr/share/qt3/mkspecs/default -I. -I../3party/libjingle 
-I../voip -I../3party/jrtplib -I../voip/portaudio -Icutestuff/util 
-Icutestuff/network -Itools/trayicon -Itools/idle -Itools/systemwatch 
-Itools/mac_dock -Itools/zip -Itools/dirwatch -Itools/openpgp 
-Itools/globalaccel -Itools/advwidget -I../3party/qca -I../iris/libidn 
-I../iris/include -I../iris/xmpp-core -I../iris/xmpp-im -I../iris/jabber 
-Ilibpsi/iconset -Ilibpsi/psiwidgets -Ilibpsi/psipng -I/usr/include/qt3 
-I/usr/X11R6/include -I.ui/ -I. -Ioptions -I.moc/ -o .obj/stun.o 
../voip/stun.cpp
../voip/stun.cpp:681:7: error: #error Need some way to seed the random 
number generator
../voip/stun.cpp:722: warning: unused parameter 'input'
../voip/stun.cpp:722: warning: unused parameter 'length'
../voip/stun.cpp:722: warning: unused parameter 'key'
../voip/stun.cpp:722: warning: unused parameter 'sizeKey'
make[2]: *** [.obj/stun.o] Error 1
make[2]: Leaving directory `/tmp/buildd/jabbin-2.0beta2a/src'
make[1]: *** [sub-src] Error 2
make[1]: Leaving directory `/tmp/buildd/jabbin-2.0beta2a'
make: *** [build-stamp] Error 2

HTH

Francesco.


-- 
:wq


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: RFS: jabbin

2006-08-23 Thread Andrew Donnellan

On 8/24/06, Francesco Pedrini [EMAIL PROTECTED] wrote:
On Sunday 06 August 2006 06:40, Andrew Donnellan wrote:

 I am looking for a sponsor for my package jabbin.

 * Package name: jabbin
   Version : 2.0beta2-2
   Upstream Author : Stefano Grini [EMAIL PROTECTED]/Jabbin
 Team http://jabbin.com
 * URL : http://jabbin.com
 * License : GPL
   Section : net

 It builds these binary packages:
 jabbin - Jabber IM client with VoIP support

I've tried to build jabbin on my iBook (ppc), but it FTBFS with

g++ -c -pipe -O0 -g3 -Wall -W -g -D_REENTRANT  -DHAVE_XSS -DPOSIX -DJINGLE 
-DQCA_STATIC -DOSSL_097 -DXMPP_TEST -DQT_THREAD_SUPPORT -DQT_SHARED 
-DQT_TABLET_SUPPORT -I/usr/share/qt3/mkspecs/default -I. -I../3party/libjingle 
-I../voip -I../3party/jrtplib -I../voip/portaudio -Icutestuff/util 
-Icutestuff/network -Itools/trayicon -Itools/idle -Itools/systemwatch 
-Itools/mac_dock -Itools/zip -Itools/dirwatch -Itools/openpgp 
-Itools/globalaccel -Itools/advwidget -I../3party/qca -I../iris/libidn 
-I../iris/include -I../iris/xmpp-core -I../iris/xmpp-im -I../iris/jabber 
-Ilibpsi/iconset -Ilibpsi/psiwidgets -Ilibpsi/psipng -I/usr/include/qt3 
-I/usr/X11R6/include -I.ui/ -I. -Ioptions -I.moc/ -o .obj/stun.o 
../voip/stun.cpp
../voip/stun.cpp:681:7: error: #error Need some way to seed the random
number generator


This must be an error generated in an #ifdef or something. As I can't
hack C++ I'll just report it to upstream.

andrew



../voip/stun.cpp:722: warning: unused parameter 'input'
../voip/stun.cpp:722: warning: unused parameter 'length'
../voip/stun.cpp:722: warning: unused parameter 'key'
../voip/stun.cpp:722: warning: unused parameter 'sizeKey'
make[2]: *** [.obj/stun.o] Error 1
make[2]: Leaving directory `/tmp/buildd/jabbin-2.0beta2a/src'
make[1]: *** [sub-src] Error 2
make[1]: Leaving directory `/tmp/buildd/jabbin-2.0beta2a'
make: *** [build-stamp] Error 2

HTH

Francesco.


--
:wq


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]





--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: RFS: jabbin

2006-08-16 Thread Andrew Donnellan

On 8/16/06, Mikael Magnusson [EMAIL PROTECTED] wrote:
On Tue, Aug 15, 2006 at 05:26:06PM +1000, Andrew Donnellan wrote:

 On 8/15/06, Tzafrir Cohen [EMAIL PROTECTED] wrote:
 It's based on psi, which is already packaged. What are the pros/cons of
 it vs. psi?

 Voice support. Video support is planned at a later stage.

 andrew

 
 I'm trying to build it now on Sarge/amd64...
 

I have built it on testing/unstable x86, but I haven't tried it much
yet. I'm including a patch that uses libjingle and portaudio library
packages from Debian instead of linking statically against the built-in
third part sources.


Thanks! Upstream seems to have told me that the libjingle in Debian is
different from the libjingle that they use in the source - they claim
that the libjingle in their tarball is modified from the original
Google one. But if it seems to work using Debian libjingle then I may
forward the patch upstream and get them to add libjingle to
build-deps.

andrew




Mikael






--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: RFS: jabbin

2006-08-15 Thread Andrew Donnellan

On 8/15/06, Tzafrir Cohen [EMAIL PROTECTED] wrote:

On Tue, Aug 15, 2006 at 01:43:32AM +, Andrew Donnellan wrote:
 Is anyone interested in sponsoring this package? I'm happy to fix any
 problems and I'm in close contact with upstream.

 (VoIP team cc'd, maybe this would interest you guys)

It's based on psi, which is already packaged. What are the pros/cons of
it vs. psi?


Voice support. Video support is planned at a later stage.

andrew



I'm trying to build it now on Sarge/amd64...

--
Tzafrir Cohen sip:[EMAIL PROTECTED]
icq#16849755  iax:[EMAIL PROTECTED]
+972-50-7952406  jabber:[EMAIL PROTECTED]
[EMAIL PROTECTED] http://www.xorcom.com




--
Andrew Donnellan
http://andrewdonnellan.com
http://ajdlinux.blogspot.com
Jabber - [EMAIL PROTECTED]
GPG - hkp://subkeys.pgp.net 0x5D4C0C58
---
Member of Linux Australia - http://linux.org.au
Debian user - http://debian.org
Get free rewards - http://ezyrewards.com/?id=23484
OpenNIC user - http://www.opennic.unrated.net


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: RFS: jabbin

2006-08-15 Thread Christoph Haas
On Tuesday 15 August 2006 03:43, Andrew Donnellan wrote:
 Is anyone interested in sponsoring this package? I'm happy to fix any
 problems and I'm in close contact with upstream.

I just took a look at the package. Various thoughts:

- the orig.tar.gz that you provide differs in some places from the
  source tarball available from http://www.jabbin.com/int/download
- consider using a version of 2.0~beta2. That way you can later
  call it 2.0 and it will be treated as newer. If you now use
  2.0-beta2 then 2.0 will be considered as older by the numbering
  scheme.
- in debian/rules's 'clean:' target you clean away a Makefile.
  But there are several other Makefiles throughout the tree.
- you set export DH_COMPAT=4 in debian/rules but ship a
  debian/compat of 5. User either one.
- Also the package is not lintian-clean.

Cheers
 Christoph
-- 
~
~
.signature [Modified] 1 line --100%--1,48 All


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: RFS: jabbin

2006-08-15 Thread Andrew Donnellan

On 8/15/06, Christoph Haas [EMAIL PROTECTED] wrote:

On Tuesday 15 August 2006 03:43, Andrew Donnellan wrote:
 Is anyone interested in sponsoring this package? I'm happy to fix any
 problems and I'm in close contact with upstream.

I just took a look at the package. Various thoughts:

- the orig.tar.gz that you provide differs in some places from the
  source tarball available from http://www.jabbin.com/int/download


Sorry, yeah the orig.tar.gz I've shipped I'm actually meaning to
release upstream. It's only a cleanup that resolves some issues with
Makefiles etc.


- consider using a version of 2.0~beta2. That way you can later
  call it 2.0 and it will be treated as newer. If you now use
  2.0-beta2 then 2.0 will be considered as older by the numbering
  scheme.


Will do.


- in debian/rules's 'clean:' target you clean away a Makefile.
  But there are several other Makefiles throughout the tree.


The newer tarball should fix this problem, the rm statements should be
removed soon.


- you set export DH_COMPAT=4 in debian/rules but ship a
  debian/compat of 5. User either one.


That export statement was inherited from psi, will remove.


- Also the package is not lintian-clean.


Working on it.

andrew



Cheers
 Christoph
--
~
~
.signature [Modified] 1 line --100%--1,48 All


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
[EMAIL PROTECTED]





--
Andrew Donnellan
http://andrewdonnellan.com
http://ajdlinux.blogspot.com
Jabber - [EMAIL PROTECTED]
GPG - hkp://subkeys.pgp.net 0x5D4C0C58
---
Member of Linux Australia - http://linux.org.au
Debian user - http://debian.org
Get free rewards - http://ezyrewards.com/?id=23484
OpenNIC user - http://www.opennic.unrated.net


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: RFS: jabbin

2006-08-14 Thread Andrew Donnellan

Is anyone interested in sponsoring this package? I'm happy to fix any
problems and I'm in close contact with upstream.

(VoIP team cc'd, maybe this would interest you guys)

TIA
Andrew


On 8/6/06, Andrew Donnellan [EMAIL PROTECTED] wrote:
I am looking for a sponsor for my package jabbin.


* Package name: jabbin
  Version : 2.0beta2-2
  Upstream Author : Stefano Grini [EMAIL PROTECTED]/Jabbin Team
http://jabbin.com
* URL : http://jabbin.com
* License : GPL
  Section : net

It builds these binary packages:
jabbin - Jabber IM client with VoIP support

The package is not lintian clean, there are quite a few warnings,
however the problems are due to an unclean upstream tarball. Upstream
has promised to fix the problems soon.

The package is not very clean (it still has a lot of example files and
stuff) but I am working on that. It also does not contain much by way
of documentation (not even a man page).

The package can be found on mentors.debian.net:
- URL: http://mentors.debian.net/debian/pool/main/j/jabbin
- Source repository: deb-src http://mentors.debian.net/debian unstable
main contrib non-free
- dget http://mentors.debian.net/debian/pool/main/j/jabbin/jabbin_2.0beta2-2.dsc

I would be glad if someone uploaded this package for me.

TIA,
--
Andrew Donnellan
http://andrewdonnellan.com
http://ajdlinux.blogspot.com
Jabber - [EMAIL PROTECTED]
GPG - hkp://subkeys.pgp.net 0x5D4C0C58
---
Member of Linux Australia - http://linux.org.au
Debian user - http://debian.org
Get free rewards - http://ezyrewards.com/?id=23484
OpenNIC user - http://www.opennic.unrated.net




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: RFS: jabbin

2006-08-07 Thread Andrew Donnellan

On 8/6/06, George Danchev [EMAIL PROTECTED] wrote:

Hi,
Just to let you know that the upstream tarball
(jabbin_2.0beta2.orig.tar.gz)
contains non-free bits, that is 3party/iLBC/* [1], thus you should repackage
it as dfsg tarball with these bits removed. I don't know how vital that is
for the jabbin application, but you can give it a try, considering the
possible impacts. Also talk to upstream to consider remove it from their
next
version too. This seems to be a common problem for almost all voip apps
around, and you might find more specialized help by pkg-voip people [2] if
you need to.


I can confirm that the 3party/iLBC directory is not listed in the
Makefiles and therefore can be removed safely without any problems.
(not yet tested, will test soon) I'm helping upstream produce a new
tarball without the SVN directories left in or the original Makefiles
and also producing documentation.

I'm considering co-maintaining this, if anyone wants to help feel free to ask.

--
Andrew Donnellan
http://andrewdonnellan.com
http://ajdlinux.blogspot.com
Jabber - [EMAIL PROTECTED]
GPG - hkp://subkeys.pgp.net 0x5D4C0C58
---
Member of Linux Australia - http://linux.org.au
Debian user - http://debian.org
Get free rewards - http://ezyrewards.com/?id=23484
OpenNIC user - http://www.opennic.unrated.net


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: RFS: jabbin

2006-08-07 Thread Andrew Donnellan

On 8/7/06, George Danchev [EMAIL PROTECTED] wrote:

Sounds great.


I'm also busy fixing up their license notices and stuff, I have write
access to upstream SVN so bugs can be fixed and so on.



 I'm considering co-maintaining this, if anyone wants to help feel free to
 ask.

I noone steps in, you can contact VoIP maintainers at:

[EMAIL PROTECTED]


I have considered the VoIP team as possible co-maintainers, yes.



You will probably get write access to their SVN repo (I don't know if svn if
fine with you, though ;-) you can browse at:


I have read the discussion on -devel, and all I can say is that SVN is
the most easy to use decent VCS I've seen. :)


http://svn.debian.org/wsvn/pkg-voip

You will certaintly get your voip package uploaded by someone from the VoIP
team when the package is ready to hit the archive ;-)


Hopefully soon :)

--
Andrew Donnellan
http://andrewdonnellan.com
http://ajdlinux.blogspot.com
Jabber - [EMAIL PROTECTED]
GPG - hkp://subkeys.pgp.net 0x5D4C0C58
---
Member of Linux Australia - http://linux.org.au
Debian user - http://debian.org
Get free rewards - http://ezyrewards.com/?id=23484
OpenNIC user - http://www.opennic.unrated.net


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: RFS: jabbin

2006-08-06 Thread George Danchev
On Sunday 06 August 2006 07:40, Andrew Donnellan wrote:
 I am looking for a sponsor for my package jabbin.

 * Package name: jabbin
   Version : 2.0beta2-2
   Upstream Author : Stefano Grini [EMAIL PROTECTED]/Jabbin Team
 http://jabbin.com
 * URL : http://jabbin.com
 * License : GPL
   Section : net

 It builds these binary packages:
 jabbin - Jabber IM client with VoIP support

 The package is not lintian clean, there are quite a few warnings,
 however the problems are due to an unclean upstream tarball. Upstream
 has promised to fix the problems soon.

 The package is not very clean (it still has a lot of example files and
 stuff) but I am working on that. It also does not contain much by way
 of documentation (not even a man page).

 The package can be found on mentors.debian.net:
 - URL: http://mentors.debian.net/debian/pool/main/j/jabbin
 - Source repository: deb-src http://mentors.debian.net/debian unstable
 main contrib non-free
 - dget
 http://mentors.debian.net/debian/pool/main/j/jabbin/jabbin_2.0beta2-2.dsc

Hi,
Just to let you know that the upstream tarball 
(jabbin_2.0beta2.orig.tar.gz) 
contains non-free bits, that is 3party/iLBC/* [1], thus you should repackage 
it as dfsg tarball with these bits removed. I don't know how vital that is 
for the jabbin application, but you can give it a try, considering the 
possible impacts. Also talk to upstream to consider remove it from their next 
version too. This seems to be a common problem for almost all voip apps 
around, and you might find more specialized help by pkg-voip people [2] if 
you need to. 

[1] http://lists.debian.org/debian-legal/2005/10/msg2.html
[2] http://alioth.debian.org/projects/pkg-voip/

-- 
pub 4096R/0E4BD0AB 2003-03-18 people.fccf.net/danchev/key pgp.mit.edu
fingerprint 1AE7 7C66 0A26 5BFF DF22 5D55 1C57 0C89 0E4B D0AB 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: RFS: jabbin

2006-08-06 Thread Andrew Donnellan

Sorry, forgot to fix that. Upstream says iLBC isn't needed anymore and
they just forgot to remove it.

On 8/6/06, George Danchev [EMAIL PROTECTED] wrote:

On Sunday 06 August 2006 07:40, Andrew Donnellan wrote:
 I am looking for a sponsor for my package jabbin.

 * Package name: jabbin
   Version : 2.0beta2-2
   Upstream Author : Stefano Grini [EMAIL PROTECTED]/Jabbin Team
 http://jabbin.com
 * URL : http://jabbin.com
 * License : GPL
   Section : net

 It builds these binary packages:
 jabbin - Jabber IM client with VoIP support

 The package is not lintian clean, there are quite a few warnings,
 however the problems are due to an unclean upstream tarball. Upstream
 has promised to fix the problems soon.

 The package is not very clean (it still has a lot of example files and
 stuff) but I am working on that. It also does not contain much by way
 of documentation (not even a man page).

 The package can be found on mentors.debian.net:
 - URL: http://mentors.debian.net/debian/pool/main/j/jabbin
 - Source repository: deb-src http://mentors.debian.net/debian unstable
 main contrib non-free
 - dget
 http://mentors.debian.net/debian/pool/main/j/jabbin/jabbin_2.0beta2-2.dsc

Hi,
Just to let you know that the upstream tarball
(jabbin_2.0beta2.orig.tar.gz)
contains non-free bits, that is 3party/iLBC/* [1], thus you should repackage
it as dfsg tarball with these bits removed. I don't know how vital that is
for the jabbin application, but you can give it a try, considering the
possible impacts. Also talk to upstream to consider remove it from their
next
version too. This seems to be a common problem for almost all voip apps
around, and you might find more specialized help by pkg-voip people [2] if
you need to.

[1] http://lists.debian.org/debian-legal/2005/10/msg2.html
[2] http://alioth.debian.org/projects/pkg-voip/

--
pub 4096R/0E4BD0AB 2003-03-18 people.fccf.net/danchev/key pgp.mit.edu
fingerprint 1AE7 7C66 0A26 5BFF DF22 5D55 1C57 0C89 0E4B D0AB


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
[EMAIL PROTECTED]





--
Andrew Donnellan
http://andrewdonnellan.com
http://ajdlinux.blogspot.com
Jabber - [EMAIL PROTECTED]
GPG - hkp://subkeys.pgp.net 0x5D4C0C58
---
Member of Linux Australia - http://linux.org.au
Debian user - http://debian.org
Get free rewards - http://ezyrewards.com/?id=23484
OpenNIC user - http://www.opennic.unrated.net


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]