All of lore.kernel.org
 help / color / mirror / Atom feed
From: brian avery <brian.avery@intel.com>
To: toaster@yoctoproject.org
Cc: brian avery <brian.avery@intel.com>
Subject: [PATCH 0/2] toaster: allow builddir to be named other than build bug 9992
Date: Wed,  1 Feb 2017 11:11:30 -0800	[thread overview]
Message-ID: <cover.1485975972.git.brian.avery@intel.com> (raw)

This pattchset fixes two bugs. The most important of which is in the sublject line.

9992 -> if we do oe-init-build-env cow, toaster would fail because it had the directory
name build hardcoded for toaster.sqlite.  This patch moves the toaster.sqlite database to
TOASTER_DIR so that you can name your builddir whatever you'd like to.

11006-> the runbuilds process was printing out alot of debug and status messages to the
console.  Since the console can also be used to run cli builds while toaster displays
their status, this was quite disconcerting.  This patch redirects the output to
toaster_runbuilds.log.

-brian avery


The following changes since commit ec3d83f9a90288403b96be25da855fa280aadd8d:

  xmlto: Don't hardcode the path to tail (2017-01-31 23:47:33 +0000)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib bavery/toaster/9992-builddir-not-buildV4
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=bavery/toaster/9992-builddir-not-buildV4

brian avery (2):
  toaster: put runbuilds output into a log file
  toaster: move sqlite database to TOASTER_DIR

 bitbake/bin/toaster                         | 5 ++++-
 bitbake/lib/toaster/toastermain/settings.py | 3 +--
 2 files changed, 5 insertions(+), 3 deletions(-)

--
1.9.1


             reply	other threads:[~2017-02-01 19:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-01 19:11 brian avery [this message]
2017-02-01 19:11 ` [PATCH 1/2] toaster: put runbuilds output into a log file brian avery
2017-02-01 19:11 ` [PATCH 2/2] toaster: move sqlite database to TOASTER_DIR brian avery

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=cover.1485975972.git.brian.avery@intel.com \
    --to=brian.avery@intel.com \
    --cc=toaster@yoctoproject.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.