mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kristian Fiskerstrand <k_f@gentoo.org>
To: Domenico Andreoli <domenico.andreoli@linux.com>,
	Ben Finney <bignose@debian.org>
Cc: Nadia Yvette Chambers <nyc@holomorphy.com>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	919356@bugs.debian.org, debian-legal@lists.debian.org,
	linux-kernel@vger.kernel.org
Subject: Re: Licensing of include/linux/hash.h
Date: Mon, 11 Feb 2019 00:08:32 +0100	[thread overview]
Message-ID: <c3aa1b37-60bb-aceb-10ba-9768157a2a5a@gentoo.org> (raw)
In-Reply-To: <20190123085000.fp7lhtjxcyzw3m4x@dumbo>


[-- Attachment #1.1: Type: text/plain, Size: 3513 bytes --]

On 1/23/19 9:50 AM, Domenico Andreoli wrote:
> Ben Finney <bignose@debian.org> writes:
>> Domenico Andreoli <cavok@debian.org> writes:
>>
>>>   the situation of dwarves-dfsg improved a lot over the weekend
>>
>> That's good to hear. What is the event you're referring to? Can you give
>> a URL to something that describes this change?
> 
> Upstream (in CC) reacted to my request of clarification and patches
> have been applied upstream and on Salsa. See bug 919356 [0] (please
> keep in CC).
> 
>>> the only knot left is now the license of hash.h
>>>
>>> This file is also present in the kernel [0] with an updated copyright
>>> but still without license.
>>
>> The file you show (in the Linux code base) seems likely to have an
>> equivalent implementation under a different license, from some other
>> code base.
> 
> This will require research and work unlikely to be done before Buster
> release. Are we going to drop this package for now?
> 
>>> I received a private email from somebody in the kernel community who
>>> already tried to contact Nadia in the past but did not get any reply.
>>
>> Thank you also for contacting the Linux developers forum to ask
>> <URL:https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1900588.html>.
> 
> (also in CC now)
> 
>>> I think that pushing it to non-free is formally the right thing but I
>>> actually feel it's not the right thing.
>>
>> To know that work (that file) is free software, we need a clear grant of
>> some specific license, for that work.
>>
>> If the work is not free, it would be incorrect to have the work in Debian.
> 
> Is it possible that for the kernel it is instead correct because it is,
> as whole, covered by its COPYING?
> 
>> Alternatives, for complying with the Debian Free Software Guidelines with
>> this package, include:
>>
>> * Find a credible grant of license under some GPL-compatible free
>>   license to that exact file. Document that explicit grant in the Debian
>>   package. This demonstrates the work is DFSG-free.
>>
>> * Convince ‘dwarves-dfsg’ upstream to replace that file with a different
>>   implementation (I don't know whether such an implementation exists)
>>   under a license compatible with the same version of GNU GPL. Document
>>   that explicit grant in the Debian package. This demonstrates the
>>   modified work is DFSG-free.
> 
> Arnaldo, what priority would you give to this task?
> 
>>
>> * Replace that file in Debian only, with a different implementation as
>>   above. Document that explicit grant in the Debian package. This
>>   demonstrates the modified Debian package is DFSG-free.
>>
>> * Move the work to the ‘non-free’ area.
>>
>> * Remove the work altogether.
>>
>> Those are in descending order of (my recommended) preference.
> 
> Thanks,
> Domenico
> 
> [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919356
> 

It was [pointed out] by one of our license group that [hash.h]  is the
same that has a GPL-2+ in [fio] which has a signed-off-by.

References:
[pointed out]
https://bugs.gentoo.org/677586#c1

[hash.h]
https://git.kernel.org/pub/scm/linux/kernel/git/axboe/fio.git/commit/hash.h?id=bdc7211e190482f0c17c109a0d90834a6611be1c

[fio]
https://metadata.ftp-master.debian.org/changelogs/main/f/fio/fio_3.12-2_copyright



-- 
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2019-02-10 23:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-15 17:00 Domenico Andreoli
2019-01-23  8:50 ` Domenico Andreoli
2019-02-10 23:08   ` Kristian Fiskerstrand [this message]
2019-02-11  7:22     ` Domenico Andreoli
2019-02-11 12:43       ` Ulrich Mueller
2019-02-11 14:51         ` Ulrich Mueller
     [not found]       ` <2977287.v5rPGuGa1n@merkaba>
2019-02-11 22:55         ` Jens Axboe
2019-02-12  6:26         ` Bug#919356: " Ben Finney
2019-02-12  6:27         ` Ben Finney
2019-02-12  6:27         ` Ben Finney
2019-02-12 16:16           ` Jens Axboe
2019-02-12 17:16             ` [PATCH] Add the SPDX header to include/linux/hash.h Domenico Andreoli
2019-02-12 20:34             ` Bug#919356: Licensing of include/linux/hash.h Martin Steigerwald
2019-02-12 22:08             ` Ben Finney
2019-02-12 20:36           ` Martin Steigerwald

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=c3aa1b37-60bb-aceb-10ba-9768157a2a5a@gentoo.org \
    --to=k_f@gentoo.org \
    --cc=919356@bugs.debian.org \
    --cc=acme@redhat.com \
    --cc=bignose@debian.org \
    --cc=debian-legal@lists.debian.org \
    --cc=domenico.andreoli@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nyc@holomorphy.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®