| 11 Nov 2025 |
pentane ⭔ | huh, that sounds like an AVB problem | 08:44:40 |
puffnfresh | oh looks like you accidentally dropped avbFlags | 08:55:31 |
puffnfresh | I didn't see your message until I noticed that problem, so that makes me pretty confident | 08:57:48 |
pentane ⭔ | Oops | 08:58:59 |
pentane ⭔ | Thanks for testing then :D | 08:59:04 |
pentane ⭔ | you wanna commit avbFlags back in? (just tell me the name of your brsnch, I'll manually pull from it) | 08:59:31 |
pentane ⭔ | * | 08:59:39 |
puffnfresh | testing first, but will do | 09:00:59 |
puffnfresh | https://github.com/nix-community/robotnix/pull/327 | 09:30:00 |
puffnfresh | works great, used the generation script for the APEX keys, then copied in my Shiba keys which I previously generated with a different script | 09:31:46 |
pentane ⭔ | nice! | 09:34:26 |
pentane ⭔ | today, my tegu should be arriving, so I'll also be able to test this myself properly | 09:34:49 |
| 12 Nov 2025 |
mio | It works for my pixel8a! | 04:31:22 |
mio | some warnings ```
2025-11-12 15:25:08 - common.py - WARNING : Unable to get boot image build props: Failed to run command '['toybox', 'cpio', '-F', '/tmp/boot_b7t7hqvs.img/uncompressed_ramdisk', '-i']' (exit code 1):
cpio: empty archive
2025-11-12 15:25:08 - common.py - WARNING : Unable to get boot image build props: Failed to run command '['toybox', 'cpio', '-F', '/tmp/boot_ay_2ledc.img/uncompressed_ramdisk', '-i']' (exit code 1):
cpio: dev/null: Operation not permitted
cpio: dev/console: Operation not permitted
cpio: dev/urandom: Operation not permitted
Building factory image
ln: cannot create symbolic link from 'akita-img-2025110800.zip' to 'akita-img-2025110800.zip': File exists``` | 04:31:48 |
mio | * some warnings ```
2025-11-12 15:25:08 - common.py - WARNING : Unable to get boot image build props: Failed to run command '['toybox', 'cpio', '-F', '/tmp/boot_b7t7hqvs.img/uncompressed_ramdisk', '-i']' (exit code 1):
cpio: empty archive
2025-11-12 15:25:08 - common.py - WARNING : Unable to get boot image build props: Failed to run command '['toybox', 'cpio', '-F', '/tmp/boot_ay_2ledc.img/uncompressed_ramdisk', '-i']' (exit code 1):
cpio: dev/null: Operation not permitted
cpio: dev/console: Operation not permitted
cpio: dev/urandom: Operation not permitted
Building factory image
ln: cannot create symbolic link from 'akita-img-2025110800.zip' to 'akita-img-2025110800.zip': File exists``` | 04:31:58 |
mio | * some warnings
2025-11-12 15:25:08 - common.py - WARNING : Unable to get boot image build props: Failed to run command '\['toybox', 'cpio', '-F', '/tmp/boot\_b7t7hqvs.img/uncompressed\_ramdisk', '-i'\]' (exit code 1):
cpio: empty archive
2025-11-12 15:25:08 - common.py - WARNING : Unable to get boot image build props: Failed to run command '\['toybox', 'cpio', '-F', '/tmp/boot\_ay\_2ledc.img/uncompressed\_ramdisk', '-i'\]' (exit code 1):
cpio: dev/null: Operation not permitted
cpio: dev/console: Operation not permitted
cpio: dev/urandom: Operation not permitted
Building factory image
ln: cannot create symbolic link from 'akita-img-2025110800.zip' to 'akita-img-2025110800.zip': File exists
| 04:32:14 |
puffnfresh | yeah I get the same warnings, I think that last one is from doing it in a directory with an existing link | 09:20:15 |
puffnfresh | you don't get the warnings when running as root because cpio can create those files, but it's unnecessary | 09:20:38 |
| Inayet changed their display name from inayet to Inayet. | 12:37:27 |
pentane ⭔ |  Download 1000030213.jpg | 17:07:45 |
pentane ⭔ | ready to do some AVB testing by myself now! | 17:07:56 |
pentane ⭔ |  Download 1000030216.jpg | 22:36:07 |
pentane ⭔ | test successful. | 22:36:15 |
pentane ⭔ | contains 0% test-keys, as validated by the hacky Rust program I am about to commit | 22:37:06 |
pentane ⭔ | https://github.com/nix-community/robotnix/pull/328 | 22:56:22 |
magic_rb | i mean, i could technically try this on my oneplus 8t, but maybe not on my primary and only phone lol | 23:10:12 |
| 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 ⭔ | Hmm, haven't dealt with that part of the code yet | 22:33:02 |
pentane ⭔ | 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 |