all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Dave Love <fx@gnu.org>
Cc: 28946-done@debbugs.gnu.org
Subject: bug#28946: licence problem with cufflinks
Date: Tue, 31 Oct 2017 08:19:10 +0100	[thread overview]
Message-ID: <8760avlr81.fsf@elephly.net> (raw)
In-Reply-To: <87zi8ghnhl.fsf@albion.it.manchester.ac.uk>


Dave Love <fx@gnu.org> writes:

> Ricardo Wurmus <rekado@elephly.net> writes:
>
>> Ricardo Wurmus <rekado@elephly.net> writes:
>>
>>> Hi Dave,
>>>
>>>> I noticed that there's a package for cufflinks, but it has a non-free
>>>> component.  It isn't packaged for Debian or Fedora because of that.  See
>>>> <https://github.com/cole-trapnell-lab/cufflinks/issues/16>.
>>>
>>> Thank you for the information! I’m going to investigate this.
>> […]
>>
>> I have written email to coletrap@uw.edu to report my findings and ask
>> about details.
>
> Sorry, I could probably have saved you effort.  I think I already mailed
> before cufflinks moved to github, and I also tried to track down the
> author of the problematic component, though they probably wouldn't hold
> the copyright as far as I remember..

I have not received any response; neither to the bug report, nor to the
email I sent.  I have removed cufflinks from Guix with commit 7bf59f702.

Thanks again for the report!

So… I’ll try to see if I can adapt the GPL code from r-locfit in a fork
of Cufflinks at some point.

--
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

      reply	other threads:[~2017-10-31  9:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-22 16:52 bug#28946: licence problem with cufflinks Dave Love
2017-10-22 21:39 ` Ricardo Wurmus
2017-10-24  7:10   ` Ricardo Wurmus
2017-10-24 10:03     ` Dave Love
2017-10-31  7:19       ` Ricardo Wurmus [this message]

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=8760avlr81.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=28946-done@debbugs.gnu.org \
    --cc=fx@gnu.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.
Code repositories for project(s) associated with this external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.