| 14 Aug 2022 |
 @linus:schreibt.jetzt | Rick (Mindavi): did you look at alternative UUID implementations when you were fixing UUID4-Tiny for aarch64? I seem to remember an alternative being mentioned somewhere, but don't remember what it was... | 13:17:21 |
 Mic92 | How do I need to specify remote builders? https://github.com/nix-community/infra/commit/75415763e156af5460cf41a4e72f0af4a6ed9864#diff-2404a9483fea5d1ff23e25a108e54c5a2a9d5df3bed79a506b0738659c95e08bR77 | 14:23:31 |
| Mic92 | Hydra does not like the format that I am using: https://hydra.nix-community.org/build/17198636 | 14:24:03 |
 hexa | without ssh://? | 15:17:26 |
 ajs124 | yeah, hydra have a separate parser for the machine file | 15:18:21 |
 Arian | Redacted or Malformed Event | 15:28:00 |
 Rick (Mindavi) | In reply to @linus:schreibt.jetzt
Rick (Mindavi): did you look at alternative UUID implementations when you were fixing UUID4-Tiny for aarch64? I seem to remember an alternative being mentioned somewhere, but don't remember what it was... I didn't, and since I've never written perl I didn't really feel qualified to fix the implementation anyway. But I'm sure there should be simple alternatives | 16:32:35 |
| Rick (Mindavi) | This is all I've got, I think: https://github.com/NixOS/hydra/issues/1209 | 16:33:32 |
| @linus:schreibt.jetzt | fair enough, thanks :) | 17:27:14 |
|  K900 joined the room. | 18:11:59 |
| K900 | OK whomst do I poke here to get https://github.com/NixOS/hydra/pull/1243 merged | 18:12:22 |
| ajs124 | In reply to @k900:0upti.me
OK whomst do I poke here to get https://github.com/NixOS/hydra/pull/1243 merged das_j | 18:16:42 |
 das_j | In reply to @andreas.schraegle:helsinki-systems.de
das_j ajs124 | 18:17:29 |
| K900 | 
Download image.png | 18:17:59 |
|  @weebsorceress:matrix.org joined the room. | 19:05:52 |
| @weebsorceress:matrix.org left the room. | 19:08:50 |
| 15 Aug 2022 |
 @ulrikstrid:matrix.org | Is this the only thing I need to set to get remote cache upload working for hydra? https://github.com/NixOS/nixos-org-configurations/blob/master/delft/hydra.nix#L33 | 11:43:29 |
| @ulrikstrid:matrix.org | And the aws stuff obviously | 11:43:51 |
 Amanda (she/her) | That's all I needed for my minio cache, yeah | 14:37:29 |
|  ReplayCoding changed their display name from ReplayCoding (she/her) to ReplayCoding. | 16:24:36 |
|  h7x4 set a profile picture. | 17:21:10 |
|  pbsds changed their display name from pederbs to pbsds. | 23:19:28 |
| 16 Aug 2022 |
| K900 | In reply to @k900:0upti.me
OK whomst do I poke here to get https://github.com/NixOS/hydra/pull/1243 merged Bump | 18:42:44 |
| das_j | In reply to @k900:0upti.me
Bump ajs124 | 18:42:56 |
|  -=h0p3=- joined the room. | 21:45:16 |
| 17 Aug 2022 |
|  @leons:is.currently.online joined the room. | 08:55:37 |
| @leons:is.currently.online | I haven't used Hydra much and have a question to see whether it might be a suitable tool for my usecase. I maintain a repository which defines some FPGA-targets for an embedded OS and I am providing pre-built FPGA bitstreams for these targets, so people don't have to install the heavyweight proprietary FPGA toolchains (>= 50GB binary blob) themselves.
I'm already building all of this with Nix, but using regular CI infrastructure like GitHub Actions or TravisCI to automate this is infeasible (can't redistribute the binary blob and it exceeds CI resource limitations).
If I were to build this with Hydra, can I
- manually add the proprietary toolchain to the build system's nix-store as a garbage collector root and have Hydra use that for its builds, and
- instruct Hydra to not offer / publish the proprietary toolchain itself? While it should be perfectly legal to compile a bitstream and redistribute that final artifact, I am not allowed to redistribute the toolchain itself. I do want to make the final artifacts available somewhere, although that doesn't have to be through Hydra directly.
| 09:05:59 |
 Sandro |
- required file
- not easily
| 09:31:52 |
| ajs124 | 1. maybe/sort of yes. we build stuff like displaylink on our internal hydra, where you need to download the zip manually and agree to the license.
2. sure. hydra comes with a binary cache, but barely anyone uses it. you could just have a hook to only copy the bitstreams or use hydra-support stuff, to offer downloads. | 09:31:58 |
| das_j | In reply to @andreas.schraegle:helsinki-systems.de
1. maybe/sort of yes. we build stuff like displaylink on our internal hydra, where you need to download the zip manually and agree to the license.
2. sure. hydra comes with a binary cache, but barely anyone uses it. you could just have a hook to only copy the bitstreams or use hydra-support stuff, to offer downloads. We should finally implement a setting to disable the binary cache | 09:32:33 |
