There is a list of environment variable names that need to be exported when executing external commands, such as 'http_proxy'. To avoid duplication, make this a top-level variable. Also add

Instead of just exporting the proxy variables when calling into urllib, use bb.utils.environment() to export all of the known variables that are needed for proper connectivity. Specifically, this

bb.utils.environment() is a context manager to alter os.environ inside a specific block, restoring it after the block is closed. Signed-off-by: Ross Burton <ross.burton@...> ---

If run on an empty build directory, taskexp wasn't working as it didn't send the current environment to the server. This means HOSTTOOLS in oe-core couldn't be built and gave an error. Add the missing

When an exception occurs at startup, show it to the user. [YOCTO #14408] Signed-off-by: Richard Purdie <richard.purdie@...> --- lib/bb/ui/taskexp.py | 4 ++++ 1 file changed, 4

If an exception occurs in early setup, bitbake could just hang. Return the exception rather than doing that. [YOCTO #14408] Signed-off-by: Richard Purdie <richard.purdie@...> ---

Currently the code can just show nothing as the exception if there was a double fault, which in this code path is quite likely. This leads to an error log which effectively says "it failed" with no

Updates the Vim syntax highlighting to account for the new override syntax and also highlight "append" and "prepend" overrides Signed-off-by: Joshua Watt <JPEWhacker@...> ---

Thanks. I couldn't get the patch to apply for some reason (line wrapping?) so I just fixed up the references. This one shouldn't be changed, at least not at this point as name is

Fix some references that missed during the overrides syntax migration or were incorrect. Thanks to Quentin Schulz <foss@...> for the patch. Signed-off-by: Richard Purdie

Fix some references missed during the overrides syntax migration. Thanks to Quentin Schulz <foss@...> for the patch. Signed-off-by: Richard Purdie <richard.purdie@...> ---

That isn't quite the same thing though as for example what if value was  False? You'd hope that we didn't have such situations but I coded it that way so it would cause an error if it occurred,

On Mon, Aug 2, 2021 at 12:58 PM Steve Sakoman via lists.openembedded.org <steve=sakoman.com@...> wrote: And I see Richard beat me to it :-) Steve

Hmmm . . . I thought I had grabbed this, but clearly not! I'm on it! Steve

Hi Richard, [...] I can suggest the following additional changes. Please note that there are two sections for which I have doubts about their correctness. They are preceded by a FIXME FIXME FIXME

Ping. -- Regards, Denys Dmytriyenko <denis@...> PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964 Fingerprint: 25FC E4A5 8A72 2F69 1186 6D76 4209 0272 9A92 C964

Yeah, it took a moment too long in my head to compute this change :-) Sorry for the noise. Patch is correct IMHO, although I'm not sure about the fallout of this change, as any kind of string

The code change turns what was a return value of "" into a return value of None. I  did run the test before and after the change and it seems to be correct? Put another way, sstting

Maybe I'm not seeing it but to me the test doesn't match the changes made. If the code change turns None into "", how can the assert ever work here? I would have expected assertNotEqual or similar