| 16 Nov 2024 |
 atemu12 | Depends on what they are | 00:36:16 |
| atemu12 | There's a matrix for stuff that's expected to work or not | 00:36:27 |
 oak 🏳️🌈♥️ | It wasn't actually the webview that was failing, I think it was the chromium apk package itself | 00:37:00 |
| atemu12 | Yeah that's not unexpected | 00:37:17 |
| atemu12 | I created an issue on yeeting chromium earlier | 00:37:31 |
| oak 🏳️🌈♥️ | Ah yes this one I did encounter before:
error: hash mismatch in fixed-output derivation '/nix/store/hcz1f4ld47syakxfkl54p6s3g3jr972i-android_external_chromium-webview_prebuilt_arm-3a32a73.drv':
specified: sha256-XEzHw0c/xPM3X8VDptJNZln2aOlxhkRXp+EDp1eM4NI=
got: sha256-C9Syc7A5OyL4iGV1n9qNvwsZ//A5t3E5PDOR0wd5Mu8=
For all these webview prebuilts the hashes are wrong, these should get updated by the update.sh?
| 00:39:13 |
| atemu12 | Nope, webview stuff is entirely separate | 00:39:39 |
| atemu12 | update.sh is for lineageos onlu | 00:39:45 |
| atemu12 | * update.sh is for lineageos only | 00:39:49 |
| oak 🏳️🌈♥️ | Yeah and if I fix the hashes manually inside the lineage-19.1/repo.json then they start to work | 00:40:31 |
| oak 🏳️🌈♥️ | I realized I actually need to set the webview setting to false because it probably defaults to true | 00:44:45 |
| oak 🏳️🌈♥️ | * I realized I actually need to set the webview setting to false (in my configuration) because it probably defaults to true | 00:45:03 |
| oak 🏳️🌈♥️ | Okay now it actually tried to build and:
FAILED: out/target/product/instantnoodlep/obj/ETC/build-manifest_intermediates/build-manifest.xml
/bin/bash -c "(mkdir -p out/target/product/instantnoodlep/obj/ETC/build-manifest_intermediates/ ) && (python3 .repo/repo/repo manifest -o - -r | grep -Ev \"proprietary_\" > out/target/product/instantnoodlep/obj/ETC/build-manifest_intermediates/build-manifest.xml )"
python3: can't open file '/build/.repo/repo/repo': [Errno 2] No such file or directory
| 00:58:11 |
| oak 🏳️🌈♥️ | Well I'll simply try to go to back to that commit id you gave | 01:06:39 |
| atemu12 | It appears to be attempting to run repo during the build? | 01:07:23 |
| atemu12 | That suggests to me it's missing some source dir | 01:07:32 |
| oak 🏳️🌈♥️ | I'm guessing it's trying to run repo to generate some kind of manifest to be included in the build | 01:16:02 |
| atemu12 | Ah if you look closer it appears to be missing the proprietary vendor stuff | 01:16:45 |
| oak 🏳️🌈♥️ | It's nice to get this kind of deep insight :D | 01:17:47 |
| atemu12 | Well it's only a guess based on the log | 01:18:11 |
| atemu12 | Make sure there's a proprietary/ for every device/ | 01:18:42 |
| atemu12 | In source.dirs | 01:18:47 |
| oak 🏳️🌈♥️ | From the commit you gave me, I was able to build lineageos-19.1 but if I try to update things with update.sh things start to break the same way | 02:05:39 |
| atemu12 | You won't be able to update from that commit in the first place as its update script would have been broken by now | 02:06:08 |
| atemu12 | So I wonder how you'd have done that? | 02:06:20 |
| oak 🏳️🌈♥️ | Ah I wasn't able to update all the device dirs, maybe that's the reason for problems | 02:06:51 |
| oak 🏳️🌈♥️ | I only manually updated instantnoodlep | 02:07:04 |
| atemu12 | Well yeah, if you don't actually update the device dirs, it will never update the vendor dirs either | 02:07:14 |
| oak 🏳️🌈♥️ | I noticed some of the repos get updated to lineage-20 and I'm not sure is that the breakage you are talking about | 02:07:25 |
| atemu12 | 19 needs the combined vendor dirs | 02:07:46 |
