| 26 Aug 2021 |
 Sandro | Especially for some leaf packages some Darwin user needs to speak up and fix it or provide a patch or a failed test at least | 17:27:49 |
| Sandro | And for x86_64-linux: I can't really speak because I have enough build power right now. | 17:28:24 |
 ryantm | I think the 60 euro per month server I have is enough for r-ryantm. At least until I do more work to parallelize updates. | 17:29:24 |
| ryantm | * I think the 60 euro per month server (build02) I have is enough for r-ryantm. At least until I do more work to parallelize updates. | 17:33:36 |
 @andi:kack.it | Some intelligent build scheduling across the machines (self-hostable nixbuild.net?) would be lovely for that work. Of course you can add all the machines to all the other machines as remote builders but that isn't really that great in my experience. | 17:44:54 |
| @andi:kack.it | ryantm: hows does r-ryantm work? Does it go one package at a time and waits for the builds to finish? | 17:45:19 |
| ryantm | andi-: Currently it has three sources Repology, GitHub releases, PyPi. Whenever it starts a new batch, it queries those and makes a big list of stuff to work on, then it goes through the list one at a time. Builds are usually not the slowest thing. The slowest things are nixpkgs-review and figuring out how many rebuilds a change causes. | 17:58:12 |
| ryantm | Recently, I just made it run those three sources in parallel. | 17:58:38 |
| ryantm | I have lots of ideas for how to make that better, its just a matter of having the time for it. | 17:59:56 |
| ryantm | I canceled my Yubikey order because I found a much better deal expiring today: https://slickdeals.net/f/15242767-yubico-yubikey-5-nfc-2-factor-authentication-security-keys-usb-c-2-for-55-usb-a-2-for-45-free-shipping?src=frontpage | 18:21:35 |
 Mic92 | I would start to prepare build01 for public access. | 20:18:22 |
| Mic92 | to close https://github.com/nix-community/infra/issues/100 | 20:18:36 |
 Jonas Chevalier | what procedure do we want to have in place to hand out builder access? | 20:37:25 |
| Jonas Chevalier | are we just giving access to those who are asking? | 20:37:38 |
| Mic92 | zimbatm: similar to our aarch64 server? | 20:42:22 |
| Mic92 | to people we sort of know maybe? | 20:42:40 |
| Jonas Chevalier | do we have a list of the users somewhere? | 20:43:56 |
| Jonas Chevalier | we don't need to be KYC-strict, but some way of contacting them would be good | 20:44:19 |
| Jonas Chevalier | maybe ask them to be in this Matrix channel | 20:44:26 |
| Jonas Chevalier | if we make the interface clear, we can get more people onboard | 20:45:02 |
| Jonas Chevalier | anybody who is a nixpkgs committer maybe? | 20:45:19 |
| Mic92 | Beeing present in a matrix channel sounds useful | 21:01:49 |
 adisbladis | Sounds like a good bare minimum requirement | 21:02:37 |
| adisbladis | It'd be nice if meta.maintainers could contain SSH keys | 21:03:56 |
| adisbladis | For this kind of stuff | 21:04:05 |
 nix-community-bot | [nix-community/infra] Mic92 pushed 2 commits to build01: https://github.com/nix-community/infra/commit/2ea7b938556c3a8df77fc86819417495d403f57c
Mic92: build01: clone-nixpkgs
Mic92: build01: install some packages for nixpkgs development | 21:25:07 |
| nix-community-bot | [nix-community/infra] Mic92 opened pull request #112: Build01: prepare for users [open] - https://github.com/nix-community/infra/pull/112 | 21:25:26 |
| ryantm | Are we reformatting build01 from scratch? that might be good since it used to have a bunch of secrets on it. | 23:35:28 |
| ryantm | We should also carefully audit that we aren't deploying secrets to it that we don't mean to. | 23:36:08 |
| 27 Aug 2021 |
| Mic92 | I already had the machine re-formatted when the disk was replaced. After that we did not deploy any secrets to it. | 05:54:18 |
