From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-python][jethro][PATCH 4/4] python-cryptography: Error fix
Date: Mon, 4 Jan 2016 15:12:30 +0100 [thread overview]
Message-ID: <20160104141230.GD2581@jama> (raw)
In-Reply-To: <1451902358-1844-4-git-send-email-lixin.fnst@cn.fujitsu.com>
[-- Attachment #1: Type: text/plain, Size: 2214 bytes --]
On Mon, Jan 04, 2016 at 01:12:38PM +0300, Li Xin wrote:
> python-cryptography depends on python-enum34 python-six python-pyasn1,
> And will download modules enum34 six pyasn1 in the step of do_compile.
> If your network is not very well,errors will occur as following:
> Download error on https://pypi.python.org/simple/enum34/:
> [Errno -5] No address associated with hostname -- Some packages may not be found!
> Couldn't find index page for 'enum34' (maybe misspelled?)
Is this change needed in master as well? Where we have 1.1 version.
1/4 and 3/4 do apply in master
>
> Signed-off-by: Li Xin <lixin.fnst@cn.fujitsu.com>
> ---
> .../recipes-devtools/python/python-cryptography_0.8.1.bb | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/meta-python/recipes-devtools/python/python-cryptography_0.8.1.bb b/meta-python/recipes-devtools/python/python-cryptography_0.8.1.bb
> index 41e4acd..d6ebbb7 100644
> --- a/meta-python/recipes-devtools/python/python-cryptography_0.8.1.bb
> +++ b/meta-python/recipes-devtools/python/python-cryptography_0.8.1.bb
> @@ -38,6 +38,20 @@ RDEPENDS_${PN}-ptest = "\
>
> inherit ptest
>
> +do_compile_prepend() {
> + install -d ${S}/.eggs
> + if [ -f ${STAGING_DIR_HOST}/${PYTHON_SITEPACKAGES_DIR}/enum34*.egg ]; then
> + cp ${STAGING_DIR_HOST}/${PYTHON_SITEPACKAGES_DIR}/enum34*.egg ${S}/.eggs/
> + fi
> +
> + if [ -f ${STAGING_DIR_HOST}/${PYTHON_SITEPACKAGES_DIR}/pyasn1*.egg ]; then
> + cp ${STAGING_DIR_HOST}/${PYTHON_SITEPACKAGES_DIR}/pyasn1*.egg ${S}/.eggs/
> + fi
> +
> + if [ -f ${STAGING_DIR_HOST}/${PYTHON_SITEPACKAGES_DIR}/six*.egg ]; then
> + cp ${STAGING_DIR_HOST}/${PYTHON_SITEPACKAGES_DIR}/six*.egg ${S}/.eggs/
> + fi
> +}
> do_install_ptest() {
> install -d ${D}${PTEST_PATH}/tests
> cp -rf ${S}/tests/* ${D}${PTEST_PATH}/tests/
> --
> 1.8.4.2
>
>
>
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
prev parent reply other threads:[~2016-01-04 14:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 10:12 [meta-python][jethro][PATCH 1/4] python-enum34: Error Fix for recipes depend on python-enum34 Li Xin
2016-01-04 10:12 ` [meta-python][jethro][PATCH 2/4] python-pyasn1: Error fix for recipes depend on python-pyasn1 Li Xin
2016-01-04 14:11 ` Martin Jansa
2016-01-04 10:12 ` [meta-python][jethro][PATCH 3/4] python-six: Error fix for recipes depend on python-six Li Xin
2016-01-04 10:12 ` [meta-python][jethro][PATCH 4/4] python-cryptography: Error fix Li Xin
2016-01-04 14:12 ` Martin Jansa [this message]
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=20160104141230.GD2581@jama \
--to=martin.jansa@gmail.com \
--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