| 13 Nov 2025 |
 mio | I was doing it in a directory with no existing akita*.zip | 00:09:29 |
| 17 Nov 2025 |
 autra | hi! I'm wondering if updater.url really works.... It's currently commented on modules/release.nix:163 | 10:59:34 |
 pentane (DECT CYPT/2978) | Hmm, haven't dealt with that part of the code yet | 22:33:02 |
| pentane (DECT CYPT/2978) | but that's not the location where the actual on-device app is being configured - that happens via an RRO in modules/apps/updater.nix | 22:34:51 |
| 18 Nov 2025 |
 puffnfresh | pentane ⭔: I'm having a problem with 2025111800
unpacking 'shiba BP3A.251105.015 factory'nfinityAunpacked shiba-BP3A.251105.015
> Generated vendor module at vendor/google_devices/shiba
> /nix/store/clbb2cvigynr235ab5zgi18dyavznlk2-gnused-4.9/bin/sed: can't read vendor/google_devices/shiba/proprietary/device-vendor.mk: No such file or directory
| 23:06:09 |
| puffnfresh | I don't have a google_devices directory in vendor, at all
sudo ls -l /proc/815371/cwd/vendor/
total 8
dr-xr-xr-x 14 root root 4096 Jan 1 1970 adevtool
dr-xr-xr-x 2 root root 4096 Jan 1 1970 state
| 23:15:37 |
| 19 Nov 2025 |
| pentane (DECT CYPT/2978) | Yep, on it already | 09:48:30 |
| pentane (DECT CYPT/2978) | should've posted that in the PR thread, sorry | 09:48:59 |
| mio | pentane ⭔: Is the patch file missing from the commit? https://github.com/nix-community/robotnix/pull/330/commits/5dcd6a7046403dc374c8701b6a1f1d14c4140c62 | 12:36:54 |
| pentane (DECT CYPT/2978) | yep, sorry, just force-pushed it | 14:07:05 |
| pentane (DECT CYPT/2978) | gonna try to debug the actual build issue this evening | 14:07:12 |
| 20 Nov 2025 |
|  John joined the room. | 06:14:22 |
| 21 Nov 2025 |
| mio | In reply to @cyclopentane:aidoskyneen.eu
gonna try to debug the actual build issue this evening how is it going? | 04:36:19 |
| 22 Nov 2025 |
| pentane (DECT CYPT/2978) | haven't had time yet, too much to do at work in the last couple days. gonna try to fix it this weekend | 12:15:34 |
| pentane (DECT CYPT/2978) | Found the issue: https://github.com/nix-community/robotnix/pull/331/commits/f67e30e064544206ffe59604de41a92ddcc09a2d | 13:20:22 |
| pentane (DECT CYPT/2978) | Still waiting for the lockfile bump to 2025112100 to complete, gonna test it on my tegu then | 13:20:48 |
| pentane (DECT CYPT/2978) | (i should really also improve Git mirror support in repo2nix...) | 13:21:00 |
| pentane (DECT CYPT/2978) | done: https://github.com/nix-community/robotnix/pull/331 | 22:26:52 |
| 25 Nov 2025 |
 waltmck | I'm thinking of buying myself a phone to play with robotnix, what are the best supported models? | 00:17:30 |
| waltmck | I don't see any sort of list in the documentation of what is known to work | 00:18:31 |
| waltmck | * | 00:19:06 |
 Atemu | Something like the 7a would be ideal and it should build | 01:32:33 |
| Atemu | What's the error? Do you have enough RAM? | 01:33:00 |
| 26 Nov 2025 |
 cornu | hi, have a similar error building lineage for bluejay (pixel 6a). Graphene flavor and other lineage builds (e.g. FP4) build without error.
``´
Running phase: unpackPhase
> Running phase: patchPhase
> Running phase: updateAutotoolsGnuConfigScriptsPhase
> Running phase: buildPhase
> Trying dependencies-only mode on a non-existing device tree?
> Kernel source /build/out-kernel/google/gs-6.1 is missing, preparing folder structure
> cp: cannot stat '/build/.repo/repo': No such file or directory
´´´
| 16:47:12 |
| cornu | * hi, have a similar error building lineage for bluejay (pixel 6a). Graphene flavor and other lineage builds (e.g. FP4) build without error.
Running phase: unpackPhase
> Running phase: patchPhase
> Running phase: updateAutotoolsGnuConfigScriptsPhase
> Running phase: buildPhase
> Trying dependencies-only mode on a non-existing device tree?
> Kernel source /build/out-kernel/google/gs-6.1 is missing, preparing folder structure
> cp: cannot stat '/build/.repo/repo': No such file or directory
´´´
| 16:47:39 |
| 30 Nov 2025 |
 oak 🏳️🌈♥️ | Btw did Google remove all the kernel sources for old versions as well? I know Google removed kernel sources and device tree sources at least for the new Pixel phones, which is the reason Pixels are not recommended for Custom ROm usage anymore | 12:35:49 |
| 29 Nov 2025 |
 luelista | oh that might be the same problem i ran into with lineage for pixel 9a
it seems that at some point google switched to using bazel for building the kernel (https://android.googlesource.com/kernel/build/+/refs/heads/main/kleaf/README.md)
I've tried various things to get it to work, but without success so far:
- downloading necessary kernel source repos before running bazel: https://github.com/nix-community/robotnix/compare/master...luelista:robotnix:lineage-tegu (problem: bazel still wants to fetch more things from the internet during build, e. g. precompiled kernel image)
- turning off downloading precompiled images (takes way longer to build, and i think it still didn't work, not sure any more)
- building kernel with buildBazelPackage from nixpkgs (prebuilt images disabled)
- downloading prebuilt kernel images as fixed output derivation using buildBazelPackage
| 21:14:50 |
| 30 Nov 2025 |
| oak 🏳️🌈♥️ | * Btw did Google remove all the kernel sources for old versions as well? I know Google removed kernel sources and device tree sources at least for the new Pixel phones, which is the reason Pixels are not recommended for Custom ROM usage anymore | 12:36:00 |
| 29 Nov 2025 |
| luelista | * oh that might be the same problem i ran into with lineage for pixel 9a
it seems that at some point google switched to using bazel for building the kernel (https://android.googlesource.com/kernel/build/+/refs/heads/main/kleaf/README.md)
I've tried various things to get it to work, but without success so far:
| 21:15:21 |
| 30 Nov 2025 |
| oak 🏳️🌈♥️ | It's strange my custom built LineageOS started to offer me a system update yesterday, even though I haven't build a new version and uploaded it to webserver | 12:38:12 |
