summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* man-db: update to 2.9.0Alexander Kanavin2019-12-161-2/+2
| | | | | | | (From OE-Core rev: dd0c62ba4c1ade7aaa4760f351cf9f76c0aca91e) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* man-pages: update to 5.04Alexander Kanavin2019-12-161-2/+2
| | | | | | | (From OE-Core rev: 6451a900ce184e7d78785dbdfced9c7812e33374) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* parted: update 3.2->3.3Alexander Kanavin2019-12-1612-737/+117
| | | | | | | | | | | | | | | | | 0001-Unset-need_charset_alias-when-building-for-musl.patch is no longer necessary as upstream has removed the code. dm_check.patch is replaced with 0002-tests-use-skip_-rather-than-skip_test_-which-is-unde.patch Rework ptests, in particular remove the generated Makefile from the layer, and use the upstream Makefile. Ptest pass rate is 100%. (From OE-Core rev: 5dc6529d0b5b8b1bef12b90008f0a25612bd453e) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libxml2: update to 2.9.10Alexander Kanavin2019-12-162-32/+34
| | | | | | | (From OE-Core rev: de72e0440bc36fab09a7e3c13d3967c97dcda66b) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* glide: update to 0.13.3Alexander Kanavin2019-12-161-1/+1
| | | | | | | (From OE-Core rev: 0270b64a69f30d36f03ce8de819fa703da84ecbb) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* puzzles: update to latest revisionAlexander Kanavin2019-12-165-84/+35
| | | | | | | | | Remove 0001-Use-labs-instead-of-abs.patch as problem is fixed upstream. (From OE-Core rev: 6ecc17f83d57d08bbeb6366cb586993a8844c8a6) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dos2unix: update to 7.4.1Alexander Kanavin2019-12-161-3/+2
| | | | | | | | License-Update: copyright years (From OE-Core rev: 248e777ac61e90da061e336acbcd23e8e71cd0e4) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstatesig: Further optimiseRichard Purdie2019-12-161-3/+2
| | | | | | | | Optimise the call into the parent function to be only when needed. (From OE-Core rev: 198bacaa1068fd68075d9182318fe64e9809dd36) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts/oe-build-perf-test: Use python3 from the environmentRichard Purdie2019-12-151-1/+1
| | | | | | | | | On test machines we have python3 available at alternative locations. Use these rather from the evnrionment rather than a hardcoded path. (From OE-Core rev: 81ee68f39a155c79443d45321ce4b81d9bf6675e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstatesig: Optimise get_taskhash for hashequivRichard Purdie2019-12-151-2/+11
| | | | | | | | | | | With hashequiv the get_taskhash function is called much more regularly and contains expensive operations. This these don't change based upon hash in a given build, improve the caching within the function to reduce overhead. (From OE-Core rev: de98cfe3cde4b8d5f4b163b5fba3f129651ef06a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* conf/machine/x86-base: use wic instead of liveRoss Burton2019-12-151-1/+1
| | | | | | | | | | Use wic instead of the live/hddimg filesystem type for x86 machines, as it produces better filesystems and doesn't have a hard limit of 4GB. (From OE-Core rev: 04e4e93efa4d8e2bdde950fe95c2fd95f89c13e7) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildstats: Replace 'is' with '==' in python condition check expressionKhem Raj2019-12-151-1/+1
| | | | | | | | | | | | | | | python 3.8 has started to throw this as a warning but usage is wrong see [1], it seems to be working by accident and not design. Fixes SyntaxWarning: "is" with a literal. Did you mean "=="? [1]: https://bugs.python.org/issue34850 (From OE-Core rev: c3cb6bc21f3f84e2ed103b6438516ab85222faa9) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libjpeg-turbo: Build reproduciblyJoshua Watt2019-12-151-0/+2
| | | | | | | | | | Configures the options passed to nasm to remove build paths in the generated object files. (From OE-Core rev: 9119a882adbf19df9f47f66cebaa7f730d3e9462) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* nasm: Add debug-prefix-map optionJoshua Watt2019-12-153-0/+444
| | | | | | | | | | | Adds an option to nasm to change the prefix for file paths encoded in the object files. This allows builds to be reproducible regardless of the build directory. (From OE-Core rev: ad5c914933c7b38296dcb8bba3c36aed45aacc32) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Revert "go: Reset unneeded GOARCH variables for native recipe"Khem Raj2019-12-151-10/+0
| | | | | | | | | This reverts commit 4825eede606b075d0d529b38d6162999f1dec506. (From OE-Core rev: 18b90967bd367263280ec871be84e67e3eed11fa) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* goarch: Remove target specific dependenciesKhem Raj2019-12-151-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | goarch is used in all classes of recipes ranging from native to target, therefore its best to contain the variables and not spill over into recipe classes where they can adversely affect shared state reuse e.g. go-native currently gets TUNE_FEATURES into dependency chain of referenced variables which means go-native gets rebuilt when we change from qemuarm to qemux86 machine types since TUNE_FEATURES is defined with DEFAULTTUNE which would change as machines are switched These variables are specific to arm/mips/x86 so marking them with appropriate overrides for native recipes will be right thing here Chose 'hardfloat' for mips which is default too, 7 for arm and sse2 for x86 somehow go-native bootstrap compiler (1.4) still needs them so feed commonly used values or defaults. Fixes ERROR: go-native different signature for task do_configure.sigdata between qemux86copy and qemuarm ... List of dependencies for variable TUNE_FEATURES changed from '{'DEFAULTTUNE', 'TUNE_FEATURES_tune-core2-32'}' to '{'DEFAULTTUNE', 'TUNE_FEATURES_tune-armv7vethf-neon'}' changed items: {'TUNE_FEATURES_tune-core2-32', 'TUNE_FEATURES_tune-armv7vethf-neon'} (From OE-Core rev: 83eebf5577dd0a23be937375c1a8a15e3da4fa64) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cronie:fix SRC_URI pathStefano Babic2019-12-151-1/+1
| | | | | | | (From OE-Core rev: 06ce57157a43f5988e1a0c6bc147fec7b55e63ec) Signed-off-by: Stefano Babic <sbabic@denx.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bluez5: disable debug output in ptestsAlexander Kanavin2019-12-151-1/+1
| | | | | | | | | | This makes the log very large and breaks the ptest result parser. (From OE-Core rev: 78221af4c0297e0278c042eed390ad0e53f2548a) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bluez: update 5.50 -> 5.52Alexander Kanavin2019-12-159-982/+16
| | | | | | | | | | | | | Drop a big pile of backports. Disable zsh completions, as they're unlikely to be useful. (From OE-Core rev: dad8cd50bcc4203a65d153dc2445502c1e728975) (From OE-Core rev: 1a31a31a3bd68f027ba0a13f8e66ce92104a4d4c) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kbd: avoid vlock conflict with busyboxHongxu Jia2019-12-151-1/+2
| | | | | | | | | | | | | | | | | | | | | | busybox as well as vlock utility from meta-oe provides vlock utility which can conflict when with kbd if pam is a enabled distro_feature Fixes image build errors update-alternatives: Error: not linking <rootfs>/usr/bin/vlock to /bin/busybox.suid since <rootfs>/usr/bin/vlock exists and is not a link ERROR: yoe-qt5-wayland-image-1.0-r0 do_rootfs: Postinstall scriptlets of ['busybox'] have failed. If the intention is to defer them to first boot, then please place them into pkg_postinst_ontarget_${PN} (). Deferring to first boot via 'exit 1' is no longer supported. (From OE-Core rev: 08636708f6ca677a6ee6c88fa2999c7b70b7d474) Signed-off-by: Khem Raj <raj.khem@gmail.com> The vlock doesn't exist if PAM isn't enabled. Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* reproducible_build_simple: inherit podfixRoss Burton2019-12-151-0/+1
| | | | | | | | | | When doing reproducible builds inherit podfix to remove the possibility of differing Perl versions causing manpages to change. (From OE-Core rev: 5dc43edab4787906f2c9f51e51bf78d1dc966286) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* podfix: class to remove Pod::Man versions from manpagesRoss Burton2019-12-151-0/+32
| | | | | | | | | | | | | | Manpages generated by Pod::Man contain the version number, which isn't reproducible if we're using the host Perl to generate manpage. One option is to always depend on perl-native when generating manpages but this is a heavy dependency, so instead strip out the versions in do_install(). (From OE-Core rev: 18d8e5ac689d6eb6098f68ac785f43e9d5f5938a) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* runqemu: handle tap device creation failure properlyPaul Eggleton2019-12-151-2/+6
| | | | | | | | | | | | If we fail to run the command to generate the tap devices then we should show a reasonable message and then exit, without showing a traceback. "return 1" at this point in the code does nothing because the caller doesn't check the return, so just use sys.exit(). (From OE-Core rev: 47e40fdd7dd58bde4e017e2375c16450fcb14eca) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* runqemu: log parameters correctly within testimagePaul Eggleton2019-12-151-12/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It is not a good idea to mix logging and calls to print() - if the output is being captured the result can be that the two types of output are not recorded contiguously; this could be observed if an error occurred running runqemu from inside testimage: ---------- snip ---------- ERROR: core-image-minimal-1.0-r0 do_testimage: Output from runqemu: runqemu - INFO - Continuing with the following parameters: runqemu - INFO - Setting up tap interface under sudo sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper runqemu - ERROR - Setting up tap device failed: Command '('sudo', '/home/paul/poky/poky/scripts/runqemu-ifup', '1000', '1000', '/home/paul/poky/poky/build/tmp/work/x86_64-linux/qemu-helper-native/1.0-r1/recipe-sysroot-native/usr/bin')' returned non-zero exit status 1. Run runqemu-gen-tapdevs to manually create one. runqemu - INFO - Cleaning up KERNEL: [/home/paul/poky/poky/build/tmp/deploy/images/qemux86-64/bzImage--5.2.20+git0+bd0762cd13_dd25a04fc5-r0-qemux86-64-20191205213021.bin] MACHINE: [qemux86-64] FSTYPE: [ext4] ROOTFS: [/home/paul/poky/poky/build/tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64.ext4] CONFFILE: [/home/paul/poky/poky/build/tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64.qemuboot.conf] ---------- snip ---------- What we should see here is the KERNEL, MACHINE, etc. lines appearing immediately after the "Continuing with the following parameters:" line as they do when you run runqemu directly. If we put all of the lines through the logger instead then it works properly. (From OE-Core rev: ca64a3d490fbe1bf87c9f1dd6d87a1ecdeba8325) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa: qemu: ensure we print runqemu output in the event of failurePaul Eggleton2019-12-151-2/+2
| | | | | | | | | | | | If we get here in the code it's because runqemu has failed, this is not a debug situation - we need to see the output, so print it as an error. Fixes [YOCTO #13681]. (From OE-Core rev: c1def38c680d64c992839166bbf9bec51eb0788a) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa: qemu: fix width of top output in host dumpPaul Eggleton2019-12-151-0/+1
| | | | | | | | | | | | | | | | | | If runqemu fails, there is some logic to run a set of commands to dump various bits of information that might help debug the issue (particularly in a busy situation such as on the autobuilder). One of those commands is "top -bn1", however top restricts the output to the width of the calling terminal, and for whatever reason this is a little restrictive when called from inside testimage, so set COLUMNS in the environment to a high value to fix it. (Another way is to use the -w option, but that is not supported by our default busybox configuration so it will then fail when this same list of commands is used on the target). (From OE-Core rev: 07da998f5aa6c3f5ffeee5150fc579e8a1051ba4) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa: qemu: ensure that host dump commands can be run properlyPaul Eggleton2019-12-151-1/+3
| | | | | | | | | | | | | | | | | If runqemu fails, there is some logic to run a set of commands to dump various bits of information that might help debug the issue (particularly in a busy situation such as on the autobuilder). However, when we try to run these we are inside the normal build environment which restricts commands to be run on the host to those specified in HOSTTOOLS. Since this isn't a place where host contamination is going to be a problem, override PATH to a reasonable default so that we run the actual host tools directly to avoid the issue. (Logically we would want to use the original PATH value here, but it is not easily accessible.) (From OE-Core rev: 3f6dcf67bccb4f0fc1a9a64e02bd0e2da620ad0e) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/systemd_boot: Ensure wic-tools are availableRichard Purdie2019-12-151-3/+5
| | | | | | | | | | If mtools isn't present on the underlying system this test would fail. Ensure wic-tools is available in a similar way to other wic selftests in OE-Core. (From meta-yocto rev: 5d48d41a3f93ca0e7085ce3c0f646b1d0c8d52d1) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* selftest/systemd-boot: test against wic imageChee Yang Lee2019-12-151-5/+4
| | | | | | | | | | | | effort to remove live for x86 from default image see https://bugzilla.yoctoproject.org/show_bug.cgi?id=11291 reduce dependency on hddimg, change the test to based on wic image. (From meta-yocto rev: 8cce1493f625664c21c156a36d9c9fb6d4dd4b1f) Signed-off-by: Chee Yang Lee <chee.yang.lee@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* genericx86: wic wks do not hardcode loaderChee Yang Lee2019-12-152-2/+3
| | | | | | | | | | | replace .wks with .wks.in and refer loader to EFI_PROVIDER to enable different bootloader. soft assign default EFI_PROVIDER "grub-efi" for genericx86. (From meta-yocto rev: 11ecd2febed95e923c8cc68e2c438cd846a88d02) Signed-off-by: Chee Yang Lee <chee.yang.lee@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: siggen: Fix performance issue in get_unihashRichard Purdie2019-12-151-3/+3
| | | | | | | | | | There is a significant performance issue in get_unihash(). The issue turns out to be the lookups of setscene tasks. We can fix this by using a set() instead of the current list. (Bitbake rev: 1e561672d039ebfb8cd0e0654a44dcf48513317c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to master head revision3.1_M1Richard Purdie2019-12-121-1/+1
| | | | | | (From OE-Core rev: 0f04e81c797d5d337ece4e8638a6b71c75bc0a00) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: Revert "siggen: Fix hashequiv performance issues"Richard Purdie2019-12-121-13/+14
| | | | | | | | This reverts commit c4b8440f730c33eaf9f818b856ae81b2f1017fec. The logic in this change is flawed and needs to be re-thought. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to master head revisionRichard Purdie2019-12-121-1/+1
| | | | | | (From OE-Core rev: 0980868fb1a315b2bb2ccd8d36873808056cb1ee) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: siggen: Fix hashequiv performance issuesRichard Purdie2019-12-121-14/+13
| | | | | | | | | | | | | | | | | | | We're seeing huge slowdowns on large builds on the autobuilder. A qemux86 world build was running really slowly, a primary feature was lots of rehashing going on due to an sstate change which caused a rebuild when all output should be identical. This was traced to the hundreds of thousands of calls to get_unihash() from get_taskash(). If we simplify the unitaskhashes data structure, we can bypass the function call and access the data directly. In local profile charts, this significanly sped up process_possible_migrations(), both on profiles and visually. Whilst this change doesn't aid readability, it does solve an otherwise huge performance issue. (Bitbake rev: c4b8440f730c33eaf9f818b856ae81b2f1017fec) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: runqueue: Batch scenequeue updatesJoshua Watt2019-12-121-4/+7
| | | | | | | | | | | | Batch all updates to scenequeue data together in a single invocation instead of checking each task serially. This allows the checks for sstate object to happen in parallel, and also makes sure the log statement only happens once (per set of rehashes). (Bitbake rev: db033a8f8a276d864bdb2e1eef159ab5794a0658) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to master head revisionRichard Purdie2019-12-111-1/+1
| | | | | | (From OE-Core rev: cb5e746a2398d70b14a14ada7cef82bfd5e80d0e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate: Ensure mkdir happens before mktempRichard Purdie2019-12-111-3/+2
| | | | | | | | | | This avoids a directory not present error. Fix a comment typo whilst here. (From OE-Core rev: 1360d8d7d99b70a80c8cdbc1fc6d9e6752483139) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to master head revisionRichard Purdie2019-12-111-1/+1
| | | | | | (From OE-Core rev: bf6ee2b39e2294f7f3719f7d373af9e0ec2979e9) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate: Ensure target sstate directory exists if unihash changesRichard Purdie2019-12-111-2/+2
| | | | | | | | | The previous patches meant the mkdir might no longer match the final target directory. Fix this. (From OE-Core rev: 0af4dae84099e8632a9ea6a4afdbea2f232bb170) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to master head revisionRichard Purdie2019-12-101-1/+1
| | | | | | (From OE-Core rev: 76e84ce1815ff273647657eeafb5149d6016730b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate: Ensure SSTATE_PKG is reloaded when handling siginfoRichard Purdie2019-12-101-1/+2
| | | | | | | | | STATE_PKG may have been changed by sstate_report_unihash so don't cache the variable's value. (From OE-Core rev: be29a25400c4ea285ab3f588c5831f00ba5d4f63) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to master head revisionRichard Purdie2019-12-101-1/+1
| | | | | | (From OE-Core rev: 093a1971f2ae12e1f514598da984f268607e550b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Revert "bluez: update 5.50 -> 5.52"Richard Purdie2019-12-109-16/+982
| | | | | | | | | This reverts commit dad8cd50bcc4203a65d153dc2445502c1e728975. It is causing performance problems in ptest, taking hours (~18) to parse the ptest runner logs. Log output increased from ~4MB to ~65MB. Revert until we can deal with the performance issue. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to master head revisionRichard Purdie2019-12-101-1/+1
| | | | | | (From OE-Core rev: 42719edc86ac2013280a34f1c58ca83726cec04a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate: Stop overwriting SSTATE_PKGRichard Purdie2019-12-101-4/+4
| | | | | | | | | | | | Its rather antisocial to overwrite SSTATE_PKG with an expanded form for the variable and it stops the value of BB_UNIHASH being changed when the package is written out. Instead of expanding the variable, append to it instead to avoid this rather hard to figure out behaviour and allow the siggen code to behave as expected. (From OE-Core rev: 62eca02024b4c44d618ab9bcf87a3166c886dadb) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to master head revisionRichard Purdie2019-12-101-1/+1
| | | | | | (From OE-Core rev: 85b7a3d5ec553ef71fa6060b99afbdccdc87dd37) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: siggen: Ensure new unihash propagates through the systemRichard Purdie2019-12-091-0/+1
| | | | | | | | | | Its possible the new unihash may not exist in sstate. Currently the code would create an sstate object with the old hash however this updates it to create the object with the new unihash. (Bitbake rev: abcaa1398031fa5338a43859c661e6d4a9ce863d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to master head revisionRichard Purdie2019-12-091-1/+1
| | | | | | (From OE-Core rev: efc1945a95897539a491f9e833ba07e653fdb1d4) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cve-check: Switch to NVD CVE JSON feed version 1.1Niko Mauno2019-12-092-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Switch to recently released version 1.1 of NVD CVE JSON feed, as in https://nvd.nist.gov/General/News/JSON-1-1-Vulnerability-Feed-Release it is mentioned that Due to changes required to support CVSS v3.1 scoring, the JSON vulnerability feeds must be modified. This will require the consumers of this data to update their internal processes. We will be providing the JSON 1.1 schema on the data feeds page and the information below to prepare for this transition. ... The JSON 1.1 data feeds will be available on September 9th, 2019. At that time the current JSON 1.0 data feeds will no longer available. This change was tested briefly by issuing 'bitbake core-image-minimal' with 'cve-check.bbclass' inherited via local.conf, and then comparing the content between the resulting two 'DEPLOY_DIR_IMAGE/core-image-minimal-qemux86.cve' files, which did not seem to contain any other change, except total of 167 entries like CVSS v3 BASE SCORE: 0.0 were replaced with similar 'CVSS v3 BASE SCORE:' entries which had scores that were greater than '0.0' (up to '9.8'). (From OE-Core rev: cc20e4d8ff2f3aa52a2658404af9a0ff358cc323) Signed-off-by: Niko Mauno <niko.mauno@iki.fi> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-09-29 01:24:27 +0000