Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Derek Straka <derek@asterius.io>
To: openembedded-devel@lists.openembedded.org
Cc: Derek Straka <derek@asterius.io>
Subject: [meta-python][PATCH 02/11] python-flufl-enum: update to 4.1
Date: Mon, 22 Feb 2016 08:34:56 -0500	[thread overview]
Message-ID: <1456148105-9644-2-git-send-email-derek@asterius.io> (raw)
In-Reply-To: <1456148105-9644-1-git-send-email-derek@asterius.io>

Signed-off-by: Derek Straka <derek@asterius.io>
---
 .../python/{python-flufl-enum_4.0.1.bb => python-flufl-enum_4.1.bb} | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
 rename meta-python/recipes-devtools/python/{python-flufl-enum_4.0.1.bb => python-flufl-enum_4.1.bb} (74%)

diff --git a/meta-python/recipes-devtools/python/python-flufl-enum_4.0.1.bb b/meta-python/recipes-devtools/python/python-flufl-enum_4.1.bb
similarity index 74%
rename from meta-python/recipes-devtools/python/python-flufl-enum_4.0.1.bb
rename to meta-python/recipes-devtools/python/python-flufl-enum_4.1.bb
index fe25fd7..ef10848 100644
--- a/meta-python/recipes-devtools/python/python-flufl-enum_4.0.1.bb
+++ b/meta-python/recipes-devtools/python/python-flufl-enum_4.1.bb
@@ -4,10 +4,10 @@ specific, concise semantics in an easy to read and write syntax. flufl.enum has
 features needed to make enumerations useful, but without a lot of extra baggage to weigh them down. "
 
 LICENSE = "LGPLv3"
-LIC_FILES_CHKSUM = "file://PKG-INFO;md5=1fa25baed15d3be23c902636379438e8"
+LIC_FILES_CHKSUM = "file://PKG-INFO;startline=8;endline=9;md5=250adb4c74c359b7049abcd9d6b115e7"
 
-SRC_URI[md5sum] = "b3ad23761a78232bc78499ced7cb85d9"
-SRC_URI[sha256sum] = "4af7e7cf2dcc7517251570c7ef9ad194e30ee4b6f860eba500c03954ae95f9d8"
+SRC_URI[md5sum] = "461779384c07ed2b5f554a5d51a000c4"
+SRC_URI[sha256sum] = "94da1413ba085473652f81565847913ea1543d1739972ecbd6afe57d7b1b68b4"
 
 PYPI_PACKAGE = "flufl.enum"
 inherit pypi setuptools
-- 
1.9.1



  reply	other threads:[~2016-02-22 13:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-22 13:34 [meta-python][PATCH 01/11] python-ujson: update to 0.35 Derek Straka
2016-02-22 13:34 ` Derek Straka [this message]
2016-02-22 19:22   ` [meta-python][PATCH 02/11] python-flufl-enum: update to 4.1 Khem Raj
2016-02-23 15:47     ` Derek Straka
2016-02-22 13:34 ` [meta-python][PATCH 03/11] python-enum34: update to 1.1.2 Derek Straka
2016-02-22 13:34 ` [meta-python][PATCH 04/11] python-feedparser: update to 5.2.1 Derek Straka
2016-02-22 13:34 ` [meta-python][PATCH 05/11] python-prettytable: fix fetch issues in divergent pypi url pattern Derek Straka
2016-02-22 13:35 ` [meta-python][PATCH 06/11] python-mccabe: update to 0.4.0 Derek Straka
2016-02-22 13:35 ` [meta-python][PATCH 07/11] python-pyflakes: update to 1.0.0 Derek Straka
2016-02-22 13:35 ` [meta-python][PATCH 08/11] python-mock: update to 1.3.0 Derek Straka
2016-02-24 13:04   ` Martin Jansa
2016-02-24 16:20     ` python-setuptools fetch issues Was: " Martin Jansa
2016-02-25  2:19       ` [OE-core] " Burton, Ross
2016-02-22 13:35 ` [meta-python][PATCH 09/11] python-monotonic: update to 0.6 Derek Straka
2016-02-22 13:35 ` [meta-python][PATCH 10/11] python-msgpack: update to 0.4.7 Derek Straka
2016-02-22 13:35 ` [meta-python][PATCH 11/11] python-pyserial: update to 3.0.1 Derek Straka

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=1456148105-9644-2-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