20 May 2021 |
_hc | I should be able to sort it out today | 12:35:41 |
| dupondje left the room. | 12:45:33 |
| @freenode_djBRDF:matrix.org left the room. | 13:17:13 |
| @freenode_djBRDF:matrix.org joined the room. | 13:18:04 |
| @freenode_djBRDF:matrix.org left the room. | 13:32:19 |
| @freenode_djBRDF:matrix.org joined the room. | 13:33:04 |
cdesai | https://salsa.debian.org/android-tools-team/admin/-/issues/21 (bundletool packaging) | 13:34:37 |
_hc | proletarius101: could you send me your SSH public key? via matrix is fine | 14:08:27 |
proletarius101 | In reply to @eighthave:matrix.org proletarius101: could you send me your SSH public key? via matrix is fine Sent via PM | 14:13:49 |
proletarius101 | https://gitlab.com/fdroid/fdroidclient/-/merge_requests/978 is blocked by https://gitlab.com/fdroid/fdroidclient/-/merge_requests/989, FYI | 14:14:14 |
proletarius101 | !978 is about comprehensive dependency scanning of the fdroidclient, including their licence compliance calculation | 14:15:41 |
proletarius101 | * r!978 is about comprehensive dependency scanning of the fdroidclient, including their licence compliance calculation | 14:15:47 |
proletarius101 | * !978 is about comprehensive dependency scanning of the fdroidclient, including their licence compliance calculation | 14:15:57 |
| @freenode_djBRDF:matrix.org left the room. | 14:22:11 |
| @freenode_djBRDF:matrix.org joined the room. | 14:24:11 |
| TheAssassin left the room. | 15:39:34 |
@obfusk:matrix.org | In reply to @proletarius101:matrix.org But probably they won't drop the apk format, since so many apps in China are not delivered by Google Play iiuc you upload the AAB to google play, which then delivers APKs customised for the user's device. so I don't think APKs are going anywhere. though you won't be able to upload new apps to google play w/o google having access to the signing key. | 15:45:05 |
proletarius101 | In reply to @obfusk:matrix.org iiuc you upload the AAB to google play, which then delivers APKs customised for the user's device. so I don't think APKs are going anywhere. though you won't be able to upload new apps to google play w/o google having access to the signing key. yeah Google's signing key is the core of this change | 15:46:05 |
proletarius101 | In reply to @obfusk:matrix.org iiuc you upload the AAB to google play, which then delivers APKs customised for the user's device. so I don't think APKs are going anywhere. though you won't be able to upload new apps to google play w/o google having access to the signing key. * yeah Google's control of the signing key is the core of this change | 15:46:16 |
| @freenode_djBRDF:matrix.org left the room. | 15:47:04 |
| @freenode_djBRDF:matrix.org joined the room. | 15:48:35 |
@obfusk:matrix.org | In reply to @eighthave:matrix.org 幸猫: yes! there are many things we could use help running, including verification.f-droid.org, gitlab runners, the forum, contributor buildserver instances, etc. what are you most interested in? they're all Debian. w/o further details on the setup and what needs doing I'd say verification, buildservers, maybe runners. | 15:51:48 |
| @freenode_djBRDF:matrix.org left the room. | 16:51:49 |
| jomo_ left the room. | 16:52:02 |
_hc | for all of them, first there just needs to be updates and make sure they stay up and running. | 16:53:41 |
_hc | If you're looking for more, there is creating an ansible setup to make an "auto-scaling" gitlab runner and have ansible manage the gitlab runner tokens. | 16:53:45 |
_hc | verification is currently hacked together. Ideally it would fully recreatable with an ansible setup that would be based on the builserver ansible setup | 16:54:04 |
| @freenode_djBRDF:matrix.org joined the room. | 16:54:27 |
_hc | verification could also be developed further, like making run the builds in Docker rather than a VM, since that would be faster, and security isn't so importnat for verification | 16:54:44 |
_hc | 幸猫: I think the main thing is for someone to take ownership of some of those boxes | 16:55:06 |