But this 2nd example is what might be difficult to spot and most likely needs the leading space as well, right? Especially when there is some override like VAR2:append:machine-foo:distro-foo =

I was just going to comment with the same idea. Much earlier in my OE journey, this bit me often and was a source of confusion.

Hi All, I would also emit a (switchable on / off) warning for VAR_append and VAR:append without a space when VAR contains spaces already i.e.: VAR = "opt1 opt2" VAR:append = "opt3" --> warning VAR2

Hi Richard, Using the old syntax :D? I'm all for removing potential areas of confusion, so +1. On that topic, if I'm not mistaken, the same applies to: FOO:.*{append, prepend,

Lovely! -- Marco

I think this is a good change, since it clarifies the functionality and removes undefined behavior that sort of seemed to achieve a valid operation.

Agreed, this combination isn't really needed and it's easy to fix relatively few cases which slipped into various layers. LGTM

Hi All, I shared a patch on the bitbake mailing list to make some syntax generate warnings, specifically things of the form: XXX_append += "YYY" XXX_prepend += "YYY" XXX_remove += "YYY" and the ?=,

I am not saying there are no solution but it was saying was to reduce the amount of customizations and default to common protocols which would help

Isn't this all already handled by: https://git.openembedded.org/openembedded-core/commit/?id=abb8895d5b42a5dc171360a261a2652acd14ee7e ?

<richard.purdie@...> wrote: I understand that, however, the reality is that organizations have IT teams which are catering to a wider set of security needs and have been

Some servers out there (e.g. our own git.yoctoproject.org) have slightly different git and https urls so this isn't as simple as you'd think. The security offered by https isn't as great as it first

Can we change bitbake fetcher to default to https instead git anonymous protocol as fallback? this will be good security measure too. <richard.purdie@...> wrote:

wrote: I've sent out a couple of patches for bitbake, one which does the remapping and a second which adds the warning. Testing would be appreciated before I merge them (I need to focus on master

I think we put a warning on master and forwards but not older bitbakes. Cheers, Richard

I totally agree with that. I still think we should also warn out so we don't have to maintain this magic quirk forever. Andrei

The brownouts are already happening, got 20+ failed jenkins jobs over night, because they failed to fetch various metadata layers over git:// from github. And hopefully my understanding of the

Thanks for reporting this, it helps to know this is happening as we'll probably start seeing odd error reports for the brownouts. I've updated the conversion script I mentioned earlier in this thread

The difference is that only few upstream repos are renaming master to main while removing the master branch completely and the change of the default branch to main affects only newly created repos on

The issue I think is the size of it. When you consider just the main branch for oe-core, this isn't an issue, but with all the release branches people are still on, with all the various layers some