Closed NicolasDorier closed 4 years ago
Use master branch or step us as a day-day maintaner of that branch that will manually pull bugfixes into that branch and keep it up to date. Option B - that we will do that for you - is not going to happen.
@igorpecovnik I may have not understood correctly, but I thought that 20.08 was a "release". If I find the correct commit fixing this error, should I make a backport to 20.08 and make PR for it, or you will just make a new release later?
I found some commits with patches related to this file, but those are all on 20.08 already. Will try on master tomorrow.
If I find the correct commit fixing this error, should I make a backport to 20.08 and make PR for it, or you will just make a new release later?
Only if you plan of doing this on a long term, otherwise, for one time fix, don't bother. In a few weeks, some other (major) problem might pop up ... it is possible to fix this problem to freeze (unfreez on bugfix) commits on all sources. There are a lot of them and represent a serious maintainace issue and I can assure you that we will not do anything about. We can't.
Those releases are in fact only used for building images - we branch once we are ready https://docs.armbian.com/Process_Release-Model/#release-branching-versioning-and-tags to release master for further development. But we only keep last stable branch maintained for about 1 month to issue smaller bug fix releases, then we move on. This is the best possible and we will no imprve this with current crew - also make sure to check support terms https://github.com/armbian/build#support
If somebody get stuck, cherry-picking this commit on top of the branch fixed my issue:
https://github.com/armbian/build/commit/f28912f041985e6341c5efcaa6218234738a53d2
Based on branch v20.08, I do not manage to build the kernel:
Config
Logs