unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Max Horn <max@quendi.de>
Cc: 42759@debbugs.gnu.org, "Jakub Kądziołka" <kuba@kadziolka.net>
Subject: bug#42759: Flint license is wrong
Date: Sat, 08 Aug 2020 21:09:05 +0200	[thread overview]
Message-ID: <87tuxdc5v2.fsf@nckx> (raw)
In-Reply-To: <2EA056B4-B4E9-4260-9B70-134A4209A574@quendi.de>

[-- Attachment #1: Type: text/plain, Size: 836 bytes --]

Max,

Max Horn 写道：
> What, that the license is lgpl2.1+ ?

Yes.

> That's what the website states (right at the top of the front 
> page), along with an explanation that the license changed from 
> 2.5 to 2.6. It is also what the README and the LICENSE files 
> state.

I'm aware.  That's why I considered it implausible that...

> whoever updated the package from 2.5.2 to 2.6.0 did not pay 
> attention and missed the license change.

Of course only Jakub (CC'd) can know for sure.  :-)

I opened an issue[0] upstream earlier today but no reply yet.  If 
these GPL2+ headers are meaningful *in any jurisdiction*, we 
*can't* claim that our FLINT is LGPL2+.  Nor can upstream.

I was unable to build FLINT without these files.

Kind regards,

T G-R

[0]: https://github.com/wbhart/flint2/issues/812

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  reply	other threads:[~2020-08-08 19:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-08 10:42 bug#42759: Flint license is wrong Max Horn
2020-08-08 14:56 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-08-08 15:23   ` Max Horn
2020-08-08 19:09     ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
2020-08-08 19:12       ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-08-15 20:11 ` bug#42759: Flint licence updated Tobias Geerinckx-Rice via Bug reports for GNU Guix

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87tuxdc5v2.fsf@nckx \
    --to=bug-guix@gnu.org \
    --cc=42759@debbugs.gnu.org \
    --cc=kuba@kadziolka.net \
    --cc=max@quendi.de \
    --cc=me@tobias.gr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).