linux/poky.git/bitbake, branch krogoth-enea

bitbake: siggen: Ensure taskhash mismatches don't override existing data

2017-02-10T11:21:35+00:00

We recalculate the taskhash to ensure the version we have matches what we think it should be. When we write out a sigdata file, use the calculated value so that we don't overwrite any existing file. This leaves any original taskhash sigdata file intact to allow a debugging comparison. (Bitbake rev: dac68af6f4add9c99cb7adcf23b2ae89b96ca075) Signed-off-by: Richard Purdie Minor fixup Signed-off-by: Armin Kuster Signed-off-by: Sona Sarmadi

bitbake: siggen: Pass basehash to worker processes and sanity check reparsing result

2017-02-10T11:21:35+00:00

Bitbake can parse metadata in the cooker and in the worker during builds. If the metadata isn't deterministic, it can change between these two parses and this confuses things a lot. It turns out to be hard to debug these issues currently. This patch ensures the basehashes from the original parsing are passed into the workers and that these are checked when reparsing for consistency. The user is shown an error message if inconsistencies are found. There is debug code in siggen.py (see the "Slow but can be useful for debugging mismatched basehashes" commented code), we don't enable this by default due to performance issues. If you run into this message, enable this code and you will find "sigbasedata" files in tmp/stamps which should correspond to the hashes shown in this error message. bitbake-diffsigs on the files should show which variables are changing. (Bitbake rev: 46207262ee6cdd2e49c4765481a6a24702ca4843) Signed-off-by: Richard Purdie Fixed up do to python3 changes not being in krogoth. Signed-off-by: Armin Kuster Signed-off-by: Sona Sarmadi

bitbake: build: Ensure we preserve sigbasedata files as well as sigdata ones

2017-02-10T11:21:35+00:00

We don't remove sigdata files, we also shouldn't remove sigbasedata files as this hinders debugging. (Bitbake rev: 06e7c00f2e1ddda6a2632ec2354a3c8f5c34562d) Signed-off-by: Richard Purdie Signed-off-by: Armin Kuster Signed-off-by: Sona Sarmadi

bitbake: bitbake: toaster: settings set ALLOWED_HOSTS to * in debug mode

2016-11-28T14:23:48+00:00

This is a backport of 7c3a47ed8965c3a3eb90a9a4678d5caedbba6337 >From the commit to master: As of Django 1.8.16, Django is rejecting any HTTP_HOST header that is not on the ALLOWED_HOST list. We often need to reference the toaster server via a fqdn, if we start it via webport=0.0.0.0:8000 for instance, and are hitting the server from a laptop. This change does reduce the protection from a DNS rebinding attack, however, if you are running the toaster server outside a protected network, you should be using the production instance. [YOCTO #10586] (Bitbake rev: 449dc9b955dfbe048e380f5ab9fd61c3d1489dad) Signed-off-by: brian avery Signed-off-by: Richard Purdie

bitbake: fetch: copy files with -H

2016-11-08T23:47:15+00:00

When using a PREMIRROR with plain (non-unpack) files, a SRC_URI like SRC_URI = "file://devmem2.c" will cause devmem2.c to be a symlink in the WORKDIR pointing to the local PREMIRROR. Trying to apply a patch on this file will either modify the file on the PREMIRROR or will fail due to sanity checks: ERROR: devmem2-1.0-r7 do_patch: Command Error: 'quilt --quiltrc /cache/build-ubuntu/sysroots/x86_64-oe-linux/etc/quiltrc push' exited with 1 Output: Applying patch devmem2-fixups-2.patch File devmem2.c is not a regular file -- refusing to patch (Bitbake rev: e82862ba8fedb2c5cd478c731b3d259d16c6e3d8) Signed-off-by: Enrico Scholz Signed-off-by: Richard Purdie

bitbake: bb.event: fix infinite loop on print_ui_queue

2016-11-08T23:47:14+00:00

If bitbake ends before _uiready and bb.event.LogHandler was add to the bitbake logger it causes an infinite loop when logging something. The scenario is print_ui_queue is called at exit and executes the log handlers [2] one of them is bb.event.LogHandler this handler appends the same entry to ui_queue causing the inifine loop [3]. In order to fix a new copy of the ui_queue list is created when iterate ui_queue. [YOCTO #10399] [1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=10399#c0 [2] http://git.openembedded.org/bitbake/tree/lib/bb/event.py?id=41d9cd41d40b04746c82b4a940dca47df02514fc#n156 [3] http://git.openembedded.org/bitbake/tree/lib/bb/event.py?id=41d9cd41d40b04746c82b4a940dca47df02514fc#n164 (Bitbake rev: bb56a8957255999b9ffd1408d249cc5b715b5a3a) Signed-off-by: Aníbal Limón Signed-off-by: Richard Purdie

bitbake: event: prevent unclosed file warning in print_ui_queue

2016-11-08T23:47:14+00:00

Use logger.addHandler(), rather than assigning an array of Handlers to the loggers handlers property directly, to avoid a warning from Python 3 about unclosed files: $ bitbake Nothing to do. Use 'bitbake world' to build everything, or run 'bitbake --help' for usage information. WARNING: /home/joshuagl/Projects/poky/bitbake/lib/bb/event.py:143: ResourceWarning: unclosed file <_io.TextIOWrapper name='/home/joshuagl/Projects/poky/build/tmp/log/cooker/qemux86/20161004094928.log' mode='a' encoding='UTF-8'> logger.handlers = [stdout] (Bitbake rev: 775888307dc2917ef4b52799cc1600a6b3a01abe) Signed-off-by: Joshua Lock Signed-off-by: Richard Purdie

bitbake: event.py: output errors and warnings to stderr

2016-11-08T23:47:14+00:00

All logging messages are printed on stdout when processing UI event queue. This makes it impossible to distinguish between errors and normal bitbake output. Output to stderror or stdout depending on log level should fix this. (Bitbake rev: c4029c4f00197804511fc71e1190d34eb120212a) Signed-off-by: Ed Bartosh Signed-off-by: Richard Purdie

bitbake: lib/bb/tests/fetch: remove URL that doesn't exist anymore

2016-09-13T15:19:46+00:00

The CUPS ipptool URL we were checking now redirects to github where the tarball isn't present, so remove it from the test suite. (Bitbake rev: e64564bcaa7331f505baa5209fef1f50dfda1469) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

bitbake: toaster: Fix adding of bitbake variables containing ':'

2016-08-31T19:37:44+00:00

This fix is a backport from toaster-next. Krogoth Toaster is unable to add a variable containing ':' and fails with the following error message: error on request: too many values to unpack Traceback (most recent call last): File "bitbake/lib/toaster/toastergui/views.py", line 2171, in xhr_configvaredit variable, value = t.spli(":") ValueError: too many values to unpack. [YOCTO #10170] (Bitbake rev: bee144eeed6c08ec2829533e82f94405058ce453) Signed-off-by: Alexander Egorenkov Signed-off-by: Ed Bartosh Signed-off-by: Richard Purdie