From: Jon Turney <jon.turney@dronecode.org.uk>
To: Takashi Yano <takashi.yano@nifty.ne.jp>,
"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: [ITA] mpg123 (1.31.1)
Date: Sat, 21 Jan 2023 14:58:46 +0000 [thread overview]
Message-ID: <bb057599-d456-8807-1b34-545d63625a37@dronecode.org.uk> (raw)
In-Reply-To: <20230120193455.aca3b334adb90601451027bb@nifty.ne.jp>
On 20/01/2023 10:34, Takashi Yano via Cygwin-apps wrote:
> I would like to take over the maintenance of mpg123
> package which is currently orphanded. I have already
> prepared the updated package at:
>
> https://tyan0.yr32.net/cygwin/x86_64/release/mpg123/
Looks good, apart from:
LICENSE="LGPL v2.1"
The contents of LICENSE is expected to be a valid SPDX license
expression, which I don't think this is. Perhaps "LGPL-2.1-only" [2]
[1] https://cygwin.github.io/cygport/pkg_info_cygpart.html#LICENSE
[2] https://spdx.org/licenses/
next prev parent reply other threads:[~2023-01-21 14:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 10:34 Takashi Yano
2023-01-21 14:58 ` Jon Turney [this message]
2023-01-22 12:23 ` Takashi Yano
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bb057599-d456-8807-1b34-545d63625a37@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@cygwin.com \
--cc=takashi.yano@nifty.ne.jp \
/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).