Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Trevor Woerner <trevor.woerner@linaro.org>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [RFC PATCH 0/7] Developer workflow improvements
Date: Thu, 11 Dec 2014 14:43:40 -0500	[thread overview]
Message-ID: <5489F3EC.1090206@linaro.org> (raw)
In-Reply-To: <5489EDA6.1000709@linaro.org>

bisecting (manually) leads to this commit being safe:

ea50ec527483eb3a094588858baebd5fb23f71c6 devtool: rename deploy/undeploy
to deploy-target/undeploy-target

and this one introducing the problem:

770f203f73f358ce3c6c5ac12fe2775b812bdc6b devtool: fool bitbake into
thinking it's outputting to a terminal



On 12/11/14 14:16, Trevor Woerner wrote:
> Oops! (this worked before the "git pull")
>
>     $ devtool add xannounce ~/devel/yocto/build/workflow/xannounce/
>     NOTE: Creating workspace layer in
>     /home/trevor/devel/yocto/build/workflow/build/workspace
>     NOTE: Recipe
>     /home/trevor/devel/yocto/build/workflow/build/workspace/recipes/xannounce/xannounce.bb
>     has been automatically created; further editing may be required to
>     make it fully functional
>     Traceback (most recent call last):
>       File
>     "/home/trevor/devel/yocto/build/workflow/meta-poky/scripts/devtool",
>     line 274, in <module>
>         ret = main()
>       File
>     "/home/trevor/devel/yocto/build/workflow/meta-poky/scripts/devtool",
>     line 267, in main
>         ret = args.func(args, config, basepath, workspace)
>       File
>     "/home/trevor/devel/yocto/build/workflow/meta-poky/scripts/lib/devtool/standard.py",
>     line 68, in add
>         _add_md5(config, args.recipename, recipefile)
>       File
>     "/home/trevor/devel/yocto/build/workflow/meta-poky/scripts/lib/devtool/standard.py",
>     line 218, in _add_md5
>         md5 = bb.utils.md5_file(filename)
>       File
>     "/home/trevor/devel/yocto/build/workflow/meta-poky/bitbake/lib/bb/utils.py",
>     line 463, in md5_file
>         with open(filename, "rb") as f:
>     IOError: [Errno 2] No such file or directory:
>     '/home/trevor/devel/yocto/build/workflow/build/workspace/recipes/xannounce/xannounce.bb'
>
> Sure enough...
>
>     $ devtool-workflow> tree workspace/
>     workspace/
>     |-- appends
>     |-- conf
>     |   `-- layer.conf
>     `-- recipes
>         `-- xannounce
>
>     4 directories, 1 file
>
>
> whereas before it was:
>
>     $ tree workspace/
>     workspace/
>     |-- appends
>     |   `-- xannounce.bbappend
>     |-- conf
>     |   `-- layer.conf
>     `-- recipes
>         `-- xannounce
>             `-- xannounce.bb
>
>     4 directories, 3 files
>
> For some reason my recipe and bbappends are not getting created :-(



  reply	other threads:[~2014-12-11 19:43 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-25 17:28 [RFC PATCH 0/7] Developer workflow improvements Paul Eggleton
2014-11-25 17:28 ` [RFC PATCH 1/7] lib/oe/patch: fall back to patch if git apply fails Paul Eggleton
2014-11-25 17:40   ` Paul Barker
2014-11-25 17:58     ` Paul Eggleton
2014-11-25 17:28 ` [RFC PATCH 2/7] lib/oe/patch: auto-commit when falling back from git am Paul Eggleton
2014-11-25 17:28 ` [RFC PATCH 3/7] lib/oe/patch: use --keep-cr with " Paul Eggleton
2014-11-25 17:28 ` [RFC PATCH 4/7] scripts/recipetool: Add a recipe auto-creation script Paul Eggleton
2014-11-25 17:28 ` [RFC PATCH 5/7] lib/oe: add recipeutils module Paul Eggleton
2014-11-25 17:28 ` [RFC PATCH 6/7] scripts/devtool: add development helper tool Paul Eggleton
2014-11-25 17:28 ` [RFC PATCH 7/7] scripts/devtool: Support deploy/undeploy function Paul Eggleton
2014-11-25 17:51 ` [RFC PATCH 0/7] Developer workflow improvements Paul Barker
2014-11-25 18:34   ` Paul Eggleton
2014-11-25 19:56 ` Trevor Woerner
2014-11-26  9:02   ` Paul Eggleton
2014-11-28 17:28 ` Trevor Woerner
2014-12-01 10:11   ` Paul Eggleton
2014-12-02  4:36     ` Trevor Woerner
2014-12-02 11:46       ` Paul Eggleton
2014-12-04 14:03         ` Trevor Woerner
2014-12-04 15:33           ` Paul Eggleton
2014-12-02  4:54 ` Trevor Woerner
2014-12-02 14:01   ` Paul Eggleton
2014-12-09 15:47     ` Trevor Woerner
2014-12-11 23:10       ` Trevor Woerner
2014-12-12 12:39         ` Paul Eggleton
     [not found] ` <54866CD7.1050102@linaro.org>
     [not found]   ` <7839390.odV1UMkpj8@peggleto-mobl5.ger.corp.intel.com>
2014-12-09 15:00     ` Trevor Woerner
2014-12-09 15:10       ` Paul Eggleton
2014-12-09 15:39         ` Trevor Woerner
2014-12-09 16:08           ` Paul Eggleton
2014-12-09 18:58             ` Trevor Woerner
2014-12-10 17:51               ` Paul Eggleton
2014-12-11 17:14                 ` Paul Eggleton
2014-12-11 18:30                   ` Trevor Woerner
2014-12-11 18:55                     ` Paul Eggleton
2014-12-11 19:16                       ` Trevor Woerner
2014-12-11 19:43                         ` Trevor Woerner [this message]
2014-12-11 21:35                           ` Paul Eggleton
2014-12-11 23:14                             ` Trevor Woerner
2014-12-12 13:01                             ` Otavio Salvador
2014-12-14  3:47                   ` Trevor Woerner

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=5489F3EC.1090206@linaro.org \
    --to=trevor.woerner@linaro.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.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