| 26 Sep 2025 |
 emily | AIUI, they fixed this upstream, so we may be due for a fetchpatch3 that is strictly better than both | 19:46:51 |
| emily | but frankly… I am going to want a test suite | 19:46:59 |
| emily | since we have been bitten once already there | 19:47:10 |
| emily | btw did you know that patch can't handle the diffs that diff/git diff produce for filenames with spaces in them? :( | 19:50:08 |
| emily | and that Meson deliberately uses spaces in its source tree? | 19:50:23 |
 samasaur | okay I think I was doing this. is fetchpatch still better than fetchpatch2 with full_index=1? | 19:50:43 |
| emily | well, sometimes the patch is not on GitHub | 19:50:54 |
| emily | but they should be mostly equivalent I think, I forget if there are any other fetchpatch2 regressions | 19:51:03 |
| emily | the main advantage is: we should deprecate fetchpatch2 as soon as we have fetchpatch3 | 19:51:16 |
| emily | whereas fetchpatch will take a long time to migrate | 19:51:24 |
| emily | so every new user of fetchpatch2 makes it more likely we continue using 3 patch fetchers in the tree rather than 2 | 19:51:39 |
 ghpzin | Checked again and unfortunately I think it would only make patches situation worse, will see how PR looks like. | 19:51:55 |
| ghpzin | Checked again and unfortunately I think it would only make patches situation worse (because of mixing vendored and fetchpatch), will see how PR looks like. | 19:52:17 |
| ghpzin | Checked again and unfortunately I think it would only make patches situation worse (because of mixing vendored and fetchpatch patches on different versions).
Will see how PR looks like. | 19:52:35 |
| 27 Sep 2025 |
 Vladimír Čunát | We still have quite a few blockers for future nixpkgs-unstable channel:
https://hydra.nixos.org/job/nixpkgs/staging-next/unstable#tabs-constituents
mainly around stdenvBootstrapTools. | 08:04:49 |
 Grimmauld (any/all) | i am down to around 4 cmake 4 fails on my system, one of which fixed by https://github.com/NixOS/nixpkgs/pull/446331 | 08:39:05 |
 K900 | What the fuck do you have that uses fltk lol | 08:45:24 |
| Grimmauld (any/all) | freecad | 09:23:09 |
| Grimmauld (any/all) | well, freecad uses vtk which pulls all kinds of crap (including, but not limited to, fltk) | 09:25:10 |
| Grimmauld (any/all) | opencollada-blender needs a fix too, and after that (and periodic merge) i might actually be able to build my system on next | 09:26:34 |
| Grimmauld (any/all) | 
Download image.png | 21:46:59 |
| Grimmauld (any/all) | another batch of fails, but its less and less bad. Might get there tomorrow... | 21:47:27 |
| 28 Sep 2025 |
| Vladimír Čunát | thunderbird.src failed? How's that possible? | 05:25:28 |
 Sami Liedes | Ah, gfortran <3 That is a fun part of things... | 05:31:21 |
| 29 Sep 2025 |
|  @brian:bmcgee.ie left the room. | 13:40:43 |
|  xxlpitu joined the room. | 18:37:08 |
| xxlpitu | hi, I have a change that fixes a bug in pkgs/build-support/rust/fetch-cargo-vendor-util.py but I'm not sure if I should open a PR to merg in to staging or staging-next. This changes causes every rust package to rebuild. | 18:41:49 |
| xxlpitu | * hi, I have a change that fixes a bug in pkgs/build-support/rust/fetch-cargo-vendor-util.py but I'm not sure if I should open a PR to merge into staging or staging-next. This changes causes every rust package to rebuild. | 18:42:14 |
| K900 | staging | 18:45:33 |
| K900 | Too late for next now | 18:45:36 |
