!UUYziobKGGxpovWyAN:nixos.org

Robotnix

239 Members
Build Android (AOSP) using Nix | https://github.com/nix-community/robotnix73 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
5 Nov 2025
@magic_rb:matrix.redalder.orgmagic_rbisnt ccache deprecated?12:07:39
@magic_rb:matrix.redalder.orgmagic_rbthats what the docs said12:07:46
@atemu12:matrix.orgAtemuStill worked with 22.214:54:33
6 Nov 2025
@puffnfresh:chat.home.brianmckenna.orgpuffnfreshhttps://github.com/nix-community/robotnix/pull/32406:12:16
@cyclopentane:aidoskyneen.eupentanenice, thanks, gonna test it one of these days!21:48:32
@cyclopentane:aidoskyneen.eupentanewhich method did you use to get a list of all new APEX packages in android 16? looking into apkcerts.txt in the target files package, or something in these lines?21:49:17
@cyclopentane:aidoskyneen.eupentane bit of context: I'm a bit catious about declaring signing as "officially supported" again, since the AOSP sign_target_files_apks tool doesn't validate whether all APKs that were signed with the test keys during the main build have in fact been re-signed with the release ones. I'm considering writing some sort of validation script that looks at META/apkcerts.txt and META/apexkeys.txt in target_files.zip to validate whether the key mappings and APEX package names defined in the module systems cover everything that needs to be re-signed 22:29:24

Show newer messages


Back to Room ListRoom Version: 6