Hi, OnTue, 2 Nov 2021, at 10:49, Andrei Gherzan wrote: And by GitLab I meanGitHub. Andrei

Hi, I don't think this is a bigger issue because I don't see this warranting a default change. It is just an upstream protocol support change and we will update the respective recipes. If we don't,

There is even bigger issue with git repos from github.com now: https://github.blog/2021-09-01-improving-git-protocol-security-github/#no-more-unauthenticated-git bitbake git fetcher uses git://

Yes, exact timing to be determined but hopefully sooner than later (before April release). Cheers, Richard

Although the situation is a bit unfortunate I like the proposal and the script will likely make the transition less painful. Are you planning to turn the warning into an error at some point?

We've had concerns about the default behaviours of tools like git and how they'll handle the default branch names going forward. There are also concerns about what providers like github may do, and

All, Our next OpenEmbedded Happy Hour is on October 27 for Asia/Pacific timezones @ 2100/9pm UTC (5pm ET / 2pm

Thanks, there might be that gizmo added then in the not too distant future :) Alex

Yes, I believe that was the intended usage: $ git clone git://git.yoctoproject.org/meta-lts-mixins -b dunfell/kernel meta-lts-kernel-mixin $ git clone git://git.yoctoproject.org/meta-lts-mixins -b

Hello Denys, if I would like to add a 'dunfell/gizmo' branch to that repository, how would it work if a given build needs both the kernel and the gizmo? Is the repo supposed to be cloned twice into

Oops, sorry, updated the subject to the correct date. -- Regards, Denys Dmytriyenko <denis@...> PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964 Fingerprint: 25FC E4A5 8A72 2F69

All, As you are aware, next week is LF Embedded Linux Conference, which coincides with our OE Happy Hour. The Board has decided to extend the Happy Hour for the entire duration of Wednesday ELC

I'm really trying to say it is another change we could potentially make (in the spirit of the rest of the list). The license functions are like spaghetti and trying to fix up the tests to work after

It's not readily visible in the UI, but the layer index already has an internal means of specifying an alternative branch name that can be set by admins on a per layer-branch basis. I deliberately

On Thu, Sep 16, 2021 at 10:30 PM Andrea Adami via lists.openembedded.org <andrea.adami=gmail.com@...> wrote: but maybe I misread 'in another meta-layer' out of your control.

See here one example: https://github.com/vu-plus/meta-vuplus/blob/master/conf/layer.conf#L4 vs one allowing them https://git.openembedded.org/meta-handheld/tree/conf/layer.conf#n8 cheers A.A.

<mayank77fromindia@...> wrote: bbappends can not be undone sadly, maybe you can try some BBMASKing it if its in unique location perhaps.

Dear Experts, Is there any way we can disable bbappend file from another meta-layer in the current meta-layer or recipe file.It will be of great help.If we can use PNBLACKLIST or BBMASK to disable

-1 for "main", https://www.etymonline.com/word/main The etymology of "main" invokes hierarchy rather than inclusive meritocracy. +1 for "devel" (works as verb, noun and adjective) or "unstable"