Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9751] New: expat legal info - manifest.csv: GPLv2 Source site: MIT License (Buildroot 2017-02)
Date: Sat, 18 Mar 2017 08:32:07 +0000	[thread overview]
Message-ID: <bug-9751-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=9751

            Bug ID: 9751
           Summary: expat legal info - manifest.csv: GPLv2 Source site:
                    MIT License (Buildroot 2017-02)
           Product: buildroot
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: timo.valimaki at sensoan.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

I started to make legal check to my Buildroot build - first time.

NAME=Buildroot
VERSION=2017.02
ID=buildroot
VERSION_ID=2017.02
PRETTY_NAME="Buildroot 2017.02"

When I checked Licenses listed in the manifest.csv file and then compared what
is said on actual source site I found differences.

E.g. package: expat - Manifest indicates GPLv2 but source site
(https://sourceforge.net/projects/expat/?source=navbar) indicates MIT License.

Is this due to a bug in expat package license info or something else?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2017-03-18  8:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-18  8:32 bugzilla at busybox.net [this message]
2017-03-18 12:59 ` [Buildroot] [Bug 9751] expat legal info - manifest.csv: GPLv2 Source site: MIT License (Buildroot 2017-02) bugzilla at busybox.net
2017-03-18 13:14 ` bugzilla at busybox.net

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=bug-9751-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.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