| 3 Oct 2025 |
 K900 | qtdeclarative is fine here? | 14:02:49 |
 Grimmauld (any/all) | apparently dead on x86_64-darwin | 14:03:12 |
| K900 | Also uhh | 14:03:17 |
| K900 | Jun 17, 2021
| 14:03:18 |
| K900 | Pick-to: 6.2
| 14:03:27 |
 dramforever | wait | 14:03:35 |
| dramforever | is it normal that we're building qt5 | 14:03:44 |
| K900 | Yes | 14:03:58 |
| K900 | We have both 5 and 6 for the time being | 14:04:08 |
| K900 | There's a variety of things people care about that are on 5 | 14:04:31 |
| dramforever | https://github.com/llvm/llvm-project/issues/74070 | 14:05:21 |
| dramforever | this makes me think it triggers that under specific circumstances | 14:05:35 |
| dramforever | and we just happened to finally run into it | 14:05:47 |
| dramforever | and qt never fixed it for qt5 probably | 14:06:24 |
| K900 | Then we can try it I guess | 14:07:17 |
| K900 | And if it works probably submit it to https://invent.kde.org/qt/qt/qtbase/-/merge_requests | 14:08:01 |
| dramforever | so that was hopefully all of the channel blockers | 14:10:16 |
| dramforever | knocks on wood | 14:10:26 |
| dramforever | can we fix the "arm64" in config.host_triple one without rebuilding everything? | 14:12:37 |
| K900 | What script is that in? | 14:13:59 |
| dramforever | llvm/test/lit.cfg.py from llvm 21 | 14:18:40 |
| K900 | Oof | 14:18:55 |
| K900 | Wait how do we not trigger that on like | 14:19:02 |
| K900 | Everything | 14:19:03 |
| K900 | Then | 14:19:03 |
| dramforever | i have no idea https://hydra.nixos.org/build/308137528/nixlog/1 | 14:21:03 |
| dramforever | i can't even find this llvm 21 | 14:21:08 |
| dramforever | nevermind it's because i'm on linux | 14:21:54 |
| Grimmauld (any/all) | we still have a LOT of regressing jobs | 14:23:10 |
| Grimmauld (any/all) | but we'll also soon have ZHF | 14:24:23 |
