All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bian Naimeng <biannm@cn.fujitsu.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/1]package_rpm.bbclass: remove xx.spec before doing rpmbuild xx.src.rpm
Date: Wed, 10 Jul 2013 10:56:45 +0800	[thread overview]
Message-ID: <51DCCD6D.5050807@cn.fujitsu.com> (raw)
In-Reply-To: <51DBC97F.1090606@cn.fujitsu.com>

Hi all

Sorry, it looks like i should post this patch to poky. please ignore this

Thanks
 Bian

said the following on 2013-7-9 16:27:, Bian Naimeng wrote:
> If the spec file already exist, and has not been stored into pseudo's files.db,
> it maybe cause rpmbuild src.rpm fail, so remove it before doing rpmbuild src.rpm.
> 
> Signed-off-by: Bian Naimeng <biannm@cn.fujitsu.com>
> 
> ---
>  meta/classes/package_rpm.bbclass |    5 +++++
>  1 files changed, 5 insertions(+), 0 deletions(-)
> 
> diff --git a/meta/classes/package_rpm.bbclass b/meta/classes/package_rpm.bbclass
> index c654cdb..217ddcb 100644
> --- a/meta/classes/package_rpm.bbclass
> +++ b/meta/classes/package_rpm.bbclass
> @@ -1069,8 +1069,13 @@ python do_package_rpm () {
>          return
>  
>      # Construct the spec file...
> +    # If the spec file already exist, and has not been stored into 
> +    # pseudo's files.db, it maybe cause rpmbuild src.rpm fail,
> +    # so remove it before doing rpmbuild src.rpm.
>      srcname    = strip_multilib(d.getVar('PN', True), d)
>      outspecfile = workdir + "/" + srcname + ".spec"
> +    if os.path.isfile(outspecfile):
> +        os.remove(outspecfile)
>      d.setVar('OUTSPECFILE', outspecfile)
>      bb.build.exec_func('write_specfile', d)



  reply	other threads:[~2013-07-10  2:56 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 [this message]
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

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=51DCCD6D.5050807@cn.fujitsu.com \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.