linux/poky.git/bitbake/lib/bb, branch denzil

bitbake: command: Fix getCmdLineAction bugs

2013-01-28T12:44:14+00:00

Executing "bitbake" doesn't get a sane message since the None return value wasn't being handled correctly. Also fix msg -> cmd_action['msg'] as otherwise an invalid variable is accessed which then crashes the server due to the previous bug. (Bitbake rev: c6211291ae07410832031a5274690437cc2b09a6) Signed-off-by: Richard Purdie

bitbake: command: Add missing import traceback

2013-01-28T12:44:06+00:00

Without this, if an exception occurs the server will silently crash with no feedback to the user about why (since traceback isn't imported). (Bitbake rev: e637a635bf7b5a9a2e9dc20afc18aceec98d578f) Signed-off-by: Richard Purdie

bitbake: command: add error to return of runCommand

2013-01-28T12:43:58+00:00

Currently, command.py can return an error message from runCommand, due to being unable to run the command, yet few of our UIs (just hob) can handle it today. This can result in seeing a TypeError with traceback in certain rare circumstances. To resolve this, we need a clean way to get errors back from runCommand, without having to isinstance() the return value. This implements such a thing by making runCommand also return an error (or None if no error occurred). As runCommand now has a method of returning errors, we can also alter the getCmdLineAction bits such that the returned value is just the action, not an additional message. If a sync command wants to return an error, it raises CommandError(message), and the message will be passed to the caller appropriately. Example Usage: result, error = server.runCommand(...) if error: log.error('Unable to run command: %s' % error) return 1 (Bitbake rev: 717831b8315cb3904d9b590e633000bc897e8fb6) Signed-off-by: Christopher Larson Signed-off-by: Richard Purdie

bitbake: lib/bb/siggen.py: log when tainting the signature of a task

2012-10-12T07:58:48+00:00

Log a note when applying a taint to a task signature (e.g. when using the -f or -C command line options) so that the user knows this has been done. (Bitbake rev: 0fd960fdea83874eedb541cbc2920257e0f3fb81) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

bitbake: bitbake: ensure -f causes dependent tasks to be re-run

2012-10-12T07:58:34+00:00

If -f is specified, force dependent tasks to be re-run next time. This works by changing the force behaviour so that instead of deleting the task's stamp, we write a "taint" file into the stamps directory, which will alter the taskhash randomly and thus trigger the task to re-run next time we evaluate whether or not that should be done as well as influencing the taskhashes of any dependent tasks so that they are similarly re-triggered. As a bonus because we write this file as .taskname.taint, the existing code which deletes the stamp files in OE's do_clean will already handle removing it. This means you can now do the following: bitbake somepackage [ change the source code in the package's WORKDIR ] bitbake -c compile -f somepackage bitbake somepackage and the result will be that all of the tasks that depend on do_compile (do_install, do_package, etc.) will be re-run in the last step. Note that to operate in the manner described above you need full hashing enabled (i.e. BB_SIGNATURE_HANDLER must be set to a signature handler that inherits from BasicHash). If this is not the case, -f will just delete the stamp for the specified task as it did before. This fix is required for [YOCTO #2615] and [YOCTO #2256]. (Bitbake rev: f7b55a94226f9acd985f87946e26d01bd86a35bb) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

Save proxy settings

2012-10-01T17:13:15+00:00

Proxy settings were not properly saved between Hob runs. This fix is mostly a backport of code in master. [YOCTO #3024] Signed-off-by: Bogdan Marinescu

bitbake: hob: format error messages properly

2012-10-01T17:13:05+00:00

Error messages that use arguments need to be formatted properly, or we don't get the full message. Use a formatter to do this when an error occurs. Partial fix for [YOCTO #2983]. (Bitbake rev: 6783538884adecd914909a9ab4ca73c27575f3ad) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

bitbake: hob: ensure error message text is properly escaped

2012-10-01T17:12:32+00:00

Our lack of markup escaping was causing invalid markup, leading to the error dialog being blank. Use the glib markup escaping function provided by PyGTK+ to do this properly and avoid the blank error dialogs. Partial fix for [YOCTO #2983]. (Bitbake rev: 563ea5233a5ab1629c51e802d04280692f96c596) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

cooker: fix UnboundLocalError when exception occurs during parsing

2012-08-21T10:35:20+00:00

Fix a recent regression where we see the following additional error after an error occurs during parsing: ERROR: Command execution failed: Traceback (most recent call last): File "/home/paul/poky/poky/bitbake/lib/bb/command.py", line 84, in runAsyncCommand self.cooker.updateCache() File "/home/paul/poky/poky/bitbake/lib/bb/cooker.py", line 1202, in updateCache if not self.parser.parse_next(): File "/home/paul/poky/poky/bitbake/lib/bb/cooker.py", line 1672, in parse_next self.virtuals += len(result) UnboundLocalError: local variable 'result' referenced before assignment (Bitbake rev: 1ae0181ba49ccfcb2d889de5dd1d8912b9e49157) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

bitbake/fetch2: remove references to ChecksumError class

2012-08-21T10:35:08+00:00

From: Matthew McClintock When merging fetch2 improvements from master into denzil, there were too many dependencies to pull in the entire ChecksumError class, so this patch removes references to ChecksumError for compatability. Fixes this issue: NameError: global name 'ChecksumError' is not defined Signed-off-by: Matthew McClintock Signed-off-by: Scott Garman