Bug#445726: libjinglebase0.3-0: Parts of libjinglebase is GPLv2 licensed and it links to OpenSSL

2008-03-09 Thread Dafydd Harries
Ar 07/10/2007 am 23:03, ysgrifennodd Thadeu Lima de Souza Cascardo:
 Package: libjinglebase0.3-0
 Version: 0.3.11-1
 Severity: serious
 Justification: Policy 2.3
 
 In the copyright file of libjinglebase, the Affine code is said to be
 licensed under the GPL version 2 or later. OpenSSL license is
 incompatible with GPL, as known by many.
 
 The usual options are:
 * ask permission to the said code to relicense (perhaps an exception
 allowing to link to OpenSSL)
 * remove or rewrite the said Affine code
 * remove OpenSSL support when building
 * try to use GNUTLS compatibility with OpenSSL
 * replace OpenSSL with GNUTLS or NSS, rewriting SSL/TLS support

I can't find the code this copyright statement refers to. Presumably the code
was removed upstream since that copyright notice was written. This suggests
that the appropriate fix is to just amend the copyright notice.

-- 
Dafydd



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



Bug#445726: libjinglebase0.3-0: Parts of libjinglebase is GPLv2 licensed and it links to OpenSSL

2008-02-07 Thread Marc 'HE' Brockschmidt
Heya,

You wanted to investigate how to fix the GPL/OpenSSL problems in
libjingle0.3 in october - did you come to any conclusions?

Marc
-- 
Fachbegriffe der Informatik - Einfach erklärt
193: PHP
   People Hate Perl (Kristian Köhntopp)




Bug#445726: libjinglebase0.3-0: Parts of libjinglebase is GPLv2 licensed and it links to OpenSSL

2007-10-18 Thread Dafydd Harries
Ar 07/10/2007 am 23:03, ysgrifennodd Thadeu Lima de Souza Cascardo:
 In the copyright file of libjinglebase, the Affine code is said to be
 licensed under the GPL version 2 or later. OpenSSL license is
 incompatible with GPL, as known by many.
 
 The usual options are:
 * ask permission to the said code to relicense (perhaps an exception
 allowing to link to OpenSSL)
 * remove or rewrite the said Affine code
 * remove OpenSSL support when building
 * try to use GNUTLS compatibility with OpenSSL
 * replace OpenSSL with GNUTLS or NSS, rewriting SSL/TLS support

I suspect we might just be able to remove this code. Will investigate.

-- 
Dafydd



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



Bug#445726: libjinglebase0.3-0: Parts of libjinglebase is GPLv2 licensed and it links to OpenSSL

2007-10-07 Thread Thadeu Lima de Souza Cascardo
Package: libjinglebase0.3-0
Version: 0.3.11-1
Severity: serious
Justification: Policy 2.3

In the copyright file of libjinglebase, the Affine code is said to be
licensed under the GPL version 2 or later. OpenSSL license is
incompatible with GPL, as known by many.

The usual options are:
* ask permission to the said code to relicense (perhaps an exception
allowing to link to OpenSSL)
* remove or rewrite the said Affine code
* remove OpenSSL support when building
* try to use GNUTLS compatibility with OpenSSL
* replace OpenSSL with GNUTLS or NSS, rewriting SSL/TLS support


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.22-2-vserver-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages libjinglebase0.3-0 depends on:
ii  openssl   0.9.8e-9   Secure Socket Layer (SSL) binary a

libjinglebase0.3-0 recommends no packages.

-- no debconf information



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