Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Asaf Kahlon <asafka7@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/python-subprocess32: bump to version 3.5.4
Date: Fri, 11 Oct 2019 11:35:25 +0300	[thread overview]
Message-ID: <20191011083527.26140-4-asafka7@gmail.com> (raw)
In-Reply-To: <20191011083527.26140-1-asafka7@gmail.com>

Signed-off-by: Asaf Kahlon <asafka7@gmail.com>
---
 package/python-subprocess32/python-subprocess32.hash | 4 ++--
 package/python-subprocess32/python-subprocess32.mk   | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/package/python-subprocess32/python-subprocess32.hash b/package/python-subprocess32/python-subprocess32.hash
index e96505d3d4..65d18763d1 100644
--- a/package/python-subprocess32/python-subprocess32.hash
+++ b/package/python-subprocess32/python-subprocess32.hash
@@ -1,5 +1,5 @@
 # md5, sha256 from https://pypi.org/pypi/subprocess32/json
-md5	afa0510115f483d668e25aa30502d9bc  subprocess32-3.5.3.tar.gz
-sha256	6bc82992316eef3ccff319b5033809801c0c3372709c5f6985299c88ac7225c3  subprocess32-3.5.3.tar.gz
+md5	748844d560be5f0c707931cba1cdb48b  subprocess32-3.5.4.tar.gz
+sha256	eb2937c80497978d181efa1b839ec2d9622cf9600a039a79d0e108d1f9aec79d  subprocess32-3.5.4.tar.gz
 # Locally computed sha256 checksums
 sha256	826b43437249d39422642f695154d064da64de92eb1476048a615f50bc1beb4a  LICENSE
diff --git a/package/python-subprocess32/python-subprocess32.mk b/package/python-subprocess32/python-subprocess32.mk
index d6c57fb8bd..ee591e6a6b 100644
--- a/package/python-subprocess32/python-subprocess32.mk
+++ b/package/python-subprocess32/python-subprocess32.mk
@@ -4,9 +4,9 @@
 #
 ################################################################################
 
-PYTHON_SUBPROCESS32_VERSION = 3.5.3
+PYTHON_SUBPROCESS32_VERSION = 3.5.4
 PYTHON_SUBPROCESS32_SOURCE = subprocess32-$(PYTHON_SUBPROCESS32_VERSION).tar.gz
-PYTHON_SUBPROCESS32_SITE = https://files.pythonhosted.org/packages/be/2b/beeba583e9877e64db10b52a96915afc0feabf7144dcbf2a0d0ea68bf73d
+PYTHON_SUBPROCESS32_SITE = https://files.pythonhosted.org/packages/32/c8/564be4d12629b912ea431f1a50eb8b3b9d00f1a0b1ceff17f266be190007
 PYTHON_SUBPROCESS32_SETUP_TYPE = setuptools
 PYTHON_SUBPROCESS32_LICENSE = Python-2.0
 PYTHON_SUBPROCESS32_LICENSE_FILES = LICENSE
-- 
2.20.1

  parent reply	other threads:[~2019-10-11  8:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-11  8:35 [Buildroot] [PATCH 1/2] package/python-backports-functools-lru-cache: new pacakge Asaf Kahlon
2019-10-11  8:35 ` [Buildroot] [PATCH 1/1] package/python-cssutils: bump to version 1.0.2 Asaf Kahlon
2019-10-12 14:17   ` Thomas Petazzoni
2019-10-11  8:35 ` [Buildroot] [PATCH 1/1] package/python-h2: bump to version 3.1.1 Asaf Kahlon
2019-10-12 14:17   ` Thomas Petazzoni
2019-10-11  8:35 ` Asaf Kahlon [this message]
2019-10-12 14:17   ` [Buildroot] [PATCH 1/1] package/python-subprocess32: bump to version 3.5.4 Thomas Petazzoni
2019-10-11  8:35 ` [Buildroot] [PATCH 1/1] package/python-ubjson: bump to version 0.14.0 Asaf Kahlon
2019-10-12 14:17   ` Thomas Petazzoni
2019-10-11  8:35 ` [Buildroot] [PATCH 2/2] package/python-arrow: bump to version 0.15.2 Asaf Kahlon
2019-10-12 20:04 ` [Buildroot] [PATCH 1/2] package/python-backports-functools-lru-cache: new pacakge 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=20191011083527.26140-4-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