public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Bastian Germann <bastiangermann@fishpost.de>
To: "Darrick J. Wong" <djwong@kernel.org>, 979653@bugs.debian.org
Cc: Eric Sandeen <sandeen@sandeen.net>
Subject: Bug#979653: xfsprogs: Incomplete debian/copyright
Date: Tue, 12 Jan 2021 19:19:16 +0100	[thread overview]
Message-ID: <24ece48a-f8e5-e350-d30d-8d6116edd9be@fishpost.de> (raw)
In-Reply-To: <20210112174644.GR1164246@magnolia>

Am 12.01.21 um 18:46 schrieb Darrick J. Wong:
> On Sun, Jan 10, 2021 at 01:23:58AM +0100, Bastian Germann wrote:
>> Files: *
>> Copyright:
>>   1995-2013 Silicon Graphics, Inc.
>>   2010-2018 Red Hat, Inc.
>>   2016-2020 Oracle.  All Rights Reserved.
> 
> /me notes that a lot of the Oracle-copyright files are actually GPL-2+,
> not GPL-2.  That might not be obvious because I bungled some of the SPDX
> tags when spdx deprecated the "GPL-2.0+" tag and we had to replace them
> all with "GPL-2.0-or-later", though it looks like they've all been
> cleaned up at this point.

Yes, I have noticed that there are some GPL-2.0-or-later and GPL-2.0+ 
licensed files. Simplifying them as GPL-2.0-only in debian/copyright 
does not harm in my opinion as the whole work including the GPL-2.0-only 
files is not usable under GPL-2.0-or-later. And someone who is 
interested in using specific files would look at their individual SPDX 
lines anyway.

> 
> Question: How can we autogenerate debian/copyright from the source files
> in the git repo?  In the long run I think it best that this becomes
> something we can automate when tagging a new upstream release.

I do not know of any SPDX to DEP-5 converter. Implementing a generic 
converter would be beneficial to more projects but is a bigger task. The 
need for it is mentioned at https://wiki.debian.org/SPDX.
Just writing a converter for xfsprogs would be doable easily from what I 
have seen.

  reply	other threads:[~2021-01-12 18:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1l1zPx-0005hZ-D4@fasolo.debian.org>
     [not found] ` <90d12c70-6679-85aa-b835-e2db9d1eb441@fishpost.de>
2021-01-09 20:42   ` Bug#979653: xfsprogs: Incomplete debian/copyright Bastian Germann
2021-01-09 22:53     ` Eric Sandeen
2021-01-10  0:23       ` Bastian Germann
2021-01-12 17:46         ` Darrick J. Wong
2021-01-12 18:19           ` Bastian Germann [this message]
2021-01-19 22:27   ` Bug#979653: marked as done (xfsprogs: Incomplete debian/copyright) Debian Bug Tracking System

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=24ece48a-f8e5-e350-d30d-8d6116edd9be@fishpost.de \
    --to=bastiangermann@fishpost.de \
    --cc=979653@bugs.debian.org \
    --cc=djwong@kernel.org \
    --cc=sandeen@sandeen.net \
    /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