Your message dated Thu, 3 Aug 2023 01:09:42 -0500
with message-id <[email protected]>
and subject line Re: Bug#1036113: libpurple0: license conflict with libsasl2
has caused the Debian Bug report #1036113,
regarding libpurple0: license conflict with libsasl2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1036113: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036113
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libpurple0
Version: 2.14.12-1
Severity: serious
Hi,
libirc.so and libjabber.so.0.0.0 depend on libsasl2-2, which is licensed under CMU's BSD-3-Clause-Attribution license
and covered by the RSA-MD license. They have clauses in place, which are known to be incompatible with GPL-2+ (as far as
I can see the mentioned libraries' license). There are several possible solutions to this problem:
1) Build with --disable-cyrus-sasl configuration and get rid of the libsasl2
(Build-)Dependencies.
2) Support my request at #996892.
3) Ask upstream to add a license exception for libsasl2-2, similar to the one that was required by Debian for OpenSSL
for a long time.
Thanks for your consideration,
Bastian
--- End Message ---
--- Begin Message ---
That was the last remaining issue, so I am closing this.
I do not consider BSD-3-Clause-Attribution to be GPL incompatible. I
posted on debian-legal about this and the only response has been in
agreement.
--
Richard
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
