linux/poky.git/bitbake/lib, branch 1.3_M5

bitbake: fetch2/git: Don't use deprecated API

2012-09-25T14:55:57+00:00

(Bitbake rev: 8e650b3307b60cfe8e7439ea6891c3a85f785af9) Signed-off-by: Richard Purdie

bitbake: hob/packageselectionpage:cancel button should redirect to Image conf screen

2012-09-25T12:39:46+00:00

Cancel button brings you to Image configuration page. [YOCTO #3105] (Bitbake rev: 88cd9586f0f6a413c1a6800b3e57444f453afb73) Signed-off-by: Cristiana Voicu Signed-off-by: Richard Purdie

bitbake: hob/builddetailspage: change tooltips and remove a dialog from "Build stopped" message

2012-09-25T12:39:46+00:00

When you stop a build, a "Build stopped" message appears. I have changed 2 tooltips and also eliminate the alert that comes up when you click 'Edit packages'. [YOCTO #3160] (Bitbake rev: f5a21da2faf7ede56cf211b96dffd8aaa4b485b8) Signed-off-by: Cristiana Voicu Signed-off-by: Richard Purdie

bitbake: event.py, knotty.py, ncurses.py, runningbuild.py: Add support for LogExecTTY event

2012-09-24T14:35:32+00:00

The LogExecTTY even is intended to provide the ability to spawn a task on a the controlling tty, if a tty is availble. When a controlling tty is not availble the previous behavior is preserved where a warning is issued about the action an end user must execute. All the available UI's were tested against the new event type. This feature is primarily intended for hooking up a screen client session automatically on the controlling tty to allow for a more streamlined end user experience when using a pure command line driven environment. The changes that send the LogExecTTY event are in the oe-core side. (Bitbake rev: cffe80d82a46aaf52ff4a7b6409435754043553f) Signed-off-by: Jason Wessel Signed-off-by: Richard Purdie

bitbake: progress.py: Fix traceback when running goggle ui

2012-09-24T14:35:31+00:00

The following traceback appears when running the following command after the devshell is exited. bitbake -u goggle -c devshell busybox -- traceback -- Traceback (most recent call last): File "/work/bitbake/lib/bb/ui/goggle.py", line 35, in event_handle_idle_func build.handle_event (event, pbar) File "/work/bitbake/lib/bb/ui/crumbs/runningbuild.py", line 299, in handle_event pbar.set_text(event.msg) AttributeError: 'ProgressBar' object has no attribute 'set_text' (Bitbake rev: a6cc53cdb3c34fc8fd01bbc5ce0008429dc6785c) Signed-off-by: Jason Wessel Signed-off-by: Richard Purdie

bitbake: runqueue: Add --no-setscene to skip all setscene tasks

2012-09-24T14:35:31+00:00

Mainly intended for the purpose of debugging or forcing builds from source, the --no-setscene will prevent any setscene tasks from running. (Bitbake rev: 440e479f3e248482c38c149643403c6907ac7034) Signed-off-by: Jason Wessel Signed-off-by: Richard Purdie

bitbake: fetch2/git: Add missing mkdir

2012-09-24T11:13:52+00:00

bitbake-selftest is failing due to directories not being created. This adds in an appropriate mkdir so the tests can complete. Presumably in general OE use, something else is ensuring the parent directory is created. (Bitbake rev: 1270a07713e2a6c6e6fadcc61b785aebc99ae17b) Signed-off-by: Richard Purdie

bitbake: fetch2: improve error output for checksum failures

2012-09-24T11:13:52+00:00

* Don't print the full exception in the initial warning - if we later succeed in fetching the file from a mirror, we won't usually need the details (which are in the fetch log if they are needed); otherwise the full error will be printed when the fetch operation fails. Also adjust the conditional block so that we don't print another warning just mentioning we're going to try mirrors. * Call logger.error() so that with knotty the full log is not printed * Provide an explanation around the lines we print for easily updating the checksums in the recipe. We don't want users to be just blindly updating the recipe in case of a transient failure or deliberately altered remote file. (Bitbake rev: 2793413106c925b06783beb7413aa87cbcf246c3) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

bitbake: fetch2: make fetch failure errors more readable

2012-09-24T11:13:52+00:00

Most of the time we don't need to see the fetch command; the fetch log includes the command as a debug message in any case, so omit it. Also adjust the way command output is printed (we don't need stderr/stdout labelled, and print "no output" instead of "output:\nNone" when there is no output. (Bitbake rev: a75505a52e4da918222100221f79e8a658f90446) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

bitbake: lib/bb/runqueue.py: fix exceptions with -k and failed targets

2012-09-24T11:13:51+00:00

If a target dependency is marked as failed and yet we are continuing on because -k has been specified, don't try to access the dependency's data in taskData.build_targets since it will have been removed. This fixes "IndexError: list index out of range" errors in this situation. Also, do not print the "unhandled exception" message when SystemExit is raised since we will have reported the actual error already in this case (e.g. when -k has been specified and some targets failed). Fixes [YOCTO #3133]. (Bitbake rev: 70eebc184eb1ab3678be87bed019b5beadecdc89) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie