-
Notifications
You must be signed in to change notification settings - Fork 70
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 21 and detailed instructions on adding a flavor #235
Comments
It's not trivial but also not unreasonably hard. It roughly goes like this:
Take a look at #213 and specifically 11e02c0. Having it documented properly would be great though. Don't copy over the directory for the sources though; you want to start fresh. As for the error, it appears that the repo command failed for some reason. Run it manually and figure out why. |
Missed this part: I'm not working on it and I am also not aware of anyone else who could be working on it. @eyJhb might be but I don't think they are. |
Thanks! I'll look at that commit today. Regarding the error, this is what I see when I run the command directly:
A quick search does reveal others with a similar problem. Looks like this module was removed with Python 3.10. |
That might be fallout from #231 You could revert that merge (or check out its first parent) enter the nix shell and then cancel the revert/go back to your branch for a quick workaround. |
Your workaround did the trick. |
I added changes similar to #213. Now after running update, It runs for a while fetching information from dozens of external repos, then it starts listing out code names for which a branch doesn't exist, then it attempts to authenticate with github, after which it fails. It seems that one of the repos has disappeared or gone private. Here's a truncated log:
|
I think it's not finding a I'll see if it's possible to fork the first repo, add the branch/tag, and use it. |
Seems that |
Github doesn't differentiate between private repo and 404 in order to not reveal the existence of private repos to the public. If you're being asked for creds for a repo under the LOS org, it's likely just a 404. 404s happen because the script is wrong and/or there is not strictly enforced convention it could follow. We construct repo paths based on assumptions that are true for most devices. There's a bunch of workarounds for devices already, just add more to the pile... I've recently started to simply ignore entire devices that do not follow the conventions of all the other devices. |
I'm not sure where to begin to address this. Can't find what is pulling in this |
The vendor- aswell as device-dirs are generated by
You'll therefore probably have to adjust this:
if branch in [ 'lineage-20.0', 'lineage-21.0' ]: Or some cleaner code that basically does Also please ensure you haven't copied any of the JSONs. |
I just created a It indeed completed without fail this time! But still a long list of
And in the end only the I'll try to piece through the code to see how it generates those files. |
I also made a change to how it calculates |
Ok, No |
Looks like they migrated from Running again with the update. BTW, is there a chat room, e.g. matrix or IRC or whatever where people keep in touch re: this project? Or is the volume low enough to keep it on Github? |
Thank you, I'll join that room. I'm in the process of updating the patches now. |
I've also came across the No idea if it works properly after the rebase yet, though. |
I'm looking to use Robotnix to build LineageOS 21 for the Pixel 7 Pro. I read the wiki, and have been parsing through the code base, and still don't have a sense as to how deep the rabbit hole goes. I'm assuming that it's not trivial to add a new version of Lineage, otherwise it probably would have been done already - is that an accurate assessment? Here's what I've done so far:
flavors/lineageos/lineage-21.0
folder, copied fromlineage-20.0
nix develop
in theflavors
path./update.sh lineage-21.0
it then fails with:
device-metdata.json
does seem to be updated, but that's it. At the moment, I have no idea whether I'm 3% of the way to adding LineageOS 21.0, or 50%. I'm guess it's more like 3%.Is there a detailed reference on the steps needed to do this? Is someone already working on this and I can either abort my efforts or help out?
The text was updated successfully, but these errors were encountered: