Adrian Bunk schrieb:
On Sat, Mar 14, 2009 at 01:48:41PM +0000, Stephen Gran wrote:
This one time, at band camp, Adrian Bunk said:
On Sat, Mar 14, 2009 at 12:40:19PM +0100, Michael Biebl wrote:
Tracker itself does not link against libssl. Problems seems to be, that it uses
libraptor, which itself uses libcurl3, that then pulls libssl.
I don't see, how I can do something about that within the tracker package. FWIW,
the tracker debian package has no dependency on libssl.
Could you clarify, where you see the license violation.
OpenSSL has a not GPL compatible licence, and tracker is a GPLed program
that is (through intermediate libraries) linked with OpenSSL.
Another way to ask the question is: Since the package linking to libssl
is out of the control of the tracker maintainer, in what way is this
helpful? Shouldn't the report go against that library?
Technically the library itself is fine. Solving the problem most likely
involves a change to the library, but the package with a RC GPL
violation is tracker.
I might add, that it's not tracker alone. I started checking the
rdepends of libraptor and stopped when I had 5 packages that are GPL2
only...
Cheers,
Michael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
