Hydra | 393 Members | |
| 110 Servers |
| Sender | Message | Time |
|---|---|---|
| 15 Feb 2022 | ||
* So I'm trying to update the hydra package in nixpkgs, and ran into migrations failing because the pgcrypto postgres extension was missing. Seems odd to me though that this wouldn't have been caught by NixOS tests. Has everyone who runs a Hydra done CREATE EXTENSION pgcrypto; manually, or am I missing a place where that's done within hydra (a plain rg pgcrypto on the hydra repo didn't yield any results), or what might be happening here? | 16:45:55 | |
Aah, apparently gen_random_uuid() is built into postgres starting from 13.x | 16:49:57 | |
In reply to @linus.heckemann:matrix.mayflower.deAh if you're touching it anyway (I know people love when I say that - could you replace --set HYDRA_RELEASE ${version} \ with --set-default HYDRA_RELEASE ${version} \? I don't think it's worth its own PR | 16:51:14 | |
| lol | 16:51:31 | |
| yeah can do that | 16:51:37 | |
| thanks ;) | 16:51:42 | |
In reply to @linus.heckemann:matrix.mayflower.deThanks for looking into that. | 17:08:44 | |
| thanks for starting the work, I picked your commit as a base :) | 17:09:00 | |
das_j: hm, why exactly should that be --set-default? Changing that to something other than the running package seems weird. | 17:14:35 | |
In reply to @linus.heckemann:matrix.mayflower.deI'm overriding the src of the package locally and the postPatch is not affected by that override | 17:15:03 | |
| aah fair | 17:16:20 | |
| das_j: Rick (Mindavi): would you care to be maintainers as well? With https://github.com/NixOS/nixpkgs/pull/158948 it doesn't currently have any maintainers. | 19:01:50 | |
In reply to @linus.heckemann:matrix.mayflower.deYeah why not. Will probably not give me substantially more GH notifications 🤷 | 19:05:31 | |
| I'm running it from nixpkgs anyway, so don't mind reviewing now and then | 19:08:40 | |
| sweet, so the package goes from 1 to 0 to 3 maintainers :D | 19:08:43 | |
| Hm, I've been trying to mix lovesegfault's changes from https://github.com/NixOS/nixpkgs/pull/157072 in as well. Not sure if this is actually something we should do or not though | 19:27:08 | |
| I think it does make sense to have a single version of hydra in nixpkgs. And I think the hydra package in nixpkgs is a bit "second-class" given that upstream development and the hno deployment use flakes. | 19:31:13 | |
| Any opinions? | 19:31:33 | |
| Though I'm pretty sure that if we have only a single hydra package, we should also only have a single hydra test :) | 19:31:50 | |
| * Though I'm pretty sure that if we have only a single hydra package, we should also only have a single hydra test, so if I do pull in lovesegfault's changes I'll also add that :) | 19:33:27 | |
In reply to @linus.heckemann:matrix.mayflower.deMy opinion is that we should have only 1 version. One can always override if need be | 19:49:31 | |
| I've opened https://github.com/NixOS/nixpkgs/pull/160202 with the current state, it's not quite finished yet though. | 19:53:34 | |
| 16 Feb 2022 | ||
| 06:09:17 | ||
In reply to @linus.heckemann:matrix.mayflower.deagreed. The multiple package thing is a relict from https://github.com/NixOS/nixpkgs/pull/83600 | 14:14:33 | |
A tricky thing is there are quite likely still people using hydra before the old version. Maybe it would make sense to have pkgs.hydra be the default, and pkgs.hydra-migrate be available as a fallback. | 14:46:58 | |
| 17 Feb 2022 | ||
| I thihk hydra's UI does not show all jobsets: https://hydra.nixos.org/project/nixpkgs I expected to see | 08:23:57 | |
| * I think hydra's UI does not show all jobsets: https://hydra.nixos.org/project/nixpkgs I expected to see | 08:24:10 | |
| yup, jobsets can be set hidden | 11:27:15 | |
| 13:31:32 | ||
| Ah, tricky. | 21:21:58 | |