Paul van Tilburg wrote:
> 
> Now that jabber14 1.6.0 is out[1], I would really like to have this 
> in Debian.  This upstream release boosts this server to complete XMPP
> compliance and deals with many past issues.

I don't know that such a major change would be able to make it into etch
at this point, but I will certainly look to packaging it for etch+1.

> I have talked with upstream about the licensing.  Currently, the only
> non-GPL licensed file is snprintf.c, which is not used on the 
> GNU/Linux platform.  It is there to be able to support more Unices. 
> This means that a DFSG clean tarball can be constructed and used to 
> distribute 1.6.0 under the terms of the GPL.

This is true only if OpenSSL is removed from the resultant package as
far as I know.  Additionally, as you indicate a DFSG clean tarball would
need to be constructed, removing snprintf.c (this is trivial).  However,
loss of SSL support upon upgrade is a larger concern for me.  Upgrading
users from a version of the jabber package that supports SSL to a
version that doesn't isn't a good idea in my opinion.

> I see that in over almost two years there has been no activity 
> surrounding this package (except for some work by Andi).

Most of the potential updates to the package have been postponed waiting
the licensing outcome as I didn't feel I could meet the requirements of
JOSL license.

An updated package for 1.6.0 could indeed be made, but I fear that such
a package will likely be seen as a regression or loss of features by
most users as I'll have to remove the SSL support due to potential
licensing conflicts (OpenSSL and GPL linking without a waiver). For more
information on this, please read Matthias Wimmer's update to this bug.

> If you do not have the time to maintain it or are no longer 
> interested, I would like to request to adopt this package from you. I
> talk with upstream frequently and also use and administrate the 
> server intensively.

Contributions to the package and/or co-maintainers are certainly welcome.

-- 
Jamin W. Collins


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

Reply via email to