From: Eric Wong <normalperson@yhbt.net>
To: hsbt@ruby-lang.org
Cc: ruby-core@ruby-lang.org
Subject: [ruby-core:70843] Re: [ruby-cvs:58952] hsbt:r51801 (trunk): * lib/rubygems: Update to RubyGems HEAD(fe61e4c112).
Date: Thu, 17 Sep 2015 18:46:33 +0000 [thread overview]
Message-ID: <20150917184633.GA15031@dcvr.yhbt.net> (raw)
In-Reply-To: <20150908224644.7A6C52400C@fluorine.ruby-lang.org>
hsbt@ruby-lang.org wrote:
> * lib/rubygems: Update to RubyGems HEAD(fe61e4c112).
> this version contains new feature that warn invalid SPDX license
RubyGems does not accept '+' suffix as allowed by
http://spdx.org/licenses for "or later" clause.
With "GPL-2.0+", I get:
WARNING: WARNING: license value 'GPL-2.0+' is invalid. Use a license
identifier from
http://spdx.org/licenses or 'Nonstandard' for a nonstandard license.
I'm not touching a proprietary bug report interface,
so forwarding this to upstream would be appreciated.
Thanks.
Side note:
I also have software under the old Ruby (<= 1.9.2)
license (with GPL option) which matches the text in
http://spdx.org/licenses/Ruby.html#licenseText
But the link on that spdx.org page also points to
http://www.ruby-lang.org/en/LICENSE.txt and that is
points to the new BSD-2-Clause (which I cannot
relicense my project to). So I'm a little nervous
about declaring "Ruby" as a license option in the
gemspec nowadays.
next parent reply other threads:[~2015-09-17 18:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150908224644.7A6C52400C@fluorine.ruby-lang.org>
2015-09-17 18:46 ` Eric Wong [this message]
2015-11-16 7:57 ` [ruby-core:71502] Re: [ruby-cvs:58952] hsbt:r51801 (trunk): * lib/rubygems: Update to RubyGems HEAD(fe61e4c112) SHIBATA Hiroshi
2015-11-20 2:31 ` [ruby-core:71597] " Eric Wong
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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150917184633.GA15031@dcvr.yhbt.net \
--to=ruby-core@ruby-lang.org \
--cc=hsbt@ruby-lang.org \
/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.
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).