From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 6/7] python-pycurl: fix packaging warnings
Date: Fri, 16 Mar 2012 23:49:34 +0000 [thread overview]
Message-ID: <1331941774.18586.214.camel@ted> (raw)
In-Reply-To: <b10ee19a1ab989049aafcb0f8eefadf8296dc900.1331924359.git.nitin.a.kamble@intel.com>
On Fri, 2012-03-16 at 12:00 -0700, nitin.a.kamble@intel.com wrote:
> From: Nitin A Kamble <nitin.a.kamble@intel.com>
>
> This commit fixes these packaging warnings:
> WARNING: For recipe python-pycurl, the following files/directories were
> installed but not shipped in any package:
> WARNING: /usr/share/share
>
> PR not bumber because no change in the output packages.
>
> Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
> ---
> .../python/python-pycurl_7.19.0.bb | 4 ++++
> 1 files changed, 4 insertions(+), 0 deletions(-)
>
> diff --git a/meta/recipes-devtools/python/python-pycurl_7.19.0.bb b/meta/recipes-devtools/python/python-pycurl_7.19.0.bb
> index d9fe465..8b849d7 100644
> --- a/meta/recipes-devtools/python/python-pycurl_7.19.0.bb
> +++ b/meta/recipes-devtools/python/python-pycurl_7.19.0.bb
> @@ -29,3 +29,7 @@ export STAGING_INCDIR
> export STAGING_LIBDIR
>
> BBCLASSEXTEND = "native"
> +
> +do_install_append() {
> + rm -rf ${D}${datadir}/share
> +}
What is actually in there? Is that a file or a directory?
This is one of the cases it might be worth looking at why it exists at
all as something looks wrong there at a deeper level...
Cheers,
Richard
next prev parent reply other threads:[~2012-03-16 23:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 19:00 [PATCH 0/7] Misc Fixes and upgrades nitin.a.kamble
2012-03-16 19:00 ` [PATCH 1/7] automake: upgrade from 1.11.2 to 1.11.3 nitin.a.kamble
2012-03-16 19:00 ` [PATCH 2/7] distro-tracking: update status of recipes nitin.a.kamble
2012-03-16 19:00 ` [PATCH 3/7] python: fix install when libdir is not "lib" nitin.a.kamble
2012-03-16 19:00 ` [PATCH 4/7] pciutils: fix a do_compile failure nitin.a.kamble
2012-03-16 19:00 ` [PATCH 5/7] python-pyrex: quite packaging warnings nitin.a.kamble
2012-03-16 19:00 ` [PATCH 6/7] python-pycurl: fix " nitin.a.kamble
2012-03-16 23:49 ` Richard Purdie [this message]
2012-03-17 0:35 ` Kamble, Nitin A
2012-03-17 9:29 ` Richard Purdie
2012-03-16 19:00 ` [PATCH 7/7] git: " nitin.a.kamble
2012-03-17 10:16 ` Paul Menzel
2012-03-19 16:33 ` [PATCH 0/7] Misc Fixes and upgrades Saul Wold
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=1331941774.18586.214.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@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