From: Asaf Kahlon <asafka7@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] python-bcrypt: bump to version 3.1.6
Date: Sat, 19 Jan 2019 10:44:52 +0200 [thread overview]
Message-ID: <20190119084454.22687-2-asafka7@gmail.com> (raw)
In-Reply-To: <20190119084454.22687-1-asafka7@gmail.com>
Signed-off-by: Asaf Kahlon <asafka7@gmail.com>
---
package/python-bcrypt/python-bcrypt.hash | 4 ++--
package/python-bcrypt/python-bcrypt.mk | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/package/python-bcrypt/python-bcrypt.hash b/package/python-bcrypt/python-bcrypt.hash
index 14933a6187..3e4c303a1f 100644
--- a/package/python-bcrypt/python-bcrypt.hash
+++ b/package/python-bcrypt/python-bcrypt.hash
@@ -1,5 +1,5 @@
# md5, sha256 from https://pypi.org/pypi/bcrypt/json
-md5 7b441a7cdabf6d6f8ad44af2c0a91ab6 bcrypt-3.1.5.tar.gz
-sha256 136243dc44e5bab9b61206bd46fff3018bd80980b1a1dfbab64a22ff5745957f bcrypt-3.1.5.tar.gz
+md5 4d8ab82e5e0c86b15f4ba5aff2bec6b5 bcrypt-3.1.6.tar.gz
+sha256 44636759d222baa62806bbceb20e96f75a015a6381690d1bc2eda91c01ec02ea bcrypt-3.1.6.tar.gz
# Locally computed sha256 checksums
sha256 8173d5c29b4f956d532781d2b86e4e30f83e6b7878dce18c919451d6ba707c90 LICENSE
diff --git a/package/python-bcrypt/python-bcrypt.mk b/package/python-bcrypt/python-bcrypt.mk
index 8d25795656..71bf036fce 100644
--- a/package/python-bcrypt/python-bcrypt.mk
+++ b/package/python-bcrypt/python-bcrypt.mk
@@ -4,9 +4,9 @@
#
################################################################################
-PYTHON_BCRYPT_VERSION = 3.1.5
+PYTHON_BCRYPT_VERSION = 3.1.6
PYTHON_BCRYPT_SOURCE = bcrypt-$(PYTHON_BCRYPT_VERSION).tar.gz
-PYTHON_BCRYPT_SITE = https://files.pythonhosted.org/packages/91/a5/fd19eac0252e56b4ce65ced937ae40024782c21108da7d830003b7f76cdb
+PYTHON_BCRYPT_SITE = https://files.pythonhosted.org/packages/ce/3a/3d540b9f5ee8d92ce757eebacf167b9deedb8e30aedec69a2a072b2399bb
PYTHON_BCRYPT_SETUP_TYPE = setuptools
PYTHON_BCRYPT_LICENSE = Apache-2.0
PYTHON_BCRYPT_LICENSE_FILES = LICENSE
--
2.19.1
next prev parent reply other threads:[~2019-01-19 8:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-19 8:44 [Buildroot] [PATCH 1/1] libuv: bump to version 1.25.0 Asaf Kahlon
2019-01-19 8:44 ` Asaf Kahlon [this message]
2019-01-19 22:07 ` [Buildroot] [PATCH 1/1] python-bcrypt: bump to version 3.1.6 Peter Korsgaard
2019-01-19 8:44 ` [Buildroot] [PATCH 1/1] python-logbook: bump to version 1.4.3 Asaf Kahlon
2019-01-19 22:07 ` Peter Korsgaard
2019-01-19 8:44 ` [Buildroot] [PATCH 1/1] python-txtorcon: bump to version 19.0.0 Asaf Kahlon
2019-01-19 22:07 ` Peter Korsgaard
2019-01-19 22:07 ` [Buildroot] [PATCH 1/1] libuv: bump to version 1.25.0 Peter Korsgaard
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=20190119084454.22687-2-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