From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Love Subject: bug#28946: licence problem with cufflinks Date: Tue, 24 Oct 2017 11:03:02 +0100 Message-ID: <87zi8ghnhl.fsf@albion.it.manchester.ac.uk> References: <87y3o3i0px.fsf@albion.it.manchester.ac.uk> <87sheauakg.fsf@elephly.net> <87wp3lc96s.fsf@mdc-berlin.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:40771) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e6w4A-00015K-Ff for bug-guix@gnu.org; Tue, 24 Oct 2017 06:04:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1e6w42-0005qW-Po for bug-guix@gnu.org; Tue, 24 Oct 2017 06:04:10 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:49704) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1e6w42-0005qI-Lx for bug-guix@gnu.org; Tue, 24 Oct 2017 06:04:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1e6w42-0004NS-8P for bug-guix@gnu.org; Tue, 24 Oct 2017 06:04:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87wp3lc96s.fsf@mdc-berlin.de> (Ricardo Wurmus's message of "Tue, 24 Oct 2017 09:10:51 +0200") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Ricardo Wurmus Cc: 28946@debbugs.gnu.org Ricardo Wurmus writes: > Ricardo Wurmus 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 >>> . >> >> Thank you for the information! I=E2=80=99m going to investigate this. > [=E2=80=A6] > > 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..