Hi great question. Def can be confusing. We're working to be more clear.
GitHub issues (NOT PRs) are meant to be specific to the Armbian build engine and not specific to devices.
Raise device issues on forum for conversation and hopefully find the attention of a maintainer. (Part of reason we do it on forum is it creates too much noise on GitHub for such a small team of devs)
If it's an issue a maintainer or armbian developer thinks it needs to be prioritized, they will add to our Jira
For those that don't like posting on forum anybody can open a draft PR with a proposed solution and explanation of what's being solved in GitHub
if using lxc the container.
you need to execute it with more priviledges
if you are already, or are using lxc the VM
your kernel needs to be ubuntu's -generic kernel rather than the -virtual kernel... -virtual doesn't have binfmt support in it the last time I checked.
misc building tips.. I personally hate the LIB_TAG thing.. and prefer to just force it to use whatever branch I'm using.. here's a hint for that https://docs.armbian.com/Developer-Guide_Build-Preparation/#using-alternate-armbian-builder-repos-and-branches
How to build from the kernel source you want and love armbian builder
As we mentioned. it's not that the armbian build checkout has changed the minor release. it's that the upstream has (it's a weakness we have). So you're going to want to specify your own kernel branch/commit/target etc by hand.
alright so.. it's just following the linux-5.10.y branch.. hence the minor release update.... and since no explicit kernel source is specified.. we can assuming it's using the default mainline
so in theory you should be able to create the file
code {
font-family: Consolas,"courier new";
color: crimson;
background-color: rgba(0, 0, 0, 0.2);
padding: 2px;
font-size: 105%;
}
userpatches/sources/meson-g12b.conf
lanefu's post in update in buster is failing with redirection from https to 'http://armbian.tnahosting.net/apt/dists/buster/Release' is forbidden was marked as the answer