| 23 Sep 2025 |
 @aloisw:julia0815.de | 25.05 basically, if you prefer I can also prepare a drop of the patch against staging-next. | 16:11:52 |
 Lun | substituting the cmake version seems preferable to me assuming it's workable and there isn't a whole bunch of cruft that broke and needs a proper patch in it | 16:12:36 |
 Grimmauld (migrated to @grimmauld:m.grimmauld.de) | there is also an upstream patch | 16:12:49 |
| Grimmauld (migrated to @grimmauld:m.grimmauld.de) | imo fetching that is the way | 16:12:59 |
| Grimmauld (migrated to @grimmauld:m.grimmauld.de) | Actually should be fine | 16:15:05 |
| Grimmauld (migrated to @grimmauld:m.grimmauld.de) | the cmake files aren't being installed anyways lol | 16:15:12 |
| Grimmauld (migrated to @grimmauld:m.grimmauld.de) | (checked against current unstable) | 16:15:26 |
| Grimmauld (migrated to @grimmauld:m.grimmauld.de) | i'll diffoscope to make sure i am not missing anything, and then just merge tbh | 16:19:36 |
| Grimmauld (migrated to @grimmauld:m.grimmauld.de) | Ah okay it does break | 16:20:38 |
 emily | whoops. I keep forgetting about 25.05. | 16:26:12 |
| emily | can we just backport the new toml11 version there? it's a pretty self-contained package, could copy-paste it as toml11_4 | 16:26:22 |
| emily | (but I'm ok with whatever you want to do) | 16:26:27 |
| emily | (this ensures more uniform behaviour between Nixpkgs releases though) | 16:26:34 |
| emily | I would rather not go CMake → autotools | 16:26:56 |
| emily | this seems worse than a substituteInPlace if it's not actually truly incompatible | 16:27:13 |
| @aloisw:julia0815.de | https://github.com/NixOS/nixpkgs/pull/445574 is the PR, currently building the package on x86_64-linux and aarch64-linux. | 16:27:24 |
| @aloisw:julia0815.de | Does that matter? 2.93 does not have uniform behaviour either. | 16:27:49 |
| emily | fair | 16:28:01 |
| @aloisw:julia0815.de | And there I would view a sudden behaviour change in 25.05 more critical. | 16:28:09 |
| emily | oh, I only meant backport it as a separate version, not backport the bump | 16:28:23 |
| emily | just for Git. but yeah, reasonable. | 16:28:29 |
| @aloisw:julia0815.de | Also 25.05 is only slightly more than 2 more months, I think I can manage the manual backports. | 16:28:46 |
 hexa | 25.05 is until EOY | 16:29:09 |
| hexa | so slightly more than 3 months 😄 | 16:29:17 |
| @aloisw:julia0815.de | Right, the releases are usually at the end of the month. Maybe I'll move patches after cargoDeps in the next manual backport then, this way the following ones shouldn't conflict due to the line being out of context. | 16:30:47 |
 Vladimír Čunát | i.e. 25.05 is just past its half-life. | 16:30:57 |
| Grimmauld (migrated to @grimmauld:m.grimmauld.de) | well, we didn't get another 24.11 staging cycle after 25.05 released, sooo the effective maintenance it gets might be less | 16:31:04 |
| hexa | yeah, staging cycle scheduling for three target branches is a mess | 16:32:25 |
| @aloisw:julia0815.de | It does not matter for Lix backports though. | 16:32:38 |
| Vladimír Čunát | The first missing merge is from May 18 | 16:32:41 |
