Openembedded Core Discussions
 help / color / mirror / Atom feed
From: jhuang0 <jackie.huang@windriver.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] libproxy_0.4.7 do_unpack failed of qemuppc_world
Date: Mon, 17 Jun 2013 15:10:58 +0800	[thread overview]
Message-ID: <51BEB682.30702@windriver.com> (raw)
In-Reply-To: <C5D1E420-8F11-410E-B763-C631248F2113@gmail.com>



On 6/17/2013 3:02 PM, Khem Raj wrote:
>
> On Jun 16, 2013, at 11:30 PM, jackie.huang@windriver.com wrote:
>
>> From: Jackie Huang <jackie.huang@windriver.com>
>>
>> The tarball from upstream shows many lines of....
>>
>>    tar: Ignoring unknown extended header keyword
>>       `LIBARCHIVE.xattr.security.selinux'
>>    tar: Ignoring unknown extended header keyword `SCHILY.dev'
>>    tar: Ignoring unknown extended header keyword `SCHILY.ino'
>>    tar: Ignoring unknown extended header keyword `SCHILY.nlink'
>>
>> Replacing it with the .zip file from upstream
>
> maybe now it would better to add zip-native to DEPENDS ?

I think the base.bbclass have added this:

     # unzip-native should already be staged before unpacking ZIP recipes
     if ".zip" in srcuri:
         d.appendVarFlag('do_unpack', 'depends', ' 
unzip-native:do_populate_sysroot')

Thanks,
Jackie

>
>>
>> Signed-off-by: Amy Fong <amy.fong@windriver.com>
>> Signed-off-by: Jackie Huang <jackie.huang@windriver.com>
>> ---
>> meta/recipes-support/libproxy/libproxy_0.4.7.bb |    8 ++++----
>> 1 files changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/meta/recipes-support/libproxy/libproxy_0.4.7.bb b/meta/recipes-support/libproxy/libproxy_0.4.7.bb
>> index 89f22b8..30abc27 100644
>> --- a/meta/recipes-support/libproxy/libproxy_0.4.7.bb
>> +++ b/meta/recipes-support/libproxy/libproxy_0.4.7.bb
>> @@ -8,16 +8,16 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=7d7044444a7b1b116e8783edcdb44ff4 \
>>
>> DEPENDS = "gconf glib-2.0"
>>
>> -PR = "r5"
>> +PR = "r6"
>>
>> -SRC_URI = "http://libproxy.googlecode.com/files/libproxy-${PV}.tar.gz \
>> +SRC_URI = "http://libproxy.googlecode.com/files/libproxy-${PV}.zip \
>>             file://g++-namepace.patch \
>>             file://libproxy_fix_for_gcc4.7.patch \
>>             file://libproxy-0.4.7-CVE-2012-4504.patch \
>>            "
>>
>> -SRC_URI[md5sum] = "509e03a488a61cd62bfbaf3ab6a2a7a5"
>> -SRC_URI[sha256sum] = "8fe0a58810139ba3c2e186deccf3e68adcd127aa0e972b0862b30b3dde493797"
>> +SRC_URI[md5sum] = "62585570de17d10f03a5a63b701ffd52"
>> +SRC_URI[sha256sum] = "429a19c57d9990349d622beecc805b23051caa62a478066bff5d9a312a8937be"
>>
>> inherit cmake pkgconfig
>>
>> --
>> 1.7.4.1
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>
>

-- 
Jackie Huang
WIND RIVER | China Development Center
MSN:jackielily@hotmail.com
Tel: +86 8477 8594
Mobile: +86 138 1027 4745


  reply	other threads:[~2013-06-17  7:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-17  6:30 [PATCH] libproxy_0.4.7 do_unpack failed of qemuppc_world jackie.huang
2013-06-17  7:02 ` Khem Raj
2013-06-17  7:10   ` jhuang0 [this message]
2013-06-17  7:12     ` Khem Raj

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=51BEB682.30702@windriver.com \
    --to=jackie.huang@windriver.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