Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Cc: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Subject: Re: [PATCH] devtool: Avoid failure for recipes with S == WORKDIR and no local files
Date: Mon, 02 Sep 2019 22:20:19 +1200	[thread overview]
Message-ID: <2938371.f3R3kiVdeO@linux.fritz.box> (raw)
In-Reply-To: <20190829204302.28348-1-pkj@axis.com>

On Friday, 30 August 2019 8:43:02 AM NZST Peter Kjellerstedt wrote:
> When extracting the sources for a recipe that has S == WORKDIR and no
> local files in the SRC_URI (which, e.g., can happen for a recipe with
> a URI that has the unpack=false attribute), the extraction fails with
> the following backtrace:
> 
>   Traceback (most recent call last):
>     File ".../scripts/devtool", line 344, in <module>
>       ret = main()
>     File ".../scripts/devtool", line 331, in main
>       ret = args.func(args, config, basepath, workspace)
>     File ".../poky/scripts/lib/devtool/standard.py", line 762, in
>     modify
>       initial_rev, _ = _extract_source(srctree, args.keep_temp,
>       args.branch, False, config, basepath, workspace,
>       args.fixed_setup, rd, tinfoil, no_overrides=args.no_overrides)
>     File ".../poky/scripts/lib/devtool/standard.py", line 647, in
>     _extract_source
>       bb.process.run('git %s commit -a -m "Committing local file
>       symlinks\n\n%s"' % (' '.join(useroptions),
>       oe.patch.GitApplyTree.ignore_commit_prefix), cwd=srctree)
>     File ".../poky/bitbake/lib/bb/process.py", line 178, in run
>       raise ExecutionError(cmd, pipe.returncode, stdout, stderr)
>   bb.process.ExecutionError: Execution of 'git commit -a -m
>   "Committing local file symlinks
> 
>   %% ignore"' failed with exit code 1:
>   On branch devtool
>   nothing to commit, working tree clean
> 
> This is because no files were found in the oe-local-files directory
> and consequently no symbolic links were added using `git add`, but the
> `git commit` command was still executed.

Looks good to me - all oe-selftest tests pass as well. (Looks like maybe we 
are missing a test though, since this code has been in place for a while.)

Acked-by: Paul Eggleton <paul.eggleton@linux.intel.com>


-- 

Paul Eggleton
Intel Open Source Technology Centre




      reply	other threads:[~2019-09-02 10:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-29 20:43 [PATCH] devtool: Avoid failure for recipes with S == WORKDIR and no local files Peter Kjellerstedt
2019-09-02 10:20 ` 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=2938371.f3R3kiVdeO@linux.fritz.box \
    --to=paul.eggleton@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=peter.kjellerstedt@axis.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