| 29 Apr 2025 |
 Mic92 | In reply to @hexa:lossy.network
I'm a bit surprised, why is hydra on 2.24.14 now Indeed. I can have a look. Maybe we switched back to the nixpkgs version of hydra? | 17:39:39 |
 hexa | I'm surprised the hydra-dev module doesn't force us onto the upstream hydra package | 17:40:03 |
| hexa | because the module is named differently in nixpkgs iirc | 17:40:17 |
| Mic92 | I thought it was supposed to be this way. | 17:41:10 |
| Mic92 | I have a look | 17:41:14 |
| Mic92 | services.hydra-dev.package = pkgs.hydra;
| 17:42:27 |
| Mic92 | nixos-infra has this line | 17:42:37 |
| hexa | which was redundant when we had the overlay | 17:43:06 |
| hexa | but now points to the wrong package | 17:43:10 |
| Mic92 | yes | 17:43:13 |
| hexa | ok, so let's drop that and restore the nix overlay? | 17:43:26 |
| Mic92 | https://github.com/NixOS/infra/pull/667 | 17:43:38 |
| Mic92 | Why do we need the nix overlay? | 17:43:47 |
| Mic92 | Is nix.package not enough? | 17:43:53 |
| Mic92 | I do not want to break random other packages by overriding nix in different places | 17:44:16 |
| hexa | we don't set nix.package, but we could | 17:44:18 |
| Mic92 | Ok. I can add this | 17:44:55 |
| hexa | we were tracking what ever nix was shipped with hydra on all the build/ machines | 17:44:58 |
| hexa | which was pointless for haumea and pluto | 17:45:13 |
| hexa | so maybe just in hydra.nix this time | 17:45:22 |
 John Ericson | https://github.com/NixOS/hydra/pull/1482 Mic92 left some questions on that | 18:23:33 |
| Mic92 | hexa (signing key rotation when): no specific procedure required for reboot on mimas, right? | 18:53:50 |
 Vladimír Čunát | I don't think so. | 18:59:56 |
| hexa | no | 19:26:32 |
| John Ericson | looks good, approved | 20:14:02 |
| 30 Apr 2025 |
 Jeremy Fleischman (jfly) | Shahar "Dawn" Or (mightyiam) and I would like to discuss deploying https://github.com/molybdenumsoftware/pr-tracker to official infrastructure at this week's team meeting. | 08:59:56 |
 Sandro | The key difference to the other projects is, that it stores the results in a database, right? | 12:46:24 |
| Sandro | Does it already expose a minimal web ui like nixpk.gs? I have interest in trying to deploy it because the existing pr-tracker performs not so well for me on our hardware due to io constraints | 12:47:30 |
 adamcstephens | This looks great. I see you're suggesting users could subscribe to some events through pr-tracker. If you'll be getting installed as a webhook receiver for the repo, would you be willing to route all webhooks you receive on to other targets on request? e.g. so others could leverage the access you've received to build their own tooling? Or would that be a level of service you'd prefer not to commit to? | 12:54:28 |
| adamcstephens | If not, would that be a standalone app we should consider? | 12:55:03 |
