!UUYziobKGGxpovWyAN:nixos.org

Robotnix

264 Members
Build Android (AOSP) using Nix | https://github.com/danielfullmer/robotnix83 Servers

Load older messages


SenderMessageTime
7 Sep 2021
@kranzes:matrix.orgkranzesimage.png
Download image.png
20:25:28
@kranzes:matrix.orgkranzesbut this is what's left20:25:33
@kranzes:matrix.orgkranzes
In reply to @kranzes:matrix.org
i highly doubt that does anything
in this case*
20:25:43
@kranzes:matrix.orgkranzesforklineageos uses a different android_vendor_lineage: https://github.com/ForkLineageOS/android_vendor_lineage20:27:20
@kranzes:matrix.orgkranzesWhat do you think we should do next?20:29:11
@danielrf:matrix.orgdanielrfTwo things we could do next: 1) dig through forklineageos changes that could be affected by either RELEASE_TYPE or OVERRIDE_TARGET_FLATTEN_APEX, or 2) continue bisecting by uncommenting RELEASE_TYPE and rebuilding/retesting20:31:14
@danielrf:matrix.orgdanielrfActually one other way we could try: compare the extracted images between working and non-working robotnix builds20:34:12
@kranzes:matrix.orgkranzesevery mention of OVERRIDE_TARGET_FLATTEN_APEX in ForkLineageOS is exactly the same as upstream LineageOS20:34:23
@kranzes:matrix.orgkranzes
In reply to @danielrf:matrix.org
Actually one other way we could try: compare the extracted images between working and non-working robotnix builds
Not sure how to do that
20:34:36
@danielrf:matrix.orgdanielrfNow that it's building in robotnix, I'd be more confident that our comparisons could reveal something20:34:40
@kranzes:matrix.orgkranzesDo you want me to upload a working robotnix built image?20:35:11
@kranzes:matrix.orgkranzesand a a working docker build image?20:35:19
@danielrf:matrix.orgdanielrfIt's OK. I'll try building both myself20:35:35
@kranzes:matrix.orgkranzes
In reply to @danielrf:matrix.org
It's OK. I'll try building both myself
Life saving
20:35:46
@kranzes:matrix.orgkranzesif i was to build now again,20:35:52
@kranzes:matrix.orgkranzesit will only be done at 3 AM20:35:57
@kranzes:matrix.orgkranzes6-7 AM if im gonna try building two images20:36:28
@kranzes:matrix.orgkranzesfor you it will take like what, 1 Hour? for both20:36:49
@danielrf:matrix.orgdanielrfeh, maybe closer to 1.5hrs, we'll see20:37:06
@kranzes:matrix.orgkranzesdoes signing.apex.enable = false; depend on setting envVars.OVERRIDE_TARGET_FLATTEN_APEX = "true"; ?20:37:34
@danielrf:matrix.orgdanielrfThey should be enabled/disabled together20:38:07
@kranzes:matrix.orgkranzes👍️20:38:15
@danielrf:matrix.orgdanielrf kranzes: Can you verify if the following image works? https://drive.google.com/file/d/1sumK24CzbWitR2XKSxUDatvYMyrkdVYP/view?usp=sharing 21:25:40
@danielrf:matrix.orgdanielrfHere's the diff between those two images, one with the APEX flattening / RELEASE_TYPE commented out, and one without21:28:25
@danielrf:matrix.orgdanielrf it's basically what you'd expect. SELinux changes for APEX, ro.lineage.releasetype differences, etc. 21:29:01
@danielrf:matrix.orgdanielrfOne thing that stands out a little is that some libraries are only in one image vs. the other. e.g. libcrypto_utils.so, libincident.so21:29:55
@danielrf:matrix.orgdanielrfand I wonder if that's a result of enabling/disabling APEX flattening21:30:09
@kranzes:matrix.orgkranzes
In reply to @danielrf:matrix.org
kranzes: Can you verify if the following image works? https://drive.google.com/file/d/1sumK24CzbWitR2XKSxUDatvYMyrkdVYP/view?usp=sharing
what changes does this image have?
21:33:24
@danielrf:matrix.orgdanielrfThat image just has commented out APEX flattening / RELEASE_TYPE.21:33:50
@kranzes:matrix.orgkranzesdidnt we build that before then?21:34:13

Show newer messages


Back to Room ListRoom Version: 6