Updated wip/ols to 2026-05. Requires Odin 2026-07. Reused the original maintainer's
setup, patched server/build.odin to remove references to Haiku, no longer in the
list of supported OS in Odin-2026-07.
xset: update to 1.2.6.
Alan Coopersmith (6):
Add -help option
Improve man page formatting
man page: fix warnings from `mandoc -T lint` and `groff -rCHECKSTYLE=10`
gitlab CI: drop the ci-fairy check-mr job
meson: Add option to build with meson
xset 1.2.6
Bjarni Ingi Gislason (1):
xset.1: some editorial changes for this man page [Debian bug #1072502]
xrefresh: update to 1.1.1.
Alan Coopersmith (10):
Assume target platforms have strcasecmp now
Use _stricmp() instead of strcasecmp() on Windows
Accept --help & --version as aliases to -help & -version
Improve man page formatting
man page: fix warnings from `mandoc -T lint`
man page: add -delay & -help options
gitlab CI: drop the ci-fairy check-mr job
Strip trailing whitespace from source files
meson: Add option to build with meson
xrefresh 1.1.1
xrdb: update to 1.2.3.
Alan Coopersmith (8):
Accept --help & --version as aliases to -help & -version
Make -help exit with 0 instead of 1
Improve man page formatting
man page: fix warnings from `mandoc -T lint`
gitlab CI: drop the ci-fairy check-mr job
meson: Add option to build with meson
Git rid of -Wstringop-truncation warnings
xrdb 1.2.3
p11-kit: updated to 0.26.4
0.26.4
Build fix
Update translations
0.26.3
server: fixed stack exhaustion via unbounded recursion in RPC attribute parsing by enforcing a recursion depth limit (CVE-2026-13757)
fixed confusing error message when trying to store an existing cert with trust anchor
fixed assert when parsing p11-kit files with value (")
fixed numerous memory management issues
Build and test fixes
libffi: updated to 3.7.1
3.7.1
Fix aarch64 ffi_call memory corruption when passing many large
structs by value.
Fix i386 thiscall/fastcall closure stack cleanup for 64-bit
integer and struct arguments.
Fix aarch64 int128 argument split between x7 and the stack on
Darwin
Fix aarch64 clang-cl link failure for HFA helper functions
Build a generic ffi_call_plan fallback on Windows x86-64.
Add Windows ARM64 (MSVC) build and continuous integration support.
x86: Save and restore all supported extended CPU state on signals.
While here, disable Intel AMX, whose state size (>>8 KiB) exceeds
MINSIGSTKSZ (8 KiB), until we are ready to safely update the ABI for
sigaltstack(2). This isn't a regression: we've never had a release
with Intel AMX support.
Previously, on signal delivery, we would only save and restore at
most what FXSAVE does, which is the x87 and SSE registers that always
exist on amd64.
To save and restore the upper halves of the YMM or ZMM registers
(AVX/AVX2/AVX512), or the AVX512 registers ZMM16..ZMM31, or the
enormous AMX state, we need to do more. And we need to do that even if
the signal handler doesn't use AVX instructions, because an SSE
instruction modifying xmmN (e.g., in a vectorized memcpy) will, as a
side effect, zero the high half of ymmN.
Fortunately, the x86 architecture has an extensible mechanism for
[47 lines not shown]
kqueue(2): Tighten branch in previous change.
If sleepok is true, then kmem_zalloc should never fail, and this
routine is inline with constant arguments at every call site, so
let's let the compiler prune dead branches for the call sites that
can sleep.
PR kern/60436: kqueue(2): random kernel null pointer deref in
EVFILT_PROC NOTE_TRACK
resterm: Update to 0.46.2
v0.46.2
What' New
When the update check finds a newer version, the version section of the status bar shows both your current version and the latest one, joined by a "?" icon. Example: ? v0.46.1 ? v0.46.2
Increased startup latency animation to 1s.
v0.46.1
This release rebuilds how resterm updates itself. Downloads are now verified end to end against checksums served by the GitHub release API, the new binary has to prove it is the right release before it replaces the current one.
Verified self-updates
resterm --update now verifies every download against the sha256 digest the GitHub release API publishes for each asset. There is no separate checksum file to fetch anymore - the expected hash arrives with the release metadata and the downloaded binary must match it exactly.
Verification is mandatory. A missing digest, a size mismatch or a checksum mismatch aborts the update and leaves the current install untouched.
As a final check, the downloaded binary is executed with --version and must report the release it claims to be before it is moved into place.
The new binary is staged next to the current one and swapped in with an atomic rename. On Windows the update now installs in place instead of waiting for a restart: the previous executable stays beside the new one as resterm.exe.old and is cleaned up by the next update once no process is still running it.
Safer installs
install.sh and install.ps1 verify the downloaded binary against the release API digest before installing and refuse to install when the checksum does not match.
[4 lines not shown]
py-tzdata: updated to 2026.3
2026.3
Briefly:
Alberta moved to permanent -06 on 2026-06-18. Morocco moves to permanent +00 on
2026-09-20. More integer overflow bugs have been fixed in zic.
py-discid: updated to 1.4.2
Changes in 1.4.2 (2026-07-10):
* Provide Python wheel on PyPI.
* Removed remaining Python 2 specific code from ``util.py``.
cargo-deny: updated to 0.20.2
0.20.2
Fixed
- fixed snapshot filenames on Windows which caused the release binary publish to fail...again.
0.20.1
Fixed
- fixed snapshot filenames on Windows which caused the release binary publish to fail.
0.20.0
Changed
- refactored the CLI, moving some duplicated options/flags into the root and removing several deprecated options/flags/values. See the PR for a full list of changes.
Added
- resolved 873 by adding a new [`bans.std-replacements`](https://embarkstudios.github.io/cargo-deny/checks/bans/cfg.html#the-std-replacements-field-optional) lint which checks the graph for crates.io sourced crates that have been partially or fully replaced in `std` and/or `core`.
Fixed
- resolved 765 by respecting non-default build script paths in manifests.
- resolved 874 by cleaning up the CLI, deduplicating some options/flags that caused bug in the `list` subcommand.
PR/60362 (gdb can not insert breakpoints on aarch64)
Update aarch64-netbsd-tdep.c to use modern gdb initialisation method and
re-gen libgdb/arch/aarch64/init.c
