GNU bug report logs -
#30836
[PATCH 2/3] guix import elpa: use #f for license
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 30836 in the body.
You can then email your comments to 30836 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
guix-patches <at> gnu.org
:
bug#30836
; Package
guix-patches
.
(Fri, 16 Mar 2018 13:59:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Konrad Hinsen <konrad.hinsen <at> fastmail.net>
:
New bug report received and forwarded. Copy sent to
guix-patches <at> gnu.org
.
(Fri, 16 Mar 2018 13:59:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Elpa doesn't supply license information. The current importer pretends that
everything is GPL3, which is not true. The importer should not invent license
information.
---
guix/import/elpa.scm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/guix/import/elpa.scm b/guix/import/elpa.scm
index 7f76a13ad..cae10eb1c 100644
--- a/guix/import/elpa.scm
+++ b/guix/import/elpa.scm
@@ -234,7 +234,7 @@ type '<elpa-package>'."
(home-page ,(elpa-package-home-page pkg))
(synopsis ,(elpa-package-synopsis pkg))
(description ,(elpa-package-description pkg))
- (license license:gpl3+))))
+ (license #f))))
(define* (elpa->guix-package name #:optional (repo 'gnu))
"Fetch the package NAME from REPO and produce a Guix package S-expression."
--
2.16.2
Information forwarded
to
guix-patches <at> gnu.org
:
bug#30836
; Package
guix-patches
.
(Sat, 17 Mar 2018 21:30:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 30836 <at> debbugs.gnu.org (full text, mbox):
Konrad Hinsen <konrad.hinsen <at> fastmail.net> skribis:
> Elpa doesn't supply license information. The current importer pretends that
> everything is GPL3, which is not true. The importer should not invent license
> information.
Do you have examples of packages on ELPA that are not GPLv3+? I don’t
know if this is the case, but I wouldn’t be surprised if it had a policy
of requiring GPLv3+ given that Emacs itself is GPLv3+.
Thanks,
Ludo’.
Information forwarded
to
guix-patches <at> gnu.org
:
bug#30836
; Package
guix-patches
.
(Sun, 18 Mar 2018 05:13:01 GMT)
Full text and
rfc822 format available.
Message #11 received at 30836 <at> debbugs.gnu.org (full text, mbox):
Ludovic Courtès <ludo <at> gnu.org> writes:
> Konrad Hinsen <konrad.hinsen <at> fastmail.net> skribis:
>
>> Elpa doesn't supply license information. The current importer pretends that
>> everything is GPL3, which is not true. The importer should not invent license
>> information.
>
> Do you have examples of packages on ELPA that are not GPLv3+? I don’t
> know if this is the case, but I wouldn’t be surprised if it had a policy
> of requiring GPLv3+ given that Emacs itself is GPLv3+.
My understanding is that anyone who contributes a non-trivial patch to
an ELPA package must assign copyright to the FSF, so I'd guess an ELPA
package is GPLv3+ by definition.
--
Kyle
Information forwarded
to
guix-patches <at> gnu.org
:
bug#30836
; Package
guix-patches
.
(Sun, 18 Mar 2018 08:28:02 GMT)
Full text and
rfc822 format available.
Message #14 received at 30836 <at> debbugs.gnu.org (full text, mbox):
ludo <at> gnu.org (Ludovic Courtès) writes:
> Konrad Hinsen <konrad.hinsen <at> fastmail.net> skribis:
>
>> Elpa doesn't supply license information. The current importer pretends that
>> everything is GPL3, which is not true. The importer should not invent license
>> information.
>
> Do you have examples of packages on ELPA that are not GPLv3+? I don’t
> know if this is the case, but I wouldn’t be surprised if it had a policy
> of requiring GPLv3+ given that Emacs itself is GPLv3+.
The ELPA importer is also used for MELPA, which has no license
requirements. The package that motivated this patch is Deft, which is
MIT-licensed:
https://jblevins.org/projects/deft/
If GNU ELPA guarantees GPL3, we could keep the old behavior for that
but use #f for MELPA and stable MELPA.
Konrad.
Reply sent
to
ludo <at> gnu.org (Ludovic Courtès)
:
You have taken responsibility.
(Sun, 18 Mar 2018 22:26:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Konrad Hinsen <konrad.hinsen <at> fastmail.net>
:
bug acknowledged by developer.
(Sun, 18 Mar 2018 22:26:02 GMT)
Full text and
rfc822 format available.
Message #19 received at 30836-done <at> debbugs.gnu.org (full text, mbox):
Konrad Hinsen <konrad.hinsen <at> fastmail.net> skribis:
> ludo <at> gnu.org (Ludovic Courtès) writes:
>
>> Konrad Hinsen <konrad.hinsen <at> fastmail.net> skribis:
>>
>>> Elpa doesn't supply license information. The current importer pretends that
>>> everything is GPL3, which is not true. The importer should not invent license
>>> information.
>>
>> Do you have examples of packages on ELPA that are not GPLv3+? I don’t
>> know if this is the case, but I wouldn’t be surprised if it had a policy
>> of requiring GPLv3+ given that Emacs itself is GPLv3+.
>
> The ELPA importer is also used for MELPA, which has no license
> requirements. The package that motivated this patch is Deft, which is
> MIT-licensed:
>
> https://jblevins.org/projects/deft/
>
> If GNU ELPA guarantees GPL3, we could keep the old behavior for that
> but use #f for MELPA and stable MELPA.
Good idea. Commit 9bb1838c3f982dfb84ba24eb2f727cb39ee5805c does that.
Thanks!
Ludo’.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Mon, 16 Apr 2018 11:24:04 GMT)
Full text and
rfc822 format available.
This bug report was last modified 6 years and 5 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.