<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<blockquote type="cite" cite="mid:alroErDPzObvqS3j@ebb.org">
<blockquote type="cite">
<pre wrap="" class="moz-quote-pre">This is a case where the license incompatibility between GPL 3 and
LGPL 2 really bit users in the *ss.
</pre>
</blockquote>
<pre wrap="" class="moz-quote-pre">
Please don't get me started on that. I sent an email to everyone
with authority over the final text of GPLv3 at the end of the GPLv3
process (but before it was released) pointing out that that it was as
disaster that LGPLv2.1-only was incompatible with GPLv3. Nobody
cared except Richard Fontana. See, there's a reason he and I are
here 20 years later as the two working on this project, and everyone
else involved in GPLv3 don't work on copyleft drafting anymore. 😆
</pre>
</blockquote>
<p>I'm not sure I understand this correctly. </p>
<p>Sec. 3 LGPL-2.1 reads as follows:</p>
<p><i>"You may opt to apply the terms of the ordinary GNU General
Public License instead of this License to a given copy of the
Library. To do this, you must alter all the notices that refer
to this License, so that they refer to the ordinary GNU General
Public License, version 2, instead of to this License. (If a
newer version than version 2 of the ordinary GNU General Public
License has appeared, then you can specify that version instead
if you wish.) "</i></p>
<p>Copyright owners using typical license headers as the following
(from libnl)</p>
<p><i>"* This library is <span class="hi-keyword">free software</span>;
<span class="hi-undefined" title="">you can re<span
class="hi-keyword">distribut</span>e it and/or<br>
* modify it under the terms of the GNU Lesser General Public<br>
* <span class="hi-keyword">Licens</span>e</span><span
class="hi-undefined" title=""> as published by the <span
class="hi-keyword">Free Software</span> Foundation version
2.1</span><span class="hi-undefined" title=""><br>
* of the <span class="hi-keyword">Licens</span>e.</span>"</i></p>
<p>try to exclude the permission to "relicense" under the LGPL-3.0
but why should that exclude the permission to relicense under
GPL-2.0 or GPL-3.0?</p>
<p>Accordingly, I do not see a problem to link a GPL-3.0 licensed
application with a LGPL-2.1-only licensed library by using the
whole under GPL-3.0. </p>
<p>Do you mean any other use case?</p>
<p>Best,</p>
<p>Till</p>
</body>
</html>