| 19 Aug 2024 |
|  @alejandrosame:matrix.org left the room. | 08:51:37 |
 @janne.hess:helsinki-systems.de | Mic92: invite is coming up :) | 19:40:16 |
| @janne.hess:helsinki-systems.de | Sorry for the long wait | 19:41:34 |
 Mic92 | No problem. I kept myself busy by cleaning up NixOS infra. | 19:51:41 |
| 21 Aug 2024 |
 hacker1024 | Is there a way to tell Hydra not to worry about specific outputs for a (declarative) jobset? E.g. a job's derivation has split out and debug outputs, but I only care about out. If out is available without debug, though, Hydra will still rebuild the derivation, because it tries to realize both output paths. | 08:15:14 |
| hacker1024 | * Is there a way to tell Hydra not to worry about specific outputs for a (declarative) jobset? E.g. a job's derivation has split out and debug outputs, but I only care about out. If out is already available without debug, though, Hydra will still rebuild the derivation, because it tries to realize both output paths. | 08:17:04 |
 @rick:matrix.ciphernetics.nl | Not that I'm aware of, and how can hydra know out doesn't change? | 11:59:34 |
| hacker1024 | In reply to @rick:matrix.ciphernetics.nl
Not that I'm aware of, and how can hydra know out doesn't change? Not sure what you mean by that exactly? If out changes, the path will change too. If the path exists, then it does not need to be rebuilt. | 12:06:26 |
| 22 Aug 2024 |
| @rick:matrix.ciphernetics.nl | If debug changes I'm pretty sure out will always change too, unless it's a ca derivation | 08:29:43 |
