Skip to content
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

Merged
merged 38 commits into from
Oct 28, 2023
Merged

Conversation

Atemu
Copy link
Contributor

@Atemu Atemu commented Sep 13, 2023

No description provided.

@samueldr
Copy link
Contributor

samueldr commented Sep 14, 2023

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 lineageos/default.nix easier, since git is eager to assume some unrelated (I think) changes are related.

(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...)

@mannp
Copy link

mannp commented Sep 14, 2023

(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 :-/

@Atemu
Copy link
Contributor Author

Atemu commented Sep 14, 2023

I'm personally fine with keeping the old 17.1 and 18 states around but I'll add a note that they're unmaintained.

@Atemu
Copy link
Contributor Author

Atemu commented Sep 14, 2023

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.

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.
@Atemu
Copy link
Contributor Author

Atemu commented Sep 14, 2023

Updating them is (perhaps unsurprisingly) broken. I'm just not going to bother. 17.1 and 18.1 are now untouched.

@samueldr
Copy link
Contributor

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.

flavors/lineageos/default.nix Outdated Show resolved Hide resolved
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!
@Atemu
Copy link
Contributor Author

Atemu commented Oct 12, 2023

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.

@Atemu
Copy link
Contributor Author

Atemu commented Oct 13, 2023

Alright, LOS 19.1 seems to be working just fine now. If nobody objects the next few days, I'll merge.

@Atemu
Copy link
Contributor Author

Atemu commented Oct 23, 2023

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.

@Atemu Atemu merged commit 73d6b0b into nix-community:master Oct 28, 2023
@Atemu Atemu deleted the lineage-20.0 branch October 28, 2023 18:27
@Atemu
Copy link
Contributor Author

Atemu commented Oct 28, 2023

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.

@minijackson
Copy link

Hey there, thank you so much for this PR!

I've tried building the FP3 LineageOS otaDir from robotnix master, but the robotnix-lineage_FP3-2023100409 build failed with:

FAILED:
hardware/qcom-caf/wlan/wcnss-service/Android.mk: error: "wcnss_service (EXECUTABLES android-arm64) missing libqmi_common_so (SHARED_LIBRARIES android-arm64)"
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.
build/make/core/main.mk:1130: error: exiting from previous errors.

I'm an Android noob, so I'm not sure what's going on.

@Atemu
Copy link
Contributor Author

Atemu commented Oct 29, 2023

Indeed, I can reproduce. Looks like that was an upstream issue though because it builds with a newer LOS.

Atemu@10edcae

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants