From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-python][jethro][PATCH 2/4] python-pyasn1: Error fix for recipes depend on python-pyasn1
Date: Mon, 4 Jan 2016 15:11:19 +0100 [thread overview]
Message-ID: <20160104141119.GC2581@jama> (raw)
In-Reply-To: <1451902358-1844-2-git-send-email-lixin.fnst@cn.fujitsu.com>
[-- Attachment #1: Type: text/plain, Size: 885 bytes --]
On Mon, Jan 04, 2016 at 01:12:36PM +0300, Li Xin wrote:
> If you bitbake recipes which depends on python-pyasn1 such as
> python-cryptography. And also your network is not very well.
> Error will occur as following:
> Download error on https://pypi.python.org/simple/pyasn1/:
> [Errno -5] No address associated with hostname -- Some packages may not be found!
> Couldn't find index page for 'pyasn1' (maybe misspelled?)
> No local packages or download links found for pyasn1
> So add do_compile_append() to fix it.
>
> Signed-off-by: Li Xin <lixin.fnst@cn.fujitsu.com>
> ---
> meta-python/recipes-devtools/python/python-pyasn1_0.1.7.bb | 9 +++++++++
> 1 file changed, 9 insertions(+)
Is this change needed in master as well? Where we have 0.1.9 version.
1/4 and 3/4 do apply in master
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2016-01-04 14:07 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 [this message]
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
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=20160104141119.GC2581@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.