Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-python][PATCH 3/3] python-m2crypto: Upgrade to 0.26.0
Date: Tue, 15 Aug 2017 10:02:35 -0500	[thread overview]
Message-ID: <1502809355.28941.41.camel@linux.intel.com> (raw)
In-Reply-To: <20170815050221.16408-3-raj.khem@gmail.com>

On Mon, 2017-08-14 at 22:02 -0700, Khem Raj wrote:
> Use proper LICENCE file for LIC_FILES_CHKSUM
> 
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
>  ...{python-m2crypto_0.25.1.bb => python-m2crypto_0.26.0.bb} | 13 +++++--------
>  1 file changed, 5 insertions(+), 8 deletions(-)
>  rename meta-python/recipes-devtools/python/{python-m2crypto_0.25.1.bb => python-m2crypto_0.26.0.bb} (79%)
> 
> diff --git a/meta-python/recipes-devtools/python/python-m2crypto_0.25.1.bb b/meta-python/recipes-devtools/python/python-m2crypto_0.26.0.bb
> similarity index 79%
> rename from meta-python/recipes-devtools/python/python-m2crypto_0.25.1.bb
> rename to meta-python/recipes-devtools/python/python-m2crypto_0.26.0.bb
> index 72523bd7f..446f4d80a 100644
> --- a/meta-python/recipes-devtools/python/python-m2crypto_0.25.1.bb
> +++ b/meta-python/recipes-devtools/python/python-m2crypto_0.26.0.bb
> @@ -2,12 +2,11 @@ SUMMARY = "A Python crypto and SSL toolkit"
>  HOMEPAGE = "http://chandlerproject.org/bin/view/Projects/MeTooCrypto"

Just tried looking into the HOMEPAGE and seems that it has moved to 

https://gitlab.com/m2crypto/m2crypto


updating this patch with the above would be the fastest path to change
this var.



>  
>  LICENSE = "BSD"
> -LIC_FILES_CHKSUM = "file://PKG-INFO;md5=95295693f047bb8f76928251a6154a60"
> -
> -SRC_URI[md5sum] = "040234289fbef5bed4029f0f7d1dae35"
> -SRC_URI[sha256sum] = "ac303a1881307a51c85ee8b1d87844d9866ee823b4fdbc52f7e79187c2d9acef"
> +LIC_FILES_CHKSUM = "file://LICENCE;md5=b0e1f0b7d0ce8a62c18b1287b991800e"
>  
>  SRC_URI += "file://0001-setup.py-link-in-sysroot-not-in-host-directories.patch "
> +SRC_URI[md5sum] = "9f02f0b88fbe225cc6ea8680945cafa0"
> +SRC_URI[sha256sum] = "05d94fd9b2dae2fb8e072819a795f0e05d3611b09ea185f68e1630530ec09ae8"
>  
>  PYPI_PACKAGE = "M2Crypto"
>  inherit pypi setuptools siteinfo
> @@ -18,10 +17,8 @@ RDEPENDS_${PN} += "python-typing"
>  DISTUTILS_BUILD_ARGS += "build_ext --openssl=${STAGING_DIR_HOST} -I${STAGING_INCDIR}"
>  DISTUTILS_INSTALL_ARGS += "build_ext --openssl=${STAGING_DIR_HOST}"
>  
> -inherit setuptools
> -
> -SWIG_FEATURES_x86-64 = "-D__x86_64__"
> -SWIG_FEATURES ?= ""
> +SWIG_FEATURES_append_x86-64 = " -D__x86_64__"
> +SWIG_FEATURES = "-ignoremissing"
>  export SWIG_FEATURES
>  
>  # Get around a problem with swig, but only if the
> -- 
> 2.14.1
> 




  reply	other threads:[~2017-08-15 14:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-15  5:02 [meta-oe][PATCH 1/3] gsoap: Upgrade to 2.8.51 Khem Raj
2017-08-15  5:02 ` [meta-multimedia][PATCH 2/3] caps: Mark ARCH empty Khem Raj
2017-08-15  5:02 ` [meta-python][PATCH 3/3] python-m2crypto: Upgrade to 0.26.0 Khem Raj
2017-08-15 15:02   ` Leonardo Sandoval [this message]
2017-08-21  7:37     ` Martin Jansa

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=1502809355.28941.41.camel@linux.intel.com \
    --to=leonardo.sandoval.gonzalez@linux.intel.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    /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