From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Bian Naimeng <biannm@cn.fujitsu.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/1]package_rpm.bbclass: remove xx.spec before doing rpmbuild xx.src.rpm
Date: Fri, 12 Jul 2013 18:07:58 +0100 [thread overview]
Message-ID: <7309265.hkedPcPrsU@helios> (raw)
In-Reply-To: <51DF6448.5010906@cn.fujitsu.com>
Hi Bian,
On Friday 12 July 2013 10:04:56 Bian Naimeng wrote:
> said the following on 2013-7-11 18:54:, Burton, Ross wrote:
> > On 10 July 2013 03:56, Bian Naimeng <biannm@cn.fujitsu.com> wrote:
> >> Sorry, it looks like i should post this patch to poky. please ignore this
> >
> > You were right the first time, meta/ is oe-core. :)
>
> Thanks for your reminding.
>
> In this case, the following error will be caught.
>
> | error: Bad owner/group: .../tmp/work/i586-poky-linux/.../xxx.spec
> | Building target platforms: i586-poky-linux
> |
> | RPM build errors:
> | Bad owner/group: .../tmp/work/i586-poky-linux/.../xxx.spec
>
> The following bb file can cause this error.
> # cat xxx.bb
> SRC_URI="..../xxx.src.rpm"
>
> do_unpack2 () {
> cd ${WORKDIR}
> tar zxvf xxx.tar.gz
> }
> addtask do_unpack2 after do_unpack before do_configure
>
> Of course, we can walk around it by append "extract=xxx.tar.gz" to SRC_URI,
> but it's not good way when the xxx.src.rpm containing lots of necessary
> files.
Wouldn't using subdir=xyz in the SRC_URI entry put the contents of the rpm
into a subdirectory and thus avoid this problem?
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-07-12 17:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-09 8:27 [PATCH 0/1]package_rpm.bbclass: remove xx.spec before doing rpmbuild xx.src.rpm Bian Naimeng
2013-07-10 2:56 ` Bian Naimeng
2013-07-11 10:54 ` Burton, Ross
2013-07-12 2:04 ` Bian Naimeng
2013-07-12 17:07 ` Paul Eggleton [this message]
2013-07-15 2:08 ` Bian Naimeng
2013-07-15 9:47 ` 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=7309265.hkedPcPrsU@helios \
--to=paul.eggleton@linux.intel.com \
--cc=biannm@cn.fujitsu.com \
--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