| 2 Nov 2025 |
 Winter | (specifically 455043) | 22:25:08 |
| Winter | and staging obviously doesn’t get merged into -next | 22:25:28 |
| Winter | am i just naive | 22:25:33 |
 Lun | is it since we swapped to merge queues? | 22:25:45 |
| Winter | no idea | 22:26:54 |
| Winter | i’d be surprised if that had something to do with it | 22:27:03 |
 Grimmauld (any/all) | the PR was opened before staging-next was created and not pushed since, so i just assumed it had no commits that were not already on staging-next and that worked out | 23:24:39 |
| Grimmauld (any/all) | shit, i botched the musl valgrind, working on it | 23:31:42 |
 ivy | also sorry guys one of my prs woyld have literally caused every single package to rebuild | 23:40:37 |
| Winter | nothing is stopping that from going in staging :-) just not -next | 23:41:09 |
| ivy | no i mean it is in staging-next | 23:41:44 |
| Winter | oh | 23:41:51 |
| ivy | like it was in staging | 23:41:57 |
| ivy | now its in next | 23:42:01 |
| Winter | i mean this is how staging works | 23:42:14 |
| Winter | so i’m not sure what you’re apologizing about | 23:42:20 |
| ivy | yeah i know but just like its every single package | 23:42:42 |
| ivy | because of buildEnv | 23:42:58 |
| ivy | one line change smh | 23:43:29 |
| ivy | the outputa dont even change smh its just the hash smh | 23:43:45 |
| ivy | * | 23:44:27 |
| ivy | there is no remorse for hydra | 23:44:48 |
| Winter | fwiw this would only have been an issue if it got in after -next had already started, probably everything has to rebuild anyways ;^) | 23:44:59 |
| Winter | so no need to apologize | 23:45:05 |
| ivy | hopefully it everything had to rebuild anyway | 23:45:30 |
 samasaur | can personally confirm that everything downstream of cmake had to, so everything on darwin | 23:46:08 |
| Grimmauld (any/all) | Ugh, now there is ghc eval fails?? | 23:46:27 |
| Winter | my favorite | 23:46:37 |
| Winter | :/ | 23:46:38 |
| ivy | okay cool so its fine | 23:48:12 |
