| 8 Nov 2023 |
 K900 | No | 14:57:29 |
 @linus:schreibt.jetzt | nah, just do it :D | 14:57:32 |
| K900 | Just do it | 14:57:33 |
| K900 | lol | 14:57:36 |
 Rick (Mindavi) | If you are able to replicate the features in a more common / liked language I think adoption will take care of itself | 15:45:28 |
| Rick (Mindavi) | Nobody really started anything yet as far as I recall or have heard though. | 15:45:57 |
 cransom | the last shake up that i can recall was when hercules started, though i don't think it was ever intended to replace hydra. | 16:05:15 |
| 9 Nov 2023 |
|  @bootstrapper:matrix.org changed their display name from snick to Ido Samuelson. | 06:33:42 |
|  @aloisw:kde.org joined the room. | 08:53:15 |
| 10 Nov 2023 |
|  connor (burnt/out) (UTC-8) changed their display name from connor (he/him) (UTC-4) to connor (he/him) (UTC-5). | 12:33:38 |
| 12 Nov 2023 |
|  @lehmanator:gnulinux.club joined the room. | 12:02:38 |
|  toonn changed their profile picture. | 17:53:48 |
|  @teutat3s:pub.solar joined the room. | 19:21:55 |
| @teutat3s:pub.solar left the room. | 19:22:44 |
| 13 Nov 2023 |
|  Greg Burd changed their profile picture. | 15:41:45 |
 Philip Taron (UTC-8) | Apologies if there's a better room for this.
For the NixOS 23.11 release, how much of a problem is this list of evaluation errors? I took a look at https://github.com/NixOS/nixpkgs/issues/265948 and didn't see something that definitively answered this question.
https://hydra.nixos.org/eval/1801638#tabs-errors | 17:48:01 |
| K900 | Not a problem | 17:48:15 |
| K900 | Hydra simply skips packages that don't evaluate | 17:48:24 |
| K900 | And most of those are expected failures because of unfree licenses or packages marked broken | 17:48:53 |
| K900 | Also, ZHF doesn't literally mean "reach 0 failures or die", and it doesn't mean "nothing is marked broken" | 17:49:12 |
| Philip Taron (UTC-8) | Thanks, K900 ⚡️ . Is there a way to cause Hydra to "triage" known evaluation errors so that "real" evaluation errors are highlighted? | 17:51:24 |
| K900 | Generally, "everything that should eval evals" is ~enforced by ofborg | 17:51:48 |
| K900 | So it's not something you need to look at closely | 17:52:08 |
| Philip Taron (UTC-8) | Got it. I'll direct my attention elsewhere. Thanks for the information! | 18:06:37 |
| 14 Nov 2023 |
|  @vyls:matrix.org left the room. | 18:21:23 |
| @vyls:matrix.org joined the room. | 18:21:32 |
| @vyls:matrix.org left the room. | 18:22:26 |
| 15 Nov 2023 |
|  Marius joined the room. | 13:45:07 |
| Marius | Hello. I set up an Hydra server for doing some custom CI of a package manager (portmod), and I had a wrongly written fetch script for a fixed output derivation. I now fixed it, but Hydra doesn’t re-evaluate it (certainly cause the result set end up having the same hash). Is there some way I can force it rebuild all failed derivation according to a new definition even if the hash is identical?
(I already had this problem once, and it seems changing the hash of the dependant and re-evaluating wasn’t enought, but I had to change the name anyway, which resulted in a different hash and so a rebuild) | 14:47:28 |
| Marius | * Hello. I set up an Hydra server for doing some custom CI of a package manager (portmod), and I had a wrongly written fetch script for a fixed output derivation. I now fixed it, but Hydra doesn’t re-evaluate it (certainly cause the result set end up having the same hash). Is there some way I can force it to rebuild all failed derivation according to a new definition even if the result set hash is identical?
(I already had this problem once, and it seems changing the hash of the dependant and re-evaluating wasn’t enought, but I had to change the name anyway, which resulted in a different hash and so a rebuild for every sources) | 14:52:08 |
