Openembedded Core Discussions
 help / color / mirror / Atom feed
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: Mon, 15 Jul 2013 10:47:21 +0100	[thread overview]
Message-ID: <3927888.IYAupCGTDk@helios> (raw)
In-Reply-To: <51E3599E.5000807@cn.fujitsu.com>

On Monday 15 July 2013 10:08:30 Bian Naimeng wrote:
> Hi Paul,
> 
> said the following on 2013-7-13 1:07:, Paul Eggleton wrote:
> > 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?
> 
> Thanks for your suggestion.
> Yes, it's can avoid this problem.
> 
> But, why we don't remove the xxx.spec file before doing rpmbuild xx.src.rpm
> if it's existed. The old xxx.spec is unuseful.

It's a tricky situation. I just think there's a limit to the lengths we should 
go to to prevent extraction of an archive that doesn't contain a subdirectory 
and may therefore extract files that clash with files the build system wants to 
write. In any case, this patch has now been merged.

> In my opinion, it can make the bb file easier and clean than using
> subdir=xyz in the SRC_URI

The subdir parameter is trivial to add, and my advice is that subdir should 
always be used when the archive doesn't contain a reasonable subdirectory and 
then you won't hit subtle problems like this one. 

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


      reply	other threads:[~2013-07-15  9:47 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
2013-07-15  2:08         ` Bian Naimeng
2013-07-15  9:47           ` Paul Eggleton [this message]

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=3927888.IYAupCGTDk@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