| 8 Oct 2025 |
dramforever | * is that too late for staging-next yet | 22:27:14 |
dramforever | oh i guess it's only for aarch64-linux literally didn't build | 22:27:44 |
jopejoe1 (4094@39c3) | Thanks for the fix ^^ | 23:28:25 |
| 9 Oct 2025 |
dramforever | dang | 01:27:30 |
dramforever | is onetbb rebuild on x86 too late yet? | 01:27:38 |
K900 | No it's like 200 jobs | 04:34:33 |
dramforever | ship it | 04:35:10 |
K900 | Sure yolo | 04:35:44 |
dramforever | the worst that can happen is just someone will have to fix it again | 04:36:17 |
| @nullcube:matrix.org left the room. | 10:38:40 |
Randy Eckenrode | The Darwin SDK bump has been merged. The minimum supported version is now 14.0. The default SDK is 14.4. Use of older SDKs will throw. All packages using apple-sdk_11, apple-sdk_12, apple-sdk_13, and (most of) apple-sdk_14 have been cleaned up to use the default SDK. Swift currently throws, but samasaur is working on an update to Swift 5.10.1 that will fix it. | 22:38:02 |
Randy Eckenrode | (Posting this here because there’s a chance that a commit to master may reintroduce an old SDK that will break eval on staging.) | 22:38:31 |
| 10 Oct 2025 |
dramforever | Grimmauld (any/all): python3Packages.inkex
ERROR inkex/tester/test_inx_file.py - lxml.etree.SchematronError: lxml.etree was compiled without Schematron supp...
ERROR tests/test_inkex_inx.py - lxml.etree.SchematronError: lxml.etree was compiled without Schematron supp...
https://gitlab.gnome.org/GNOME/libxml2/-/releases/v2.15.0
Support for Schematron is now disabled by default.
| 07:29:31 |
dramforever | is libxml2 rebuild in staging-next too late yet 🫠 | 07:31:31 |
Vladimír Čunát | In principle we can only delay it a bit.
The Python bindings and support for Schematron validation are planned to be removed in the 2.16 release.
| 07:31:41 |
dramforever | i have to imagine inkscape is going to do something about this right | 07:32:14 |
dramforever | or maybe we have to keep giving it 2.15 for a while | 07:32:38 |
Vladimír Čunát | The delay might still be worth it, given that I don't expect 2.16 in NixOS 25.11. | 07:32:45 |
Vladimír Čunát | It would rebuild darwin stdenvs, which would be not great anymore for the current staging-next. | 07:33:12 |
dramforever | so just override in inkscape? | 07:36:48 |
K900 | Just skip the tests? | 07:37:36 |
dramforever | actually python3Packages.inkex -> python3Packages.lxml -> libxml2 | 07:37:38 |
dramforever | good idea, this does seem to be test-only | 07:45:13 |
dramforever | oh great so inkex/tester/test_inx_file.py is testing the .inx files | 07:51:07 |
dramforever | presumably someone is testing them before release... | 07:51:55 |
Grimmauld (any/all) | In reply to @dramforever:matrix.org
Grimmauld (any/all): python3Packages.inkex
ERROR inkex/tester/test_inx_file.py - lxml.etree.SchematronError: lxml.etree was compiled without Schematron supp...
ERROR tests/test_inkex_inx.py - lxml.etree.SchematronError: lxml.etree was compiled without Schematron supp...
https://gitlab.gnome.org/GNOME/libxml2/-/releases/v2.15.0
Support for Schematron is now disabled by default.
Uh oh.... | 08:14:34 |
Grimmauld (any/all) | Worst case you could technically maybe pin libxml2_13 which we do already have, but I'd rather not... I can draft an override flag (something like lxml.override { schema tonsil port = true;} that gets passed through to libxml, would make the overrides more manageable maybe | 08:17:17 |
Grimmauld (any/all) | If its test-only, then skip makes sense. But I am worried there may be more of these hidden in the tree. Testing libxml updates is hard, I'll add this to the list of things I'll test next time | 08:19:06 |
Vladimír Čunát | Maybe notify upstream about schematron deprecation? | 08:29:03 |
K900 | Since I feel like people have asked themselves this | 08:31:09 |