| 26 Jan 2026 |
|  Mohamed Hisham Abdelzaher joined the room. | 21:08:44 |
| 27 Jan 2026 |
 eveeifyeve | Hey hydra team swift is currently broken, would it be best to notify everyone in hydra about it? | 03:46:19 |
| eveeifyeve | * Hey hydra team swift is currently broken, would it be best to notify everyone in hydra about it? | 03:46:30 |
| eveeifyeve | * Hey hydra team swift is currently broken, would it be best to notify everyone in hydra about it till it's fixed? | 03:46:38 |
 vcunat | I don't get what you mean. | 06:01:13 |
| eveeifyeve | Swift is currently broken, a lot of packages like jetbrains.idea for example are broken because they need swift. | 06:53:09 |
| vcunat | Yes, I know that. | 06:53:29 |
| vcunat | And why is that related to this channel? | 06:53:42 |
| eveeifyeve | Because It might cause darwin builds to fail for certain applications in hydra. | 06:54:13 |
| eveeifyeve | * Because It might cause darwin builds to fail for certain/to random applications in hydra. | 06:54:34 |
| eveeifyeve | I am looking at the issue myself, but I feel not confident that I can't find a fix. | 06:54:55 |
| eveeifyeve | I have had thoughts for now just marking it broken. | 06:55:07 |
| vcunat | This channel is supposed to be about hydra-the-software. | 06:55:28 |
| eveeifyeve | So probably best to move this convo to https://matrix.to/#/#dev:nixos.org? | 06:56:04 |
| eveeifyeve | * So probably best/wise to move this convo to https://matrix.to/#/#dev:nixos.org? | 06:56:20 |
| vcunat | Probably. It's a catch-all. There's also #macos:nixos.org as I think you care about a darwin-specific failure. | 06:57:02 |
 loudgolem | I just want to say eveeifyeve I don't understand this double negative at all I feel not confident that I can't find a fix | 06:57:36 |
| loudgolem | * I just want to say eveeifyeve I don't understand this double negative at all I feel not confident that I can't find a fix
Edit: let's not discuss it here
| 06:58:04 |
| 28 Jan 2026 |
|  @jan:smittie.de left the room. | 17:42:14 |
| 29 Jan 2026 |
|  hyperparabolic joined the room. | 02:46:28 |
| 1 Feb 2026 |
|  Fernando Rodrigues changed their display name from SigmaSquadron to Fernando Rodrigues. | 10:42:20 |
| 3 Feb 2026 |
 Corngood | I had a build (https://hydra.nixos.org/build/320776458/nixlog/14) fail on maximum-snail.mac.nixos.org
LLVM ERROR: IO failure on output stream: No space left on device
The dotnet build system happens to print df periodically:
DirSize Before Building runtime
Filesystem Size Used Avail Use% Mounted on
/dev/disk3s7 229G 222G 7.1G 97% /nix
| 23:43:31 |
| Corngood | * I had a build (https://hydra.nixos.org/build/320776458/nixlog/14) fail on maximum-snail.mac.nixos.org
LLVM ERROR: IO failure on output stream: No space left on device
The dotnet build system happens to print df periodically:
DirSize Before Building runtime
Filesystem Size Used Avail Use% Mounted on
/dev/disk3s7 229G 222G 7.1G 97% /nix
is this the right place to mention that?
| 23:43:43 |
| 4 Feb 2026 |
 hexa | no, this is #NixOS Infrastructure terriitory, but I already increased the gc interval yesterday | 00:22:41 |
| Corngood | Ah yeah, sorry. Someone literally just said "This channel is supposed to be about hydra-the-software.". Thanks | 00:24:02 |
|  Acquisition X joined the room. | 02:43:29 |
| 5 Feb 2026 |
| Acquisition X | Hi | 05:46:43 |
|  Gaétan Lepage joined the room. | 17:05:56 |
| Gaétan Lepage | I have a question about declarative projects.
Let's say, your project has a jobset named old-name.
You want to rename it to new-name.
When using regular non-declarative projects, you could edit the configuration of each jobset and, among other things, rename it.
But when using declarative projects, if you cange the name of the jobset from old-name to new-name, how can Hydra differentiate betwee:
- DROP jobset
old-name and create new jobset new-name
- RENAME jobset
old-name to new-name
?
The ideal would be to let users manually set the jobset's id in the spec file. Because I guess that Hydra can only rely on jobset names to differentiate them right? | 17:12:45 |
| Gaétan Lepage | * I have a question about declarative projects.
Let's say, your project has a jobset named old-name.
You want to rename it to new-name.
When using regular non-declarative projects, you could edit the configuration of each jobset and, among other things, rename it.
But when using declarative projects, if you change the name of the jobset from old-name to new-name, how can Hydra differentiate betwee:
- DROP jobset
old-name and create new jobset new-name
- RENAME jobset
old-name to new-name
?
The ideal would be to let users manually set the jobset's id in the spec file. Because I guess that Hydra can only rely on jobset names to differentiate them right? | 17:13:36 |
