From: David Reyna <david.reyna@windriver.com>
To: <bitbake-devel@lists.openembedded.org>
Subject: [PATCH 0/1] toaster: custom image enable layer add, protect pre-cloned layers
Date: Wed, 3 Oct 2018 23:10:41 -0700 [thread overview]
Message-ID: <cover.1538633120.git.David.Reyna@windriver.com> (raw)
From: David Reyna <David.Reyna@windriver.com>
Fix for Bug 12887:
* When attempting create a custom image in Toaster for a layer not yet added not cloned, two errors were found.
1) The "Add layer" button did not do anything, due to a missing data structure, easily fixed
2) If the layer was newly added but not yet cloned, the custom image create just hung.
This was because the problems were reported internally but not to the user. This patch adds
the error return chain plus the helpful error recovery message to the user.
The following changes since commit bdb49647874e18e7d60374b8973a307551b36a14:
go.bbclass: Add -buildmode=pie for non mips arch (2018-10-01 13:04:50 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib dreyna/toaster/custom_image_protection_12887
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=dreyna/toaster/custom_image_protection_12887
David Reyna (1):
toaster: custom image enable layer add, protect pre-cloned layers
lib/toaster/orm/models.py | 4 ++--
lib/toaster/toastergui/api.py | 8 +++++++-
lib/toaster/toastergui/static/js/libtoaster.js | 3 ++-
lib/toaster/toastergui/static/js/newcustomimage_modal.js | 7 +++++++
lib/toaster/toastergui/templates/customise_btn.html | 6 +++++-
5 files changed, 23 insertions(+), 5 deletions(-)
--
1.9.1
next reply other threads:[~2018-10-04 6:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-04 6:10 David Reyna [this message]
2018-10-04 6:10 ` [PATCH 1/1] toaster: custom image enable layer add, protect pre-cloned layers David Reyna
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.1538633120.git.David.Reyna@windriver.com \
--to=david.reyna@windriver.com \
--cc=bitbake-devel@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.