Bug#698527: marked as done (elmer: executable ElmerGUI.real links with both GPL-licensed and GPL-incompatible libraries)
Your message dated Sun, 10 Sep 2017 15:27:35 + with message-id and subject line Bug#870922: Removed package(s) from unstable has caused the Debian Bug report #698527, regarding elmer: executable ElmerGUI.real links with both GPL-licensed and GPL-incompatible libraries 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 ow...@bugs.debian.org immediately.) -- 698527: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698527 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: elmer Version: 6.1.0.svn.5396.dfsg2-1 Severity: serious Justification: Policy 2.3 Hello, this may sound like a revival of bug #618696 [1], but in fact it's distinct (although the evergreen OpenCASCADE GPL-incompatibility is still involved...). [1] http://bugs.debian.org/618696 Let's start from the beginning, anyway. I've recently found out that all libav binary packages in Debian are effectively licensed under the GNU GPL, rather than under the GNU LGPL. This would have been easier to spot, if more clearly documented [2]. [2] http://bugs.debian.org/698019 After this discover, I searched for packages potentially affected by this strong copyleft. I noticed that the binary package named "elmer" depends on some libav packages and I remembered the well-known OpenCASCADE GPL-incompatibility. Hence, I examined all the binaries shipped by the elmer binary package with ldd and I found out that /usr/bin/ElmerGUI.real is linked with the following libraries, among others: libTKSTL.so.2 [...] libTKXSBase.so.2 => OCE (OpenCASCADE Community Edition) License: OCTPL GPL-incompatible libmysqlclient.so.18 => MySQL client library License: GPL-2+ with FOSS exception (which does not allow linking with OCTPL-licensed works...) libavformat.so.53 => libavformat Effective license: GPL-3+ libavcodec.so.53 => libavcodec Effective license: GPL-2+ or libavcodec-extra Effective license: GPL-3+ libavutil.so.51 => libavutil Effective license: GPL-2+ libswscale.so.2 => libswscale Effective license: GPL-2+ (for further details, see the already mentioned bug #698019 [2], especially its message #27 [3]) [3] http://bugs.debian.org/698019#27 libcrypto.so.1.0.0 libssl.so.1.0.0 => OpenSSL License: OpenSSL license (which is GPL-incompatible!) libjbig.so.0 => JBIG-KIT library License: GPL-2+ libxvidcore.so.4 => Xvid library License: GPL-2+ libx264.so.123 => x264 library License: GPL-2+ (unless used solely through avisynth_c.h interfaces) libmp3lame.so.0 => LAME library License: GPL-2+ (since it apparently includes GPL-licensed files) So, in summary, it seems to me that this binary is linked with a number of GPL-licensed libraries, and with two GPL-incompatible libraries (OpenCASCADE Community Edition and OpenSSL). Once again, the possible solutions I can think of, in descending order of desirability, are: (A) Open CASCADE S.A.S. should be contacted and persuaded to re-license Open CASCADE Technology under GPLv2-and-v3-compatible terms; OpenSSL should be replaced by GnuTLS or disabled. (B) OpenCASCADE Community Edition should be substituted with a GPLv2-and-v3-compatible replacement, if any is available; OpenSSL should be replaced by GnuTLS or disabled. (C) All the GPL-licensed libraries should be substituted with non-strong-copyleft replacements or disabled. As usual, if anyone is willing to contribute to the persuasion effort I am carrying on to convince Open CASCADE S.A.S. to switch to the GNU LGPL v2.1, his/her help will be more than appreciated by me! As explained in bug #617613 [4], I have been trying hard to achieve this result since April 2009... [4] http://bugs.debian.org/617613 Thanks for any help you can provide. P.S.: the binary package named "libelmersolver-6.1" probably needs a similar audit --- End Message --- --- Begin Message --- Version: 6.1.0.svn.5396.dfsg2-4+rm Dear submitter, as the package elmerfem has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/870922 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#698527: marked as done (elmer: executable ElmerGUI.real links with both GPL-licensed and GPL-incompatible libraries)
Your message dated Sat, 15 Oct 2016 19:54:28 +0300 with message-id <20161015165428.wyomoqygfuuvl...@bunk.spdns.de> and subject line Already fixed in oldstable has caused the Debian Bug report #698527, regarding elmer: executable ElmerGUI.real links with both GPL-licensed and GPL-incompatible libraries 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 ow...@bugs.debian.org immediately.) -- 698527: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698527 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: elmer Version: 6.1.0.svn.5396.dfsg2-1 Severity: serious Justification: Policy 2.3 Hello, this may sound like a revival of bug #618696 [1], but in fact it's distinct (although the evergreen OpenCASCADE GPL-incompatibility is still involved...). [1] http://bugs.debian.org/618696 Let's start from the beginning, anyway. I've recently found out that all libav binary packages in Debian are effectively licensed under the GNU GPL, rather than under the GNU LGPL. This would have been easier to spot, if more clearly documented [2]. [2] http://bugs.debian.org/698019 After this discover, I searched for packages potentially affected by this strong copyleft. I noticed that the binary package named "elmer" depends on some libav packages and I remembered the well-known OpenCASCADE GPL-incompatibility. Hence, I examined all the binaries shipped by the elmer binary package with ldd and I found out that /usr/bin/ElmerGUI.real is linked with the following libraries, among others: libTKSTL.so.2 [...] libTKXSBase.so.2 => OCE (OpenCASCADE Community Edition) License: OCTPL GPL-incompatible libmysqlclient.so.18 => MySQL client library License: GPL-2+ with FOSS exception (which does not allow linking with OCTPL-licensed works...) libavformat.so.53 => libavformat Effective license: GPL-3+ libavcodec.so.53 => libavcodec Effective license: GPL-2+ or libavcodec-extra Effective license: GPL-3+ libavutil.so.51 => libavutil Effective license: GPL-2+ libswscale.so.2 => libswscale Effective license: GPL-2+ (for further details, see the already mentioned bug #698019 [2], especially its message #27 [3]) [3] http://bugs.debian.org/698019#27 libcrypto.so.1.0.0 libssl.so.1.0.0 => OpenSSL License: OpenSSL license (which is GPL-incompatible!) libjbig.so.0 => JBIG-KIT library License: GPL-2+ libxvidcore.so.4 => Xvid library License: GPL-2+ libx264.so.123 => x264 library License: GPL-2+ (unless used solely through avisynth_c.h interfaces) libmp3lame.so.0 => LAME library License: GPL-2+ (since it apparently includes GPL-licensed files) So, in summary, it seems to me that this binary is linked with a number of GPL-licensed libraries, and with two GPL-incompatible libraries (OpenCASCADE Community Edition and OpenSSL). Once again, the possible solutions I can think of, in descending order of desirability, are: (A) Open CASCADE S.A.S. should be contacted and persuaded to re-license Open CASCADE Technology under GPLv2-and-v3-compatible terms; OpenSSL should be replaced by GnuTLS or disabled. (B) OpenCASCADE Community Edition should be substituted with a GPLv2-and-v3-compatible replacement, if any is available; OpenSSL should be replaced by GnuTLS or disabled. (C) All the GPL-licensed libraries should be substituted with non-strong-copyleft replacements or disabled. As usual, if anyone is willing to contribute to the persuasion effort I am carrying on to convince Open CASCADE S.A.S. to switch to the GNU LGPL v2.1, his/her help will be more than appreciated by me! As explained in bug #617613 [4], I have been trying hard to achieve this result since April 2009... [4] http://bugs.debian.org/617613 Thanks for any help you can provide. P.S.: the binary package named "libelmersolver-6.1" probably needs a similar audit --- End Message --- --- Begin Message --- I am closing this bug since it is already fixed in oldstable. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed--- End Message ---
Bug#698527: marked as done (elmer: executable ElmerGUI.real links with both GPL-licensed and GPL-incompatible libraries)
Your message dated Thu, 28 Feb 2013 21:32:44 + with message-id and subject line Bug#698527: fixed in elmerfem 6.1.0.svn.5396.dfsg2-2 has caused the Debian Bug report #698527, regarding elmer: executable ElmerGUI.real links with both GPL-licensed and GPL-incompatible libraries 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 ow...@bugs.debian.org immediately.) -- 698527: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698527 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: elmer Version: 6.1.0.svn.5396.dfsg2-1 Severity: serious Justification: Policy 2.3 Hello, this may sound like a revival of bug #618696 [1], but in fact it's distinct (although the evergreen OpenCASCADE GPL-incompatibility is still involved...). [1] http://bugs.debian.org/618696 Let's start from the beginning, anyway. I've recently found out that all libav binary packages in Debian are effectively licensed under the GNU GPL, rather than under the GNU LGPL. This would have been easier to spot, if more clearly documented [2]. [2] http://bugs.debian.org/698019 After this discover, I searched for packages potentially affected by this strong copyleft. I noticed that the binary package named "elmer" depends on some libav packages and I remembered the well-known OpenCASCADE GPL-incompatibility. Hence, I examined all the binaries shipped by the elmer binary package with ldd and I found out that /usr/bin/ElmerGUI.real is linked with the following libraries, among others: libTKSTL.so.2 [...] libTKXSBase.so.2 => OCE (OpenCASCADE Community Edition) License: OCTPL GPL-incompatible libmysqlclient.so.18 => MySQL client library License: GPL-2+ with FOSS exception (which does not allow linking with OCTPL-licensed works...) libavformat.so.53 => libavformat Effective license: GPL-3+ libavcodec.so.53 => libavcodec Effective license: GPL-2+ or libavcodec-extra Effective license: GPL-3+ libavutil.so.51 => libavutil Effective license: GPL-2+ libswscale.so.2 => libswscale Effective license: GPL-2+ (for further details, see the already mentioned bug #698019 [2], especially its message #27 [3]) [3] http://bugs.debian.org/698019#27 libcrypto.so.1.0.0 libssl.so.1.0.0 => OpenSSL License: OpenSSL license (which is GPL-incompatible!) libjbig.so.0 => JBIG-KIT library License: GPL-2+ libxvidcore.so.4 => Xvid library License: GPL-2+ libx264.so.123 => x264 library License: GPL-2+ (unless used solely through avisynth_c.h interfaces) libmp3lame.so.0 => LAME library License: GPL-2+ (since it apparently includes GPL-licensed files) So, in summary, it seems to me that this binary is linked with a number of GPL-licensed libraries, and with two GPL-incompatible libraries (OpenCASCADE Community Edition and OpenSSL). Once again, the possible solutions I can think of, in descending order of desirability, are: (A) Open CASCADE S.A.S. should be contacted and persuaded to re-license Open CASCADE Technology under GPLv2-and-v3-compatible terms; OpenSSL should be replaced by GnuTLS or disabled. (B) OpenCASCADE Community Edition should be substituted with a GPLv2-and-v3-compatible replacement, if any is available; OpenSSL should be replaced by GnuTLS or disabled. (C) All the GPL-licensed libraries should be substituted with non-strong-copyleft replacements or disabled. As usual, if anyone is willing to contribute to the persuasion effort I am carrying on to convince Open CASCADE S.A.S. to switch to the GNU LGPL v2.1, his/her help will be more than appreciated by me! As explained in bug #617613 [4], I have been trying hard to achieve this result since April 2009... [4] http://bugs.debian.org/617613 Thanks for any help you can provide. P.S.: the binary package named "libelmersolver-6.1" probably needs a similar audit --- End Message --- --- Begin Message --- Source: elmerfem Source-Version: 6.1.0.svn.5396.dfsg2-2 We believe that the bug you reported is fixed in the latest version of elmerfem, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 698...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boris Pek (supplier of updated elmerfem package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators
