| 4 Sep 2021 |
 kranzes | I couldn't figure it out but that's probably because i dont know what robotnix does in depth enough to know what it does different than normal building through docker or something like that | 13:31:40 |
 danielrf | kranzes: well I was initially hoping that I could extract and compare both images to see if I noticed anything obviously wrong | 19:46:48 |
| danielrf | but there's nothing obvious at least | 19:46:59 |
| danielrf | The comparison isn't exactly great since the two images were built from slightly different source trees | 19:47:25 |
| danielrf | So one next thing to try would be to a build where we are using the exact same revisions for all repos | 19:49:49 |
| danielrf | You can generate a manifest file with these revisions pinned by running repo manifest -r -o miatoll.xml at the root of your source tree (inside your docker image?) | 19:50:38 |
| danielrf | That manifest file would be useful to set the repo .json file used in robotnix to have exactly the same revisions | 19:51:07 |
| danielrf | * So one next thing to try would be to try a build where we are using the exact same revisions for all repos | 19:51:51 |
| kranzes | I dont quite get what you mean | 19:52:30 |
| kranzes | What should i be doing? Right now i just started building in the docker image a new build for my device with a working setup wizard so i can actually use it | 19:53:24 |
| kranzes | It takes me like 3:20h to build the rom | 19:53:41 |
| danielrf | I'd like you to try to generate that pinned manifest file and share with me | 19:53:57 |
| kranzes | how do i get it? sorry | 19:54:09 |
| danielrf | hmm, lets try: docker run -it forklineageos -v "/home/1TB-HDD/Android/lineage:/srv/src" repo manifest -r -o miatoll.xml | 19:59:28 |
| kranzes | where would that drop the manifest? | 20:00:06 |
| kranzes | miatoll.xml | 20:00:09 |
| danielrf | should be at /home/1TB-HDD/Android/lineage | 20:00:20 |
| danielrf | if I'm reading the Dockerfile correctly | 20:00:25 |
| kranzes | In reply to @danielrf:matrix.org
should be at /home/1TB-HDD/Android/lineage its not there | 20:00:33 |
| danielrf | Did you get any other output from that command? | 20:01:11 |
| kranzes | nope | 20:01:18 |
| kranzes | it ran for like 2 seconds | 20:01:22 |
| kranzes | but didnt throw any output back | 20:01:26 |
| danielrf | Hmm, it should say Saved manifest to miatoll.xml | 20:01:55 |
| kranzes | [kranzes@pongo /home/1TB-HDD/Android/lineage]$ docker run -it forklineageos -v "/home/1TB-HDD/Android/lineage:/srv/src" repo manifest -r -o miatoll.xml
[kranzes@pongo /home/1TB-HDD/Android/lineage]$ ...?
| 20:02:25 |
| kranzes | No output | 20:02:38 |
| danielrf | Just to verify, what are some of the files/directories under /home/1TB-HDD/Android/lineage ? | 20:03:01 |
| kranzes | [kranzes@pongo /home/1TB-HDD/Android]$ tree lineage -L 2
lineage
└── LINEAGE_18_1
├── android
├── Android.bp -> build/soong/root.bp
├── art
├── bionic
├── bootable
├── bootstrap.bash -> build/soong/bootstrap.bash
├── build
├── compatibility
├── cts
├── dalvik
├── developers
├── development
├── device
├── external
├── frameworks
├── hardware
├── kernel
├── libcore
├── libnativehelper
├── lineage
├── lineage-sdk
├── Makefile
├── out
├── packages
├── pdk
├── platform_testing
├── prebuilts
├── sdk
├── system
├── test
├── toolchain
├── tools
├── user-keys -> /srv/keys
└── vendor
31 directories, 4 files
| 20:03:59 |
| kranzes | there is also .repo inside there | 20:04:38 |
| kranzes | with the manifests? | 20:04:42 |
