summaryrefslogtreecommitdiffstats
path: root/meta/conf/sanity.conf
AgeCommit message (Collapse)Author
2024-02-19sanity.conf: Require bitbake 2.7.3Richard Purdie
Due to hashserv API changes in siggen, we need bitbake 2.7.3. (From OE-Core rev: 7172fd527fde440f26dd6cc371cde2720dbaa366) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2024-01-26sanity: require bitbake 2.7.2 for the inherit_defer statementRoss Burton
(From OE-Core rev: 3f6840823656c5d36c1d7a467509ca13a79453a8) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2024-01-05sanity: Require bitbake 2.7.1Richard Purdie
We need bitbake 2.7.1 due to the find_siginfo changes. (From OE-Core rev: b8b6c3ebf6821b28dd1a350ccd74e47dc4bbd593) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-12-08sanity.conf: Require bitbake 2.6.1 for recent runqueue changeRichard Purdie
Require the presence of a recent change in bitbake 2.6.1 for runqueue setscene dependency handling improvements. (From OE-Core rev: a63bd8d5aa2cdcbfa899b1cfb8acad06dee44752) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-02-23sstate: Add check_for_interrupts() call functionality added in bitbakeRichard Purdie
Add in the new 'check' calls which mean that the code can exit from longer running code loops if requested by the user. This covers sstate checks and sstate manifest cleanup code which currently couldn't be interrupted by the user from the UI. Increase the minimum bitbake version which brings in this API. (From OE-Core rev: cb6c50689175668b66ffbe09ff8f250ba9a9034b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2022-06-02populate_sdk_ext: Fix race condition on bb_unihashes.datRichard Purdie
There is a race were the bb_unihashes.dat file may end up zero sized due to concurrent builds. Use recently added API within bitbake to copy the file safely. Also use the opportunity to remove hardcoded filepaths internal to bitbake from OE-Core. Bump the minimum bitbake version to match the API being used. (From OE-Core rev: 106a7e07057e4681e6fb06dfe9e28d2e183d667d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2022-02-21sanity.conf: Require bitbake version 1.53.1Richard Purdie
We require the code to handle variable renaming which is in this version of bitbake. (From OE-Core rev: e0f5938737727c3a2d738cd595a1f891c444c3c8) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-02sanity.conf: Require bitbake 1.51.1Richard Purdie
We require 1.51.1 which has the override syntax changes in it. (From OE-Core rev: 1da9f55ed84c3bec2dda080fb10613752dbd5685) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-02local.conf.sample: Bump version so users update their configRichard Purdie
It has been a while since we've done this but with the new syntax, users need to update their local.conf if based off the template. Update the versions to trigger this. (From OE-Core rev: 5452f1ba337685cf89d3429e08255450ab90b96f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-05-06sanity.conf: Require bitbake 1.51.0Richard Purdie
We're about to require bb.utils.rename() so depend on the correct version of bitbake. (From OE-Core rev: ed2b18ed6e76a3bc050a1c48526c114de5cb1a93) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-16bitbake.conf: Set as default task umask of 022Richard Purdie
Rather than trying to set the umask of every task to the correct value for determinism, set one value globally. This uses a new bitbake variable so bump the minimum version to match. This fixes strange determinism issues in at least quilt-ptest, valgrind-ptest and kernel-devsrc. (From OE-Core rev: b07b7deeae3d519d9998d583592f3e4f8f2802b3) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-10sanity.conf: Increase minimum bitbake version due to logging function changeRichard Purdie
(From OE-Core rev: 8ddfab7b185dbba171afce80260e5638eb06a769) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-06-17sanity.conf: Require bitbake 1.47.0 as the minimum versionRichard Purdie
The recent siggen changes need the new version of bitbake, update the minimum version to match (should also help the TERM environment change too). (From OE-Core rev: cb0213721893e5336995b38faffc7b65338a1b5f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-10-02sanity.conf: Bump minimum bitbake versionRichard Purdie
We need SignatureGeneratorUniHashMixIn from newer bitbake so bump the minimum version. (From OE-Core rev: 178e2d0ba8e645c5cd962b07bd7b31839cb269d3) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-08-06sanity.conf: Require bitbake 1.43.1Richard Purdie
We depend on a number of bitbake API changes, bump the min bitbake version requirement. (From OE-Core rev: 908cdd669b083b172f7cd53dd020629affee360c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-08-23sanity.conf: Update minimum bitbake version to 1.39.1Richard Purdie
We need this for the new break_hardlinks helper function. (From OE-Core rev: d6ccefd347bf31acf8d31996d796717acb4da74f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-07-21conf/sanity: Update minimum bitbake verison to 1.35.0 for server reworkRichard Purdie
(From OE-Core rev: b63fcffe8b6a3f94d4812cd03fb974e173eff3e5) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-04-10sanity: Require bitbake 1.33.4Richard Purdie
We need the bitbake bug in recrdeptask handling of missing tasks fixed in order to apply a fix for OE-Core. (From OE-Core rev: ef16288f3e1e801e5c763ed49fad8eb0c885183e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-03-31sanity.conf: Increase minimum version requirement to 1.33.3Richard Purdie
This pulls in changes to bb.utils.which() for HOSTTOOLS. (From OE-Core rev: 398fd35bfc2b4795067e25659841adaeea211809) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-03-01sanity: Require bitbake 1.33.2Richard Purdie
We want to update to a version with the bb.utils.filter() function. (From OE-Core rev: 6db26339522a22c3e3c13287ea0c9daf40c7c15e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-02-07sanity.conf: Update minimum version requirement for devtoolRichard Purdie
A recent devtool change needs bitbake changes so bump the minmium bitbake version requirement to match. (From OE-Core rev: e7b624c268cb917c00e88e8e9a6a87585eb98eac) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-01-27sanity.conf: Update minimum bitbake version requirements to 1.33.0Richard Purdie
Recipe specific sysroots and mutliconfig need recent versions of bitbake, look for version 1.33.0 as a minimum (From OE-Core rev: 3a617a4c66941cecbdccb6f410e1b0d8bfde9845) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-10-05sanity: Update minimum version requirement to 1.31.2Richard Purdie
This is so we can depend on the bb event threading fix which prevents event pipe corruption. (From OE-Core rev: 728269fe2839533a05e7f2532209466dc34e4174) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-08-18sanity: Require bitbake 1.31.1 for multi-config changesRichard Purdie
(From OE-Core rev: ecc8d346223030ee06aa6d83427f757982e948e4) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-03-31sanity: Require bitbake 1.29.1Richard Purdie
This is for the improved exec_func functionality. (From OE-Core rev: aedef9d6a585db9c1289f6117e72bdb576a1a304) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-28sanity: Improve configuration upgrade capabilities (support meta-yocto -> ↵Richard Purdie
poky transition) Right now, only one configuration file can be processed (conf/bblayers.conf) and it can only have one version number. This is a cause of immense friction between OE-Core and Poky since if one needs a version change, it shouldn't be forced on the other. We'd like to rename the meta-yocto layer (within the meta-yocto repository) to meta-poky. To do this, we need to correct the bblayers.conf file and that means changing the sanity version. After the pain this caused the last time, Paul made me promise never to have them out of sync between OE-Core and Poky, equally, having every distro changing config update OE-Core isn't scalable either. This patch changes the sanity upgrade method to list a more generic format: <config file>:<current version variable name>:<required version variable name>:<upgrade function> This in theory allows us to support upgrades to any of the core configuration files, and allow layers to extend them as needed. Files with the same name can be handled in different layers by setting a unique version name variable in the file itself. The upgrade code is only called if the version variable is set. To allow us to make the poky name change and use a new configuration file name, one last version bump is included for poky to handle the transition. (From OE-Core rev: 10fd24271e771ed12e36edcff0007caa1a4e67e4) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-12sanity: Bump minimum version to 1.29.0Richard Purdie
This requires the python expansion changes and allow SRCPV to work correctly without errors. (From OE-Core rev: 40efff29ad458937222c3dbeba070c525103907c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-06-10sanity.conf: Bump minimum bitbake version to 1.27.1 for sstate changeRichard Purdie
(From OE-Core rev: b925be92e8be2ab3b945069a699859809615c78f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-02-23classes/sanity: avoid bblayers version issue when switching between poky and ↵Paul Eggleton
other DISTRO values If you create a build directory with poky, or set DISTRO to "poky" and run bitbake, you'll get a bblayers.conf file with LCONF_VERSION set to 6. If you then set DISTRO to any other value where the new distro config doesn't pull in poky's config, e.g. "nodistro", you would then get a bblayers.conf version error which didn't immediately make sense. (The layer versions have been out-of-step ever since meta-yocto-bsp was split out of meta-yocto several years ago). This is just painful and we'd rather users didn't have to deal with it. Obviously it isn't an OE-Core problem per se, but a simple way to resolve it for everyone is to bump OE-Core's version to 6 with an automatic no-op upgrade. Also ensure that multiple upgrade functions (such as the poky one) have a chance to execute by not breaking out of the loop as we were before. Fixes [YOCTO #6139]. (From OE-Core rev: 2fdeee2fad69445b0d97148826c7b027820be63a) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-03sanity.conf: Update to require bitbake 1.25.0 as minimum versionRichard Purdie
This allows us to merge in the _defaultval changes. (From OE-Core rev: 3de8689ad4aa97acd36a76dda36c96697e2ab712) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-09-23sanity.conf: Update minimum bitbake version to 1.23.2 due to event changesRichard Purdie
(From OE-Core rev: b4e2a769e8def2e78ffca3f006a0cc88407aaeda) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-05-01sanity: Bump BitBake minimal version to 1.23.0Otavio Salvador
The metadata started using the bb.utils.contains_any which has been add in the BitBake 1.23.0 release, set this as the minimal version to ensure parsing compatibility. (From OE-Core rev: dea40c2850a32b5b67e90336f9565889f92dabe8) Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-12-20sanity.conf: Require bitbake 1.21.1 as a minumum version for deltask ↵Richard Purdie
functionality (From OE-Core rev: cdc6dfd497c7a96f8ccd666fe0b8970d5b906786) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-06-14sanity.conf: Update minimum bitbake version requirement to 1.19.1 for ↵Richard Purdie
bitbake-worker This is due to the need to rely on bitbake-worker being present going forwards. (From OE-Core rev: ccf4fe860096f4b2a56b51b612b2a1dcb3525e59) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-02-06sanity.conf: Update minimum bitbake versionRichard Purdie
We need this for the multiprocessing pool issues in python < 2.7.3 whic we now use in do_package. (From OE-Core rev: 027dc0ec80b570c79f4adb0deabb63bcf3c49b78) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-11-26sanity.conf: Increase minimum bitbake version requirement to 1.17.0 for ↵Richard Purdie
FILESDIR updates (From OE-Core rev: a85f990efd62e50e5ffaddf5c6d2703f18f11071) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-10-02sanity.conf: Require bitbake 1.16.0 (stable series) prior to release (and ↵Richard Purdie
for explode_dep_versions changes) (From OE-Core rev: bf334f01cb90483ba304b4a830d53e705637b87a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-07-19sanity.conf: Increase bitbake minimum version to 1.15.3Richard Purdie
(From OE-Core rev: c8937438a7b5d2aec4ae0318f5680f3a43979259) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-06-25sanity.bbclass: Increase LAYER_CONF_VERSION to match bblayers changeRichard Purdie
(From OE-Core rev: f4b5afe46ff018570c1949653eb6995428827f6f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-01-23sanity.conf: Incrase bitbake minimum version requirement to 1.15.1Richard Purdie
(From OE-Core rev: 383b1ef37c1c6f6b1be043ac61e338d75488c9a3) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-07-25sanity: Increase bitbake minium version to 1.13.3 for bb.utils.contains() ↵Richard Purdie
function (From OE-Core rev: 92a7e70feb1dfd882d13b5cb65e144d293ff291a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-06-30sanity.conf: Require bitbake version 1.13.2 at a minimumRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-06-09conf/sanity.conf: Set the minimum bitbake version correctly, we've needed ↵Richard Purdie
recent bitbake features for a while (From OE-Core rev: f6a38cd75edb46858da6950b5ec029db8a12d801) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-04-21sanity.conf: Rename POKY_CONF_VERSION -> LOCALCONF_VERSION and make sanity ↵Richard Purdie
versions weak assignment allowing the distro to override (From OE-Core rev: 9a5a783fb131aef98540a81ea6697031a7a429e0) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-02-25Emenlow Removal from Poky Core: meta-emenlowBeth Flanagan
Removing Emenlow from poky core as it is now in meta-intel as a BSP layer [BUGID #769] Signed-off-by: Beth Flanagan <elizabeth.flanagan@intel.com>
2010-12-20sanity.bbclass: allow minimisation of impact of more invasive sanity checksPaul Eggleton
Add a mechanism to avoid running more invasive checks every time bitbake is invoked. Adds a file in conf/ (i.e. under user's build directory) that tracks a new variable SANITY_VERSION (set in sanity.conf) as well as TMPDIR and SSTATE_DIR, allowing checks to be run when these are changed. Fixes [BUGID #562] Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
2010-09-17bblayers.conf.sample: remove meta-moblin from default layersScott Garman
This fixes [BUGID #273] Signed-off-by: Scott Garman <scott.a.garman@intel.com>
2010-07-22sanity.conf: Update layer version after the last commitRichard Purdie
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-06-07sanity.bbclass: version each of the files in the build/conf/ directoryJoshua Lock
We already have versioning of the local.conf file but it's entirely plausible for the bblayers.conf and site.conf to change incompatibly so we should version those too. Signed-off-by: Joshua Lock <josh@linux.intel.com>
2010-04-30Version the build configuration directoryJoshua Lock
The addition of BBLAYERS changes the build/conf directory to be incompatible with the "old way" in the Purple release. As such things are likely to occur in future we should bersion the build/conf directory through local.conf Signed-off-by: Joshua Lock <josh@linux.intel.com>