Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Derek Straka <derek@asterius.io>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-python][PATCH] python-bcrypt: update to version 3.1.2
Date: Thu, 22 Dec 2016 09:40:39 -0500	[thread overview]
Message-ID: <1482417639-20969-1-git-send-email-derek@asterius.io> (raw)

Signed-off-by: Derek Straka <derek@asterius.io>
---
 .../python/{python-bcrypt_3.1.1.bb => python-bcrypt_3.1.2.bb}  | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)
 rename meta-python/recipes-devtools/python/{python-bcrypt_3.1.1.bb => python-bcrypt_3.1.2.bb} (51%)

diff --git a/meta-python/recipes-devtools/python/python-bcrypt_3.1.1.bb b/meta-python/recipes-devtools/python/python-bcrypt_3.1.2.bb
similarity index 51%
rename from meta-python/recipes-devtools/python/python-bcrypt_3.1.1.bb
rename to meta-python/recipes-devtools/python/python-bcrypt_3.1.2.bb
index aae037f..d7adc0e 100644
--- a/meta-python/recipes-devtools/python/python-bcrypt_3.1.1.bb
+++ b/meta-python/recipes-devtools/python/python-bcrypt_3.1.2.bb
@@ -4,12 +4,12 @@ LIC_FILES_CHKSUM = "file://LICENSE;md5=8f7bb094c7232b058c7e9f2e431f389c"
 
 DEPENDS = "python-cffi-native"
 
-SRC_URI[md5sum] = "7348b2c361e23cf205701bba7652d789"
-SRC_URI[sha256sum] = "0309a4a72bd1dc314279cf1ee14e277227732f14c9b63ab96715654e13fe9321"
+SRC_URI[md5sum] = "c5a79004fc4ad589615e96a6fe45b664"
+SRC_URI[sha256sum] = "346e175c820a111c17d4c2def181a96e1826652edb0bb16e565085ed542785aa"
 
 inherit pypi setuptools
 
-RDEPENDS_${PN} = "\
-    python-cffi \
-    python-six \
+RDEPENDS_${PN}_class-target = "\
+    ${PYTHON_PN}-cffi \
+    ${PYTHON_PN}-six \
 "
-- 
2.7.4



                 reply	other threads:[~2016-12-22 14:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1482417639-20969-1-git-send-email-derek@asterius.io \
    --to=derek@asterius.io \
    --cc=openembedded-devel@lists.openembedded.org \
    /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