From: Ricardo Wurmus <rekado@elephly.net>
To: zimon.toutoune@gmail.com
Cc: 36797@debbugs.gnu.org
Subject: [bug#36797] [PATCH 08/11] gnu: Add r-flowpeaks.
Date: Wed, 24 Jul 2019 22:51:04 +0200 [thread overview]
Message-ID: <87tvbb9mx3.fsf@elephly.net> (raw)
In-Reply-To: <20190724182204.6818-9-zimon.toutoune@gmail.com>
zimoun <zimon.toutoune@gmail.com> writes:
> * gnu/packages/bioconductor.scm (r-flowpeaks): New variable.
[…]
> + (license license:artistic2.0))) ;TODO: artistic1.0 does not exist
Unfortunately, version 1.0 of the Artistic License is too unclear to be
considered a free license. I have excluded this package from the
set of patches that I’ll apply to the master branch.
--
Ricardo
next prev parent reply other threads:[~2019-07-24 20:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 18:21 [bug#36789] [PATCH 00/11] Add r packages to process flow cytometry data zimoun
2019-07-24 18:21 ` [bug#36790] [PATCH 01/11] gnu: Add r-umap zimoun
2019-07-24 19:17 ` [bug#36790] Merge 36789 36790 zimoun
2019-07-24 18:21 ` [bug#36791] [PATCH 02/11] gnu: Add r-kableextra zimoun
2019-07-24 18:21 ` [bug#36792] [PATCH 03/11] gnu: Add r-all zimoun
2019-07-24 18:21 ` [bug#36793] [PATCH 04/11] gnu: Add r-flowcore zimoun
2019-07-24 18:21 ` [bug#36794] [PATCH 05/11] gnu: Add r-flowutils zimoun
2019-07-24 18:21 ` [bug#36795] [PATCH 06/11] gnu: Add r-consensusclusterplus zimoun
2019-07-24 18:22 ` [bug#36796] [PATCH 07/11] gnu: Add r-flowmeans zimoun
2019-07-24 18:22 ` [bug#36797] [PATCH 08/11] gnu: Add r-flowpeaks zimoun
2019-07-24 20:51 ` Ricardo Wurmus [this message]
2020-02-21 17:07 ` bug#36797: patches merged zimoun
2019-07-24 18:22 ` [bug#36798] [PATCH 09/11] gnu: Add r-flowsom zimoun
2019-07-24 18:22 ` [bug#36799] [PATCH 10/11] gnu: Add r-mixomics zimoun
2019-07-24 18:22 ` [bug#36800] [PATCH 11/11] gnu: Add r-depecher zimoun
2019-07-24 20:49 ` Ricardo Wurmus
2019-07-25 9:54 ` zimoun
2019-07-25 12:45 ` Ricardo Wurmus
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=87tvbb9mx3.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=36797@debbugs.gnu.org \
--cc=zimon.toutoune@gmail.com \
/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).