| 3 Sep 2021 |
 kranzes | I still don't get it though the build went fine | 18:02:13 |
 samueldr | ¯\_(ツ)_/¯ | 18:06:56 |
| samueldr | maybe | 18:06:57 |
 danielrf | kranzes: About your first question: Yes, robotnix should be able to handle "nested" directories. It won't do any merging of directories, but if you have a repo that should live in a subdir of another repo, we'll pre-create subdir mount point in the outer repo when we bind-mount the source files | 18:15:05 |
| kranzes | 👍️ | 18:15:31 |
| danielrf | your configuration looks OK to me. Have you had any success building a working image for this device outside of robotnix? | 18:16:54 |
 Robin | I found a link to a CarbonROM sepolicy with an explanation regarding the boringssl_self_test:
https://review.carbonrom.org/plugins/gitiles/CarbonROM/android_system_sepolicy/+blame/549c36d27677128e57489c769ae2389637c4adab/private/boringssl_self_test.te | 18:17:18 |
| danielrf | I remember you had this issue a few months ago | 18:17:18 |
| kranzes | In reply to @danielrf:matrix.org
your configuration looks OK to me. Have you had any success building a working image for this device outside of robotnix? I tried somewhat, but got a different error with https://github.com/lineageos4microg/docker-lineage-cicd | 18:18:42 |
| kranzes | error in the build process | 18:18:54 |
| kranzes | i can try again | 18:18:58 |
| kranzes | need to modify that oci imaeg | 18:19:14 |
| kranzes | * need to modify that oci image and write a local_manifest.xml | 18:19:25 |
| kranzes | Which i don't enjoy doing | 18:19:35 |
| kranzes | i might do that later today | 18:19:39 |
| kranzes | In reply to @kranzes:matrix.org
I tried somewhat, but got a different error with https://github.com/lineageos4microg/docker-lineage-cicd If anyone knows of a better docker image let me know | 18:22:34 |
| kranzes | It seems to be the most popular | 18:23:10 |
| kranzes | so ill give it a try in a bit | 18:23:15 |
| samueldr | for the record it's upstream too:
https://android.googlesource.com/platform/system/sepolicy/+/master/private/boringssl_self_test.te | 18:25:42 |
| kranzes | 
Download image.png | 19:18:53 |
| kranzes | In reply to @danielrf:matrix.org
your configuration looks OK to me. Have you had any success building a working image for this device outside of robotnix? wish me luck | 19:18:57 |
|  dsx joined the room. | 20:13:33 |
| dsx | Hello everyone. I've build vanilla AOSP with robotnix (time nix-build "https://github.com/danielfullmer/robotnix/archive/master.tar.gz" --arg configuration '{ device="redfin"; flavor="vanilla"; apps.fdroid.enable = true; microg.enable = true; apps.seedvault.enable = true; apps.updater.enable = true; apps.updater.url = "https://ota.example.com/redfin/"; signing.enable = true; signing.keyStorePath = "/var/lib/keys/android"; }' -A releaseScript) and after following install instructions I get an boot loop. Am I missing some steps? | 20:16:43 |
| dsx | Passing keys directly to the build sandbox with … -A factoryImg --option extra-sandbox-paths /keys=/var/lib/keys/android doesn't help much either. | 20:18:02 |
| dsx | Build finishes without errors though. | 20:18:15 |
| danielrf | Looks OK to me. I know we have at least one other redfin user (I believe on grapheneos flavor), but I don't know if we have anyone else currently using redfin+vanilla | 20:48:58 |
| danielrf | If there is please let me know | 20:49:38 |
| danielrf | But this could be an issue with how the redfin kernel is built for the vanilla flavor | 20:50:08 |
| samueldr | general checks apply, maybe: was a factory reset tried? | 20:51:41 |
| danielrf | The two things I would try to test would be 1) using `flavor="grapheneos";` and 2) using upstream prebuilt kernel with `flavor="vanilla";` but `kernel.enable=false;` | 20:52:59 |
