| 7 Oct 2025 |
 vcunat | Sure, I was mainly... thinking if it's so bad that I need to do it today. | 10:21:18 |
 niklaskorz | ah I see 😄 | 10:21:31 |
| niklaskorz | no worries, PR will be there within the hour | 10:21:49 |
| vcunat | If I can just merged it, now-ish is a good moment. | 10:22:01 |
| niklaskorz | alright, I'm on it | 10:22:10 |
| vcunat | And if it's not too urgent it can be in the next one which will also get into 25.11. | 10:22:45 |
| vcunat | * Or if it's not too urgent it can be in the next one which will also get into 25.11. | 10:22:58 |
| vcunat | But it may take a couple weeks to reach master. | 10:23:14 |
| vcunat | * That would delay it by couple weeks (to reach master). | 10:23:49 |
| vcunat | Oh no, fails to build on darwin:
https://hydra.nixos.org/build/309261595/nixlog/2/tail | 10:25:50 |
| vcunat | I suppose I'll just revert the update, unless someone comes with a fix fast. | 10:27:46 |
| vcunat | (I have no bandwidth to dig into this, especially on darwin.) | 10:28:08 |
| niklaskorz | I guess if we do realize it's breaking other packages in staging-next, we can still cherry-pick it | 10:28:48 |
| niklaskorz | (but as of now I'm not aware of any) | 10:29:29 |
| niklaskorz | sounds like a generic clang issue, not darwin specific | 10:30:12 |
| niklaskorz | relevant diff for gnulib in coreutils 9.8:
- error (exit_failure, errnum, "%s",
+ error (exit_failure, errnum,
_("unable to record current working directory"));
they've removed the format string parameter in all cases
| 10:45:16 |
| niklaskorz | introduced in: https://github.com/coreutils/gnulib/commit/9537853d31b02493f6f3a0ffb9b22bef1ed7217a
reverted in: https://github.com/coreutils/gnulib/commit/9297749090b01720888dceeb5f6dab3d52dcef40 | 10:47:33 |
| niklaskorz | https://lists.gnu.org/r/bug-gnulib/2025-06/msg00325.html | 10:47:58 |
| niklaskorz | the mailing list suggests this was made redundant by a fix in gettext | 10:48:39 |
| niklaskorz | that and:
Do we care about random warnings on non-GNU systems? I thought
that we care about warnings only on GNU systems, because that's
what we develop on and that's where we have some influence on
the compiler (gcc).
meaning upstream's preferred solution would be to just disable this warning
| 10:49:34 |
| vcunat | So we can patch that by some -Wno-error=fool conditioned in coreutils on stdenv.isClang? | 10:54:20 |
| vcunat | * So we can patch that by some -Wno-error=foo conditioned in coreutils on stdenv.isClang? | 10:54:37 |
| niklaskorz | I think so, testing locally now | 10:57:47 |
| niklaskorz | (on darwin) | 10:58:09 |
 K900 | Ah shit | 11:00:50 |
| K900 | Qt 6.10 just dropped | 11:00:50 |
