Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Was there once a master branch that got renamed? #1206

Open
glaure opened this issue Oct 18, 2024 · 3 comments
Open

Was there once a master branch that got renamed? #1206

glaure opened this issue Oct 18, 2024 · 3 comments

Comments

@glaure
Copy link

glaure commented Oct 18, 2024

Hi,

i just wanted to let you now that the renaming of master to main was a breaking change for a lot of yocto based firmware builds.

I fixed for me with a bappend file, but this has to be done by everyone using yocto and openembedded at a fixed released state.

Bye Gunther

@rgetz
Copy link
Contributor

rgetz commented Oct 18, 2024

yes, my guess is it happened sometime near/before Apr 2024 - f562a61

In ADI's meta suggestion:
https://github.com/analogdevicesinc/meta-adi/blob/main/meta-adi-xilinx/recipes-support/libiio/libiio_%25.bbappend

they recommend : BRANCH ?= "libiio-v0" to get the most stable.

@nunojsa
Copy link
Contributor

nunojsa commented Oct 21, 2024

From what I can tell, things are fixed in upstream meta-oe. So if people use stable branches things should just work when upgrading from one release to another. Now, if some downstream hacking is being done on the recipe then, yeah, things can break (as it happened for meta-adi).

I fixed for me with a bappend file, but this has to be done by everyone using yocto and openembedded at a fixed released state.

The way I see it, it is already done as the rename already happened upstream. If someone is doing some downstream strange hacking (as meta-adi to get the dev branch) I would say is up to those users to fix things.

@catkira
Copy link
Contributor

catkira commented Nov 12, 2024

A little inconvenience for being woke is not a big sacrifice :P

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants