old recipes fail because the source branches go away

[abaumfalk]

We experienced a fetcher failure when using the LTS-Kernel recipe linux_altera_ltsi_4.14.130.bb.
When operating without sstate and download caches the fetcher fails, because it cannot find the upstream branch socfpga-4.14.130-ltsi any longer at git://github.com/altera-opensource/linux-socfpga.git. It seems, that the maintainers of this repo frequently delete the old branches, even if they are LTS.
We have worked around this by creating a fork and re-adding the missing branches. It is essential for us, to keep the LTS-recipies functional for a long period of time.
Is there a better (recommended) way?

[dwesterg]

The repo in question is cleared of all branches that are no longer maintained. Your method or forking the repo is appropriate, but you should also be concerned with fixing newly reported bugs and CVEs with your fork.

…

--dalon

On Fri, Oct 22, 2021 at 6:00 AM Arno Baumfalk ***@***.***> wrote: We experienced a fetcher failure when using the LTS-Kernel recipe linux_altera_ltsi_4.14.130.bb. When operating without sstate and download caches the fetcher fails, because it cannot find the upstream branch socfpga-4.14.130-ltsi any longer at git://github.com/altera-opensource/linux-socfpga.git. It seems, that the maintainers of this repo frequently delete the old branches, even if they are LTS. We have worked around this by creating a fork and re-adding the missing branches. It is essential for us, to keep the LTS-recipies functional for a long period of time. Is there a better (recommended) way? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#231>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJNSRMFX6V2OBT2OKIFFS3UIFN7HANCNFSM5GQQEVTA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[abaumfalk]

Thank you for the quick reply.

Of course we would update the fork, if needed - but I would rather find a better solution in the long run.
Another problem with this workaround is, that older versions of our project will not work any longer "out of the box" now without using the download cache, which is not be available everywhere.

The repo in question is cleared of all branches that are no longer maintained. Your method or forking the repo is appropriate, but you should also be concerned with fixing newly reported bugs and CVEs with your fork.
…
--dalon

[cyanosp]

I will just jump into this issue as it is related.
With 4.X gone there is also no rt branch left.
For now I use the recent version (5.10) and apply the patches myself, are there any plan for a new rt-yocto layer?

[mc-requtech]

A workaround is to set KBRANCH to "${SRCREV};nobranch=1". Then you can check out the commit (which is still in the repo due to a tag) even though it is on no branch.