From: Roland Hieber <r.hieber@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Roland Hieber <r.hieber@pengutronix.de>
Subject: [ptxdist] [PATCH 5/5] qpdf: correct license and pin down license MD5sum
Date: Thu, 23 Nov 2017 11:04:54 +0100 [thread overview]
Message-ID: <20171123100454.27836-5-r.hieber@pengutronix.de> (raw)
In-Reply-To: <20171123100454.27836-1-r.hieber@pengutronix.de>
A quick glance at QPDF's LICENSE.txt shows that it identifies itself at
the Apache 2.0 license, not the Artistic license.
Signed-off-by: Roland Hieber <r.hieber@pengutronix.de>
---
rules/qpdf.make | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/rules/qpdf.make b/rules/qpdf.make
index eecfe4b39..5995f22b2 100644
--- a/rules/qpdf.make
+++ b/rules/qpdf.make
@@ -23,7 +23,8 @@ QPDF_SUFFIX := tar.gz
QPDF_URL := $(call ptx/mirror, SF, /qpdf/qpdf/$(QPDF_VERSION)/$(QPDF).$(QPDF_SUFFIX))
QPDF_SOURCE := $(SRCDIR)/$(QPDF).$(QPDF_SUFFIX)
QPDF_DIR := $(BUILDDIR)/$(QPDF)
-QPDF_LICENSE := Artistic-2.0
+QPDF_LICENSE := Apache-2.0
+QPDF_LICENSE_FILES := file://LICENSE.txt;md5=3b83ef96387f14655fc854ddc3c6bd57
# ----------------------------------------------------------------------------
# Prepare
--
2.11.0
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2017-11-23 10:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-23 10:04 [ptxdist] [PATCH 1/5] nginx: " Roland Hieber
2017-11-23 10:04 ` [ptxdist] [PATCH 2/5] cups-filters: " Roland Hieber
2017-11-23 13:36 ` [ptxdist] [PATCH v2 2/6] " Roland Hieber
2017-11-23 10:04 ` [ptxdist] [PATCH 3/5] cups: " Roland Hieber
2017-11-23 10:04 ` [ptxdist] [PATCH 4/5] libpaper: " Roland Hieber
2017-11-23 10:04 ` Roland Hieber [this message]
2017-11-23 10:27 ` [ptxdist] [PATCH 6/5] poppler-data: " Roland Hieber
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=20171123100454.27836-5-r.hieber@pengutronix.de \
--to=r.hieber@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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