From: Martin Jansa <martin.jansa@gmail.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 19/24] python3-pycurl: Add recipe
Date: Mon, 8 Jul 2013 12:44:02 +0200 [thread overview]
Message-ID: <20130708104402.GI3288@jama> (raw)
In-Reply-To: <4b305736d4226c770324950a1efca903800fbc9c.1372456294.git.raj.khem@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1552 bytes --]
On Fri, Jun 28, 2013 at 03:04:04PM -0700, Khem Raj wrote:
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
> .../python/python3-pycurl/no-static-link.patch | 16 +++++++++
> .../python/python3-pycurl_7.19.0.bb | 35 ++++++++++++++++++++
> 2 files changed, 51 insertions(+)
> create mode 100644 meta/recipes-devtools/python/python3-pycurl/no-static-link.patch
> create mode 100644 meta/recipes-devtools/python/python3-pycurl_7.19.0.bb
There is some overlap with python-curl:
WARNING: The recipe python-pycurl is trying to install files into a
shared area when those files already exist. Those files and their
manifest location are:
/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/sysroots/qemuarm/usr/lib/python2.7/site-packages/pycurl.so
Matched in manifest-qemuarm-python3-pycurl
/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/sysroots/qemuarm/usr/lib/python2.7/site-packages/pycurl-7.19.0-py2.7.egg-info
Matched in manifest-qemuarm-python3-pycurl
/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/sysroots/qemuarm/usr/lib/python2.7/site-packages/curl/__init__.py
Matched in manifest-qemuarm-python3-pycurl
/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/sysroots/qemuarm/usr/lib/python2.7/site-packages/curl/__init__.pyc
Matched in manifest-qemuarm-python3-pycurl
Please verify which package should provide the above files.
Should python3-curl install also in python2.7 libdir?
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2013-07-08 10:43 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 21:59 [PATCH 00/24] Add python3 recipes Khem Raj
2013-06-28 22:03 ` [PATCH 01/24] generate-manifest-3.3.py: Add script to generate python 3.3 manifests Khem Raj
2013-06-28 22:03 ` [PATCH 02/24] python3native.bbclass: Add python3 abstraction class Khem Raj
2013-06-28 22:03 ` [PATCH 03/24] package_rpm.bbclass:Make the regexp less greedy Khem Raj
2013-06-28 22:03 ` [PATCH 04/24] classes/distutils: Introduce PYTHON_PN Khem Raj
2013-06-29 5:29 ` Martin Jansa
2013-06-29 14:07 ` Khem Raj
2013-06-28 22:03 ` [PATCH 05/24] classes: Add distutils for python3 Khem Raj
2013-06-28 22:03 ` [PATCH 06/24] setuptools.bbclass: Use python-distribute instead of python-setuptools Khem Raj
2013-06-28 22:03 ` [PATCH 07/24] distutils3.bbclass: Port the distutils class fix to handle filenames with spaces Khem Raj
2013-06-28 22:03 ` [PATCH 08/24] setuptools3.bbclass: Remove useless multiline comment Khem Raj
2013-06-28 22:03 ` [PATCH 09/24] distutils: Introduce PYTHON_ABI variable Khem Raj
2013-06-28 22:03 ` [PATCH 10/24] distutils3: Do build_ext as separate step during compile Khem Raj
2013-06-28 22:03 ` [PATCH 11/24] python-3.3-manifest: Add python3 manifest file Khem Raj
2013-06-28 22:03 ` [PATCH 12/24] python3: Add recipes Khem Raj
2013-08-26 13:32 ` Martin Jansa
2013-08-26 17:38 ` Khem Raj
2013-08-27 5:23 ` Khem Raj
2013-08-27 7:45 ` Martin Jansa
2013-08-27 7:48 ` Martin Jansa
2013-08-27 18:10 ` Khem Raj
2013-08-27 18:15 ` Martin Jansa
2013-08-28 6:23 ` Khem Raj
2013-06-28 22:03 ` [PATCH 13/24] python3: Add native recipe Khem Raj
2013-06-28 22:03 ` [PATCH 14/24] python_2.7.3.bb: Inherit python-dir Khem Raj
2013-06-28 22:04 ` [PATCH 15/24] ipython: Add recipes for ipython2 and ipython3 Khem Raj
2013-06-28 22:04 ` [PATCH 16/24] python-distribute: Add recipes for python2 and python3 Khem Raj
2013-07-08 10:49 ` Martin Jansa
2013-06-28 22:04 ` [PATCH 17/24] zeromq: Add recipe Khem Raj
2013-06-28 22:04 ` [PATCH 18/24] pyzmq: Add recipes using python3 Khem Raj
2013-06-28 22:04 ` [PATCH 19/24] python3-pycurl: Add recipe Khem Raj
2013-07-08 10:44 ` Martin Jansa [this message]
2013-06-28 22:04 ` [PATCH 20/24] python3-docutils: " Khem Raj
2013-06-28 22:04 ` [PATCH 21/24] python3-jinja: Recipe for python3 templating system Khem Raj
2013-06-30 10:30 ` Martin Jansa
2013-06-28 22:04 ` [PATCH 22/24] python3-nose: Testing tools for python Khem Raj
2013-06-28 22:04 ` [PATCH 23/24] python3-sphinx: New recipe for documentation system Khem Raj
2013-06-28 22:04 ` [PATCH 24/24] python3: Upgrade to 3.3.2 Khem Raj
2013-07-08 10:37 ` Paul Eggleton
2013-06-29 5:38 ` [PATCH 00/24] Add python3 recipes Martin Jansa
2013-06-29 14:11 ` Khem Raj
2013-06-29 15:31 ` Martin Jansa
2013-06-29 17:43 ` Khem Raj
2013-07-30 8:16 ` Khem Raj
2013-07-30 16:45 ` Saul Wold
2013-07-30 18:28 ` Khem Raj
2013-07-31 20:40 ` Saul Wold
2013-07-31 20:59 ` Khem Raj
2013-07-31 22:31 ` Khem Raj
2013-07-31 22:49 ` Saul Wold
2013-07-31 22:51 ` Khem Raj
2013-07-31 23:05 ` Saul Wold
2013-08-01 4:32 ` Khem Raj
2013-08-01 14:47 ` Khem Raj
2013-08-01 20:19 ` Khem Raj
2013-08-02 4:53 ` Saul Wold
2013-08-02 7:27 ` Khem Raj
2013-08-03 22:28 ` Saul Wold
2013-08-05 5:10 ` Saul Wold
2013-08-05 17:50 ` Khem Raj
2013-08-06 5:29 ` Khem Raj
2013-08-07 4:57 ` Khem Raj
2013-07-08 10:37 ` Paul Eggleton
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=20130708104402.GI3288@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-core@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