linux/poky.git/bitbake/lib, branch scarthgap-5.0.15Mirror of git.yoctoproject.org/pokyhttps://git.enea.com/cgit/linux/poky.git/atom?h=scarthgap-5.0.152025-11-14T14:45:29+00:00bitbake: fetch2/wget: Keep query parameters in URL during checkstatus2025-11-14T14:45:29+00:00Philippe-Alexandre Mathieupamathieu@poum.ca2025-07-30T17:44:15+00:00urn:sha1:255271dfff26a08bf2e3768f4cd767e5f577255b
When recreating the uri in wget's checkstatus method, we only use the
scheme, host and path. This completely strips the query parameters from
the final URI and potentially breaks the checking functionality for
URLs that require query parameters (such as the AZ fetcher with SAS
token).
This bug was resolved on master in
`096301250455e2a83bdd818a56317c62436c9981`.
This patch is adapted to the scarthgap branch.
CC: Steve Sakoman <steve@sakoman.com>
(Bitbake rev: 8dcf084522b9c66a6639b5f117f554fde9b6b45a)
Signed-off-by: Philippe-Alexandre Mathieu <pamathieu@poum.ca>
Signed-off-by: Steve Sakoman <steve@sakoman.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Steve Sakoman <steve@sakoman.com>
bitbake: bb/fetch2/__init__.py: remove a DeprecationWarning in uri_replace()2025-11-14T14:45:29+00:00Bin Lanbin.lan.cn@windriver.com2025-09-05T15:36:32+00:00urn:sha1:324f29337bd8ba96e6b7c3860cfb7f8c6e422db9
There is the following warning when executing to bitbake linux-yocto:
bitbake/lib/bb/fetch2/__init__.py:464: DeprecationWarning: 'count' is passed as positional argument
This is because the 4th parameter of re.sub(pattern, repl, string, count=0, flags=0)
is a keyword parameter. We use keyword arguments for parameters that are not positional.
(Bitbake rev: c2a54aceab4c75cea6f8be16fe6d0caed12b32c4)
Signed-off-by: Bin Lan <bin.lan.cn@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Chris Laplante <chris.laplante@agilent.com>
Signed-off-by: Steve Sakoman <steve@sakoman.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Steve Sakoman <steve@sakoman.com>
bitbake: bitbake: Bump version to 2.8.12025-09-17T22:36:44+00:00Martin Jansamartin.jansa@gmail.com2025-09-03T09:54:55+00:00urn:sha1:3bb8b0dd371534c24d2cfab17b34789c877648a5
To indicate compatibility with python 3.14
[YOCTO #15858]
(Bitbake rev: 1c9ec1ffde75809de34c10d3ec2b40d84d258cb4)
Signed-off-by: Martin Jansa <martin.jansa@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Steve Sakoman <steve@sakoman.com>
bitbake: Use a "fork" multiprocessing context2025-09-17T22:36:44+00:00Joshua WattJPEWhacker@gmail.com2025-08-21T22:40:06+00:00urn:sha1:f00c4968ff34c6a23f2467f310b5aae31ab4947c
Python 3.14 changes the default multiprocessing context from "fork" to
"forkserver"; however bitbake heavily relies on "fork" to efficiently
pass data to the child processes. As such, make "fork" context in the bb
namespace and use it in place of the normal multiprocessing module.
Note that multiprocessing contexts were added in Python 3.4, so this
should be safe to use even before Python 3.14
[YOCTO #15858]
(Bitbake rev: 15d7448e04aa78c827d2cef9eb1a62bd6e0dd119)
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Martin Jansa <martin.jansa@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Steve Sakoman <steve@sakoman.com>
bitbake: utils: Optimise signal/sigmask performance2025-08-04T14:55:06+00:00Richard Purdierichard.purdie@linuxfoundation.org2025-07-29T18:43:09+00:00urn:sha1:511d3e23f5e769e669f767759ea936f33b2106cd
Running "time bitbake -pP idle" with a valid cache shows around 800,000
calls to enum creation from python's signal.py. We don't care about this
overhead and it adversely affects cache load time quite badly.
Try and use _signal directly, falling back to signal, which avoids
this overhead we don't need and makes cache loading much faster.
(Bitbake rev: 982645110a19ebb94d519926a4e14c8a2a205cfd)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
(cherry picked from commit ee5fce67ce35b025c68aa61e2e758903269ee346)
Signed-off-by: Chris Laplante <chris.laplante@agilent.com>
Signed-off-by: Steve Sakoman <steve@sakoman.com>
bitbake: bitbake: runqueue: Verify mcdepends are valid2025-08-04T14:55:06+00:00Mark Hatlemark.hatle@amd.com2025-07-29T18:43:08+00:00urn:sha1:bfb799ef2a961898ad43a5803ce75d2fdb9d6c0b
In order to avoid a potentially confusing backtrace, check that the mcdepend
is valid when we add it.
Add a test case to ensure invalid configurations are caught and trigger an
error.
[RP: Reworked test case to simplify and improve code]
(Bitbake rev: 9f6f049870e0ec829e171fe91ec8f7a092ddd2ab)
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
Signed-off-by: Mark Hatle <mark.hatle@kernel.crashing.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Chris Laplante <chris.laplante@agilent.com>
Signed-off-by: Steve Sakoman <steve@sakoman.com>
bitbake: test/fetch: Switch u-boot based test to use our own mirror2025-07-29T14:59:52+00:00Richard Purdierichard.purdie@linuxfoundation.org2025-07-22T10:13:21+00:00urn:sha1:0efe19beef4754ddf3322a8e44b5f891118ed322
The upstream servers are having issues so switch to our own shadow copy
of the repo.
(Bitbake rev: 86e7a58c0e9904c33b1b94dddc3d683c2da22d1a)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Steve Sakoman <steve@sakoman.com>
bitbake: ast: Change deferred inherits to happen per recipe2025-06-11T15:17:34+00:00Richard Purdierichard.purdie@linuxfoundation.org2025-06-06T10:44:43+00:00urn:sha1:320b76cc477069d619fd44d28608d9d2c1efe77c
Currently deferred inherits get processed once for all class extensions
as a minor speed optimisation. Unfortunately this limits our options for
being able to report deferred classes to our code.
There are two challenges with using our deferred classes in OE at present.
One is that PACKAGECONFIG values don't work well with class overrides like
class-native if there are deferred classes based on PACKAGECONFIG, such
as python support. The second is that toolchain selection is proving
problematic to implement due to interactions between the toolchain deferred
inherit, the class extensions and class overrides being very late.
By changing deferred inherits to be recipe extension specific, we open
the way to generate events and "peek" at where things will end up,
allowing the class overrides to be set earlier.
The class extension code is updated to use a deferred inherit for the
class extension inheriting so that it is still inherited last.
(Bitbake rev: 139f61fe9eec221745184a14b3618d2dfa650b91)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Steve Sakoman <steve@sakoman.com>
bitbake: gcp.py: remove slow calls to gsutil stat2025-06-11T15:17:34+00:00Etienne Cordonnierecordonnier@snap.com2024-08-23T08:41:08+00:00urn:sha1:4bca6762e5baa7c8cb90b4f2f13f4cb3e2e9942e
The changes of 1ab1d36c0af6fc58a974106b61ff4d37da6cb229 added calls to "gsutil stat" to avoid unhandled exceptions, however:
- in the case of checkstatus() this is redundant with the call to self.gcp_client.bucket(ud.host).blob(path).exists() which already returns True/False
and does not throw an exception in case the file does not exist.
- Also the call to gsutil stat is much slower than using the python client to call exists() so we should not replace the call to exists() with a call to gsutil stat.
- I think the intent of calling check_network_access in checkstatus() was to error-out in case the error is disabled. We can rather change the string "gsutil stat" to something else to make the code more readable.
- add a try/except block in download() instead of the extra call to gsutil
[RP: Tweak to avoid import until needed so google module isn't required for everyone]
(Bitbake rev: 59df5390381792aba4f3f5185000adf5109267fb)
Signed-off-by: Etienne Cordonnier <ecordonnier@snap.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Steve Sakoman <steve@sakoman.com>
bitbake: fetch2: Avoid deprecation warning2025-06-05T15:41:15+00:00Richard Purdierichard.purdie@linuxfoundation.org2025-06-05T11:10:18+00:00urn:sha1:fde11311089192d86e3ec787cb9925088652d6c0
>From re on python 3.13 onwards: "Passing count and flags as positional arguments is deprecated.
In future Python versions they will be keyword-only parameters."
Avoid the warning.
(Bitbake rev: 65b744bec9756ee2f43adbfa33c14899638e2b9f)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Steve Sakoman <steve@sakoman.com>