| 16 Nov 2024 |
 Atemu | But also bad because I don't know what else it could be | 02:13:54 |
 oak 🏳️🌈♥️ | There is config.source.dirs.vendor/oneplus | 02:14:08 |
| Atemu | Ah right we have slashes in those names | 02:15:06 |
| Atemu | Although I'm not sure whether we strip the proprietary/ prefix | 02:15:22 |
| Atemu | In reply to @oak:universumi.fi
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
You're going to have to figure out what produces this error | 02:15:55 |
| Atemu | This smells LOS-specific | 02:16:15 |
| oak 🏳️🌈♥️ | That was kind of my first guess :D | 02:16:34 |
| Atemu | Could you try building cheeseburger or FP4? Just to make sure there's nothing funky with those specific devices | 02:16:56 |
| oak 🏳️🌈♥️ | Maybe they added some commit that they want to include the repo manifest as part of the build | 02:16:57 |
| oak 🏳️🌈♥️ | Testing with cheeseburger now | 02:17:29 |
| Atemu | I highly doubt they'd do that this far into LOS19's life (or death, really) | 02:17:34 |
| Atemu | Did you update its device and vendor dirs too? | 02:17:47 |
| oak 🏳️🌈♥️ | Yes | 02:18:33 |
| oak 🏳️🌈♥️ | Ah it's so awful to work with all these Android tools sometimes, maybe I'll try to check the latest merged commits from the lineageos gerrit | 02:19:06 |
| Atemu | Okay so we'd expect the same error then if this isn't device-specific | 02:19:39 |
| Atemu | Though honestly at this point I'd recommend you to just take that version of LOS19 | 02:20:01 |
| Atemu | It updates to 20 just fine | 02:20:08 |
| oak 🏳️🌈♥️ | but yes cheeseburger also provides same error | 02:21:20 |
| Atemu | Could you stash and check whether that error is present on the commit I gave you too? Just a sanity check | 02:22:02 |
| oak 🏳️🌈♥️ | You mean this commit? https://github.com/nix-community/robotnix/commit/f4d5a275a8e7381d08460a633e94d29147f61760 | 02:23:03 |
| Atemu | Yup | 02:23:15 |
| oak 🏳️🌈♥️ | I already said it built the instantnoodlep version without any issues if I don't modify it, but if I run the update scripts then this issue of it trying to run repo appears | 02:23:40 |
| Atemu | Ah right | 02:23:48 |
| Atemu | Anything interesting in the diff? | 02:23:59 |
| oak 🏳️🌈♥️ | So I would assume the cheeseburger version also builds fine or at least doesn't have this issue | 02:24:03 |
| Atemu | Any removed entries in the device dirs for instance? | 02:24:31 |
| Atemu | You could basically also diff the source.dirs | 02:25:02 |
| Atemu | Or if you want to use nix-diff then the debug-enter-env drvs | 02:25:17 |
| oak 🏳️🌈♥️ | Well I don't want to spend too much time figuring this out, but if it would have been something like reverting one commit from one of the repos to make it work again I'd had done that level of effort | 02:27:21 |
| oak 🏳️🌈♥️ | What could be the repository where they have added this manifest generation into the build? | 02:27:57 |
