Bug#1012636: isync: license conflict with libsasl2

2022-11-19 Thread Oswald Buddenhagen
On Fri, Nov 18, 2022 at 08:51:51PM +0100, Pierre-Elliott Bécue wrote: Would you agree to release isync 1.4.5 or do I need to import your license exception? the thing is that it isn't even in master - i pushed a preliminary commit to a branch. the reason for that is that its legal foundation is

Bug#1012636: isync: license conflict with libsasl2

2022-11-18 Thread Pierre-Elliott Bécue
Hi Oswald, Bastian Germann wrote on 12/11/2022 at 16:46:44+0100: > I see that in git there is now LicenseRef-isync-GPL-exception applied to > mbsync. Would you agree to release isync 1.4.5 or do I need to import your license exception? Cheers! -- PEB signature.asc Description: PGP

Bug#1012636: isync: license conflict with libsasl2

2022-11-12 Thread Bastian Germann
I see that in git there is now LicenseRef-isync-GPL-exception applied to mbsync.

Bug#1012636: isync: license conflict with libsasl2

2022-06-10 Thread Oswald Buddenhagen
On Fri, Jun 10, 2022 at 10:45:53PM +0200, Bastian Germann wrote: isync (mbsync binary) is GPL-2+ licensed and depends on libsasl2-2, which is licensed under CMU's BSD-4-clause license and covered by the RSA-MD and OpenSSL licenses. whoops. 3) Ask upstream to add a license exception for

Bug#1012636: isync: license conflict with libsasl2

2022-06-10 Thread Bastian Germann
Package: isync Version: 1.4.4-3 Severity: important Hi, isync (mbsync binary) is GPL-2+ licensed and depends on libsasl2-2, which is licensed under CMU's BSD-4-clause license and covered by the RSA-MD and OpenSSL licenses. All of them have an advertisement clause in place, which is known to be