| 16 Nov 2024 |
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 |
atemu12 | 20 has them split for each device | 02:07:52 |
atemu12 | (And SoC-specific vendor dirs AFAICT) | 02:08:05 |
atemu12 | If you're building 19, you want the vendor_oneplus thing | 02:08:47 |
oak 🏳️🌈♥️ | but yes as I said after running the update scripts I get the same error, it's trying to run repo and the line has the "proprietary" in it | 02:10:32 |
atemu12 | Is proprietary_vendor_oneplus in source.dirs? | 02:10:53 |
atemu12 | nix-instantiate --arg configuration ... -A config.source.dirs.proprietary_vendor_oneplus | 02:11:36 |
oak 🏳️🌈♥️ | It does not seem to be there | 02:13:24 |
atemu12 | Okay, that's good | 02:13:37 |
atemu12 | 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 |
atemu12 | Ah right we have slashes in those names | 02:15:06 |
atemu12 | Although I'm not sure whether we strip the proprietary/ prefix | 02:15:22 |
atemu12 | 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 |
atemu12 | This smells LOS-specific | 02:16:15 |
oak 🏳️🌈♥️ | That was kind of my first guess :D | 02:16:34 |
atemu12 | 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 |