Bug#1034358: libvncclient1: license conflict with libsasl2

2023-08-01 Thread Bastian Germann
Control: severity -1 important The RSA-MD license is gone from cyrus-sasl's binaries now, so derivative works can ignore it. For BSD-3-Clause-Attribution, the incompatibility case is not as strong, so I am lowering the severity.

Bug#1034358: libvncclient1: license conflict with libsasl2

2023-05-21 Thread Bastian Germann
Am 21.05.23 um 21:48 schrieb Mike Gabriel: Let me know if this works for you that this gets fixed only for trixie. As nobody cared about it in the past: sure.

Bug#1034358: libvncclient1: license conflict with libsasl2

2023-05-21 Thread Mike Gabriel
Control: forwarded -1 https://github.com/LibVNC/libvncserver/issues/583 Control: tag -1 bookworm-ignore Hi Bastian, On Do 13 Apr 2023 15:42:59 CEST, Bastian Germann wrote: Package: libvncclient1 Version: 0.9.14+dfsg-1 Severity: serious Hi, libvncclient1 depends on libsasl2-2, which is lice

Bug#1034358: libvncclient1: license conflict with libsasl2

2023-04-13 Thread Bastian Germann
Package: libvncclient1 Version: 0.9.14+dfsg-1 Severity: serious Hi, libvncclient1 depends 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 (libvncclient1's lic