| 21 Sep 2021 |
 Vladimír Čunát | I'm not aware. I just see https://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+base%3Astaging-21.05+is%3Aopen+ | 11:02:23 |
| Vladimír Čunát | It sounds fine to me to do the pair about now. Hydra is relatively idle currently. | 11:02:44 |
 sterni | okay, then I'll try to finish up my PR later | 11:03:09 |
| sterni | how is the staging-next branch-off usually done? by merging staging into staging-next? | 13:05:31 |
 lukegb (he/him) | Yeah. If you're lucky it becomes a fastforward | 13:17:58 |
 hexa | do we want to iterate further on the regressions on staging-next or merge? | 13:59:37 |
| lukegb (he/him) | What regressions do we have left | 14:34:26 |
| hexa | https://shells.darmstadt.ccc.de/~hexa/1706497.html | 14:44:48 |
| hexa | https://hydra.nixos.org/eval/1706497?compare=trunk | 14:46:32 |
| hexa | 1739 jobs, 516 linux hardened failures | 14:48:34 |
| hexa |
error: unused option: DEBUG_INFO_BTF
| 14:49:12 |
| Vladimír Čunát | I'd prefer that trunk-combined evaluation gets fixed before the merge. | 18:05:11 |
| Vladimír Čunát | It's been stuck for about three days now. | 18:05:39 |
| lukegb (he/him) | Makes sense. I'll try and look at the Linux hardened breakages this evening if I can muster the will | 18:05:55 |
| sterni | Vladimír Čunát: wow what happened to it? | 18:38:47 |
| Vladimír Čunát | I don't know; I typically can't immediately see the problem in similar cases. This happens from time to time. | 18:39:38 |
| lukegb (he/him) | yeah, it's the json error | 18:47:40 |
| lukegb (he/him) | 22004f7e8febc6ae6553c44ecd8bf9da9ddc5260 is the first bad commit | 20:18:32 |
| Vladimír Čunát | Hmm, I don't get it yet. When I tried hydra-eval-jobs nixos/release-combined.nix -I . it also started to build during the evaluation at some point, so perhaps some IFD is there (as well?) | 21:41:24 |
| lukegb (he/him) | Hmm, I don't think I had any builds, although I also stopped paying attention | 22:42:09 |
| lukegb (he/him) | changing the options.setuid default from "true" to "false" fixes it for reasons unknown | 23:31:12 |
| 22 Sep 2021 |
|  j-k joined the room. | 15:49:55 |
| lukegb (he/him) | Going to merge staging-next once this eval finished, unless it all goes horribly wrong; Linux hardened is now broken on master anyway (new kernel bump, hardened patchset hasn't updated yet), but I fixed the one(?) remaining working version ;) | 23:05:00 |
| lukegb (he/him) | *eval's builds are mostly settled (which is... probably a few hundred x86_64-darwin builds that seem stuck) | 23:05:25 |
| hexa | hardened kernel maintenance is a mess on master | 23:10:15 |
| hexa | the way it is right now … the hardened kernel delays regular kernel updates | 23:10:35 |
| lukegb (he/him) | In reply to @hexa:lossy.network
the way it is right now … the hardened kernel delays regular kernel updates in this case... it's just broken instead | 23:12:59 |
| lukegb (he/him) | but yeah, I agree, they probably shouldn't be modifying the base kernels because the hardened patchset often lags | 23:13:31 |
 trofi | should the package be marked as broken in metadata? (would it help?) | 23:14:37 |
| lukegb (he/him) | nah, it doesn't really matter | 23:15:07 |
