From: Asaf Kahlon <asafka7@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] python-lxml: bump to version 4.2.5
Date: Fri, 21 Sep 2018 12:59:48 +0300 [thread overview]
Message-ID: <20180921095948.964-1-asafka7@gmail.com> (raw)
Also add hashes for license files.
Signed-off-by: Asaf Kahlon <asafka7@gmail.com>
---
package/python-lxml/python-lxml.hash | 6 +++++-
package/python-lxml/python-lxml.mk | 2 +-
2 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/package/python-lxml/python-lxml.hash b/package/python-lxml/python-lxml.hash
index 9b75a26280..610c0d6db4 100644
--- a/package/python-lxml/python-lxml.hash
+++ b/package/python-lxml/python-lxml.hash
@@ -1,2 +1,6 @@
# Locally computed
-sha256 e2afbe403090f5893e254958d02875e0732975e73c4c0cdd33c1f009a61963ca lxml-4.2.4.tgz
+sha256 36720698c29e7a9626a0dc802ef8885f8f0239bfd1689628ecd459a061f2807f lxml-4.2.5.tgz
+sha256 41d49dd406aa0e1548a6d5f21a30d6bf638b3cd96eb7289dd348d83ed2e40392 LICENSES.txt
+sha256 69edb445c1335a8312d4c09271847e9956d84f0d9f724d125340cc3fad767b2a doc/licenses/BSD.txt
+sha256 0497ae8138811ef4466ede653bab7a59feb3d3c14f9ed50fc33a00aeb5bec32e doc/licenses/elementtree.txt
+sha256 705bdfece6dbb87879d9ec40a8c9530651aefb98ae387da9134584464742d539 src/lxml/isoschematron/resources/rng/iso-schematron.rng
diff --git a/package/python-lxml/python-lxml.mk b/package/python-lxml/python-lxml.mk
index 80c04c0055..61f81e6363 100644
--- a/package/python-lxml/python-lxml.mk
+++ b/package/python-lxml/python-lxml.mk
@@ -4,7 +4,7 @@
#
################################################################################
-PYTHON_LXML_VERSION = 4.2.4
+PYTHON_LXML_VERSION = 4.2.5
PYTHON_LXML_SITE = http://lxml.de/files
PYTHON_LXML_SOURCE = lxml-$(PYTHON_LXML_VERSION).tgz
--
2.17.1
next reply other threads:[~2018-09-21 9:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-21 9:59 Asaf Kahlon [this message]
2018-09-25 21:30 ` [Buildroot] [PATCH 1/1] python-lxml: bump to version 4.2.5 Thomas Petazzoni
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=20180921095948.964-1-asafka7@gmail.com \
--to=asafka7@gmail.com \
--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