-
Notifications
You must be signed in to change notification settings - Fork 64
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
lineageos: Lineage 20.0 support #213
Conversation
Can the removal of 17.1/18.1 be done in another PR? I know you haven't tested them, and don't intend to support them, but that change to me is surprising when seeing "Lineage 20.0 support" as the PR name. It's fine if you don't update their device dirs either in this PR. It would also make visually reviewing some of the changes in (I'll also add that selfishly it will make it easier for me to re-integrate the changes for 18.1 and my device if the change is less intertwined with this PR...) |
Not all of my devices work with Lineage20 either :-/ |
I'm personally fine with keeping the old 17.1 and 18 states around but I'll add a note that they're unmaintained. |
Another thing is that I may have accidentally broken many devices due to the update script being a bit broken. I'll do one last update of los 17.1 and 18.1 after the fixes. |
/tmp is usually a tmpfs and some vendor dirs require >16GB of space. That blows up even on setups with 32GB of RAM with default tmpfs size (50%).
Prints device data and URLs to be fetched
Don't ask me why their branches are named 20 rather than 20.0
(separate commit for keeping the first one small)
Included in metadata now
This fixes a really nasty bug where the updater would skip fetching a rev because it's already the newest, not have it in the store and therefore erroneously conclude that it doesn't have linage.dependencies.
Updating them is (perhaps unsurprisingly) broken. I'm just not going to bother. 17.1 and 18.1 are now untouched. |
Thank you, I might not have been 100% precise, it's fine if it's broken, I mainly want to (selfishly) have a way forward, and absolutely do not want you to lose time supporting them since in the current state it was already not great anyway. |
Also refactored this bit to be quite a bit nicer to read
I had assumed I needed this but it's easier to just implement this pattern in Nix.
This makes LOS updates reproducible given a full mirror state!
Alright, after some cleanup LOS 19.1 evals again and I can run reproducibly the updater to confirm my cleanup still works, hooray! I'll now try building LOS 19.1 and then running it on my broken cheeseburger to see whether everything still works. If it does, I think we're close to merging this. I'd love some review, specifically on the python parts. I still have very little experience in python. |
Alright, LOS 19.1 seems to be working just fine now. If nobody objects the next few days, I'll merge. |
LOS 19.1 can't be updated anymore because there are now devices which only support LOS 20. I'm inclined to put LOS 19.1 into the unmaintained bucket with 17.1 and 18.1 because I can't be bothered to fix that. |
There you go. If anyone finds a breakage in the other flavours, let me know. I'll either try to fix them or drop the other flavours aswell. |
Hey there, thank you so much for this PR! I've tried building the FP3 LineageOS
I'm an Android noob, so I'm not sure what's going on. |
Indeed, I can reproduce. Looks like that was an upstream issue though because it builds with a newer LOS. |
No description provided.