This should have been 2.11 previously but the numbers got confused.
Correct it for release.
(From OE-Core rev: d4a7c9d1e72dd6e45458ac6590e76f10805c0818)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We need a version of bitbake with the fetcher revision changes in it,
update the minimum version accordingly.
(From OE-Core rev: ec54f71dcf8166c725ff89f8689c177431bd0b52)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We need a recent siggen change in bitbake to allow SPDX to work
better.
(From OE-Core rev: 3d501e4b496be86b0089167af2f49cb750fc7ea2)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
We need this for the new break_hardlinks helper function.
(From OE-Core rev: d6ccefd347bf31acf8d31996d796717acb4da74f)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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>
This pulls in changes to bb.utils.which() for HOSTTOOLS.
(From OE-Core rev: 398fd35bfc2b4795067e25659841adaeea211809)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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>
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>
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>
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>
This is for the improved exec_func functionality.
(From OE-Core rev: aedef9d6a585db9c1289f6117e72bdb576a1a304)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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>
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>
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>
This allows us to merge in the _defaultval changes.
(From OE-Core rev: 3de8689ad4aa97acd36a76dda36c96697e2ab712)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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>
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>
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>
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>
