Pete Fotheringham

> I would like to build A14 based roms with signature spoofing support; LineageOS made changes to their code, so that they now support 'restricted` signature spoofing (i.e. only microG...

> applying the "official" sig patches - in this case for A14: > > * https://github.com/lineageos4microg/docker-lineage-cicd/blob/lineage-21/src/signature_spoofing_patches/packages_modules_Permission-Android14.patch > > * https://github.com/lineageos4microg/docker-lineage-cicd/blob/lineage-21/src/signature_spoofing_patches/android_frameworks_base-Android14.patch Just to let you that for future Android versions, los4microg...

We're discussing the possibility of doing this in the LineageOS for microG project: see [this discussion](https://github.com/lineageos4microg/l4mManagement/discussions/39) We'd welcome your input there or here if you have any thoughts about this

Thanks for that. So we (LOS for microG project) will just pull the latest version from github ***unless*** it is marked 'pre-release`. That works for us :) Sad that there...

> Until recently, I believe that the GitHub releases pages marked beta versions as 'pre-release` and stable versions as 'latest' but this no longer seems to be the case. And...

> See the xml: https://microg.org/fdroid/repo/index.xml Looking at the history of that file, I came across several instances (in various `.json` files) of a `releaseChannels` field, set either to `"Beta"` or...

> On F-Droid it is probably not suggested for the 100MB problem (only 1 mirror of 3 have the real file and most of the time it will fails). Really?...

Thanks. So for L4M, we will pull the microG components from the github releases page, making decisions about when to pull new versions into our builds. I guess you will...

Closing this issue now: we know what to look for to find the latest stable build. I've raised #3164 to track the mismatch between this definition and what F-Droid is...

I don't plan to fix it in our repo, because 1. I have no idea ***how*** to fix it in our repo; 2. I haven't ever seen an problem reported...