py-xarray-einstats: updated to 0.10.0
0.10.0
Maintenance release mostly. It is a minor version release due to the dependency updates to keep up with SPEC 0.
xkeyboard-config: update to 2.47.
# Layouts
## New
- Added the Slavistic Phonetic Alphabet variant for Polish
# Miscellaneous
## Breaking changes
- Made <ZEHA> behave like <FK24>
On Linux Kernel before v6.17, the scancode for F24 was bound to the otherwise
unused <ZEHA> keycode. v6.17 fixed this. To have a consistent behaviour across
kernel versions, make both <ZEHA> and <FK24> behave the same.
## New
[35 lines not shown]
libksba: updated to 1.6.8
Noteworthy changes in version 1.6.8 (2026-02-23)
* Fix double increment in DN parser while counting hexdigits.
* Fix a memory leak in the BER decoder's error handling.
* Fix an assertion failure in the OCSP code.
* Support SHA256 based CertIDs in OCSP.
* Use nonstring attribute for gcc-15.
* Remove remaining WindowsCE support.
SDL3: updated to 3.4.2
3.4.2
This is a stable bugfix release, with the following changes:
Enabled Vulkan support on OpenBSD
Don't include KHR_portability_enumeration by default on macOS
Added support for GPU ARGB1555 (B5G5R5A1_UNORM) textures with Direct3D11
Fixed D3D12 DSV creation for array/cube/cube-array depth textures
Added SDL_PROP_GPU_DEVICE_CREATE_METAL_ALLOW_MACFAMILY1_BOOLEAN to allow using the GPU API with older Mac hardware
Added SDL_HINT_OPENGL_FORCE_SRGB_FRAMEBUFFER to force specific sRGB behavior for OpenGL and OpenGL ES
Fixed long startup time on Windows when some non-compliant input devices are present
Fixed a crash at startup when the broken EZFRD64.DLL is present
Added support for the Razer Raiju V5 Pro
Fixed a divide by zero when using Nintendo Switch 2 controllers
Fixed hang sending output reports to the NVIDIA SHIELD Controller on macOS
Fixed various controllers showing up twice on macOS
Fixed handling GameCube adapters in PC mode on Linux and macOS
[7 lines not shown]
py-uv py-uv-build: updated to 0.10.5
0.10.5
Enhancements
Add hint when named index is found in a parent config file
Add warning for uv lock --frozen
Attempt to use reflinks by default on Linux
Fallback to hardlinks after reflink failure before copying
Filter pylock.toml wheels by tags and requires-python
Validate wheel filenames are normalized during uv publish
Fix message when exclude-newer invalidates the lock file
Change the missing files log level to debug
Performance
Improve performance of repeated conflicts with an extra
[13 lines not shown]
ansible-core: updated to 2.20.3
v2.20.3
Minor Changes
- ansible-test - Update URL used to download FreeBSD wheels for managed remotes.
- ansible-test - Use the new API endpoint for the Ansible Core CI service.
Bugfixes
- Fix interpreter discovery on delegated ``async`` tasks (https://github.com/ansible/ansible/issues/86491)
- Fix up the Action plugin ``_make_tmp_path`` error to only include the command run rather than the shell's dataclass repr from ``mkdtemp``.
- local connection - Pass correct type to become plugins when checking password (https://github.com/ansible/ansible/issues/86458)
properly mask the "number of arguments" word to avoid invalid output.
i had a system soft-hang with cc1plus waiting for memory, but there
is enough memory free now, but when i tried to "bt/a <cc1plus addr>"
i was getting an extremely large output (several megabytes before i
killed simh).
we fetch the argument count from a 32-bit space in the stack frame,
but it's only the bottom byte that matters, the other bytes should
always be zero for netbsd, as they're used by VMS.
mask the high bytes of this value before consuming it.
also, since we don't expect to see them, simply give up when we find
a "callg" instruction. i did attempt to handle this, but since they
should not be present, and seeing one would indicate that an unexpected
stack write to that bit, handling it just leads to more faults as they
vax_ap pointer does not point to valid memory and triggers crash (ie,
back to db> prompt.)
properly mask the "number of arguments" word to avoid invalid output.
i had a system soft-hang with cc1plus waiting for memory, but there
is enough memory free now, but when i tried to "bt/a <cc1plus addr>"
i was getting an extremely large output (several megabytes before i
killed simh).
we fetch the argument count from a 32-bit space in the stack frame,
but it's only the bottom byte that matters, the other bytes should
always be zero for netbsd, as they're used by VMS.
mask the high bytes of this value before consuming it.
also, since we don't expect to see them, simply give up when we find
a "callg" instruction. i did attempt to handle this, but since they
should not be present, and seeing one would indicate that an unexpected
stack write to that bit, handling it just leads to more faults as they
vax_ap pointer does not point to valid memory and triggers crash (ie,
back to db> prompt.)
