linux/poky.git/bitbake, branch pyro-next

bitbake: providers: Fix determinism issue

2018-03-09T14:12:09+00:00

We saw builds where runtime providers were sometimes changing order and the build result was therefore non-deterministic. For example it could show: DEBUG: providers for lib32-initd-functions are: ['lib32-lsbinitscripts', 'lib32-initscripts'] or DEBUG: providers for lib32-initd-functions are: ['lib32-initscripts', 'lib32-lsbinitscripts'] which could cause a test to pass or fail. This change ensures we don't rely on the random order of dictonaries in memory and act deterministically. (Bitbake rev: eddab52a4e7c49bfcdc2c26004d0bc777a1e5c25) Signed-off-by: Richard Purdie

bitbake: bitbake-user-manual: Fixed porno hack for hello world example

2018-01-17T22:32:18+00:00

Someone hacked the http://hambedded site or it was moved and some links to that site in the BB manual had been hijacked to point to an entry portal for a pornography site. Replaced the link with an archived version that restores the integrity of the links. (Bitbake rev: 533e1840d553c183e6ab37a350d492187c5eca96) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

bitbake: toaster: allow dots in user path names

2017-11-05T22:41:27+00:00

The dot '.' character should be allowed in the user paths for local non-git layers, DL_DIR, and SSTATE_DIR. [YOCTO #10650] (Bitbake rev: ca9b9ffc250eb3ece5af3d64ff5febef69d555b0) Signed-off-by: David Reyna Signed-off-by: Richard Purdie

bitbake: toaster: reserve HEAD from imported layers

2017-11-05T22:41:27+00:00

The HEAD reference in Toaster layers are reserved for the "Local Yocto Project" layers, stored at the top directory. Imported layers are not allowed to use this since they are managed differently - for example the 'remotes' will collide. Fix the add layer handler to not drop the data fields when it is a git repo. Explicitly inform the user when an internal Toaster error is returned via AJAX, so that they know why clicking the layer add button did not do anything. [YOCTO #9924] (Bitbake rev: 90fb89e5e3ada9e36ab0b2a5a0dbfd74f9be279f) Signed-off-by: David Reyna Signed-off-by: Richard Purdie

bitbake: tests/fetch: handle network failures gracefully

2017-11-05T22:37:29+00:00

If there is a network failure the return value from latest_versionstring() is ('','') which later causes an exception when comparing versions. Improve this by checking the return value and failing the test early. [ YOCTO #12053 ] (Bitbake rev: 4284d918dc7451f6a4d00be065369e86bbaec4d2) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

bitbake: bitbake: Fix return value checks from subprocess.call()'s

2017-11-05T22:37:29+00:00

Python function subprocess.call() returns the return value of the executed process. If return values are not checked, errors may go unnoticed and bad things can happen. Change all callers of subprocess.call() which do not check for the return value to use subprocess.check_call() which raises CalledProcessError if the subprocess returns with non-zero value. https://docs.python.org/2/library/subprocess.html#using-the-subprocess-module All users of the function were found with: $ git grep "subprocess\.call" | \ egrep -v 'if.*subprocess\.call|=\ +subprocess\.call|return.*subprocess\.call' Tested similar patch on top of yocto jethro. Only compile tested core-image-minimal on poky master branch. (Bitbake rev: aac956a0950c05bf58af1885474cd89bb9c8fbd1) Signed-off-by: Mikko Rapeli Signed-off-by: Richard Purdie

bitbake: Replace deprecated git branch parameter "--set-upstream"

2017-11-05T22:37:29+00:00

Since 2017-08-17 (git version 2.14.1.473.g3ec7d702a) using deprecated git branch parameter "--set-upstream" causes a fetcher error. Replace it by "--set-upstream-to". https://git.kernel.org/pub/scm/git/git.git/commit/?id=52668846ea2d41ffbd87cda7cb8e492dea9f2c4d says, it's deprecated since 2012-08-30 so hopefully all still supported host distributions have new enough git to support "--set-upstream-to". ERROR: PACKAGE do_unpack: Fetcher failure: ...; git -c core.fsyncobjectfiles=0 branch --set-upstream master origin/master failed with exit code 128, output: fatal: the '--set-upstream' option is no longer supported. Please use '--track' or '--set-upstream-to' instead. ERROR: PACKAGE do_unpack: Function failed: base_do_unpack (Bitbake rev: 698e36430761cd3cf81283d58ca5bb3426bd24dd) Signed-off-by: Andre Rosa Signed-off-by: Martin Jansa Signed-off-by: Richard Purdie

bitbake: toaster/highlight.pack.js: Fix corrupted file

2017-10-10T10:07:11+00:00

The newly added file in the last commit was corrupted, fix it. (Bitbake rev: 64e4f407bc235b774acf55f959b699ad3a5c9fa8) Signed-off-by: Richard Purdie

bitbake: toaster: Remove prettify

2017-10-10T08:42:04+00:00

Remove "prettify.js" and "prettify.css" due to license issues with Apache2. Replace with "highlight.pack.js" with its BSD3 License. [YOCTO #12206] (Bitbake rev: 8c86ec28abd406f6d62dee9f917ed1df47f7f301) Signed-off-by: Jason Wessel Signed-off-by: Brian Avery Signed-off-by: David Reyna Signed-off-by: Richard Purdie

bitbake: cooker: add BB_CMDLINE to enable access to UI command line with memres

2017-09-21T16:20:11+00:00

In OpenEmbedded's buildhistory class we want access to the bitbake command line that launched the build, and up to now we were simply using sys.argv from within the event handler to get that. Unfortunately that doesn't work in memory resident mode, since the event handler is naturally executing within the server and thus will give you the command that launched the bitbake server which is much less interesting. Add a dynamic variable BB_CMDLINE to provide access to this, set from sys.argv within the UI process in updateToServer(). (Note that BB_CMDLINE isn't currently passed through to the worker, so this is only really readable from event handlers plus any explicit getVariable calls - in theory an observe-only UI could read it for example.) Part of the fix for [YOCTO #11634]. (Bitbake rev: 85596c9af3bb6407159c6c8de229cbe275aa74ea) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie