| 7 Oct 2025 |
 niklaskorz |
the more pragmatic way is to just accept the fact that clang
produces more warnings than gcc, and to filter out / triage the warnings
from the compilation log
| 11:06:54 |
| niklaskorz | so unless you happen to know a way to make clang also treat gettext as a built-in, I'll open the PR to disable the warning now on coreutils | 11:08:54 |
 Grimmauld (any/all) | Hey, so uh, i made a mistake, and i am wondering what the best way of fixing it is:
https://github.com/NixOS/nixpkgs/pull/444579
This was targetting staging, and i merged it before i saw the cycle was started. This means the break is now in master, the fix was merged to staging, but is not yet at master. Do i just open a new PR against master with the same exact patch and merge that? | 11:27:39 |
 hexa | yes | 11:37:13 |
 Randy Eckenrode | No. I’m surprised there’s not an annotation for it. | 11:40:29 |
| niklaskorz | build passing: https://github.com/NixOS/nixpkgs/pull/449474 | 13:02:14 |
 K900 | I'm cooking qt 6.10 | 13:03:57 |
| K900 | Hopefully will be done in like an hour | 13:04:08 |
 vcunat | We're still changing stdenvs at this point, so I believe that's OK. | 13:08:24 |
| K900 | https://github.com/qt/qtconnectivity/blob/1b09545fb02a112b59148ea26ad2ca734dc0526a/src/nfc/configure.cmake#L15 | 13:13:02 |
| K900 | Love how they've been shipping a typo for nine months | 13:13:09 |
| K900 | And no one notice | 13:13:19 |
| K900 | * And no one noticed | 13:13:20 |
