Fix builds - limit new user.stuff in sysctl to real libc
Keep the user.ostype (etc) new sysctls for the real libc (and
suitable facsimilies) - other places that "borrow" syctl.c for
their own purposes can survive without, if any of those want
to include these mib vars in their version, all that is required
is to add the appropriate Makefile glue to create the header file
in the appropriate place, and add -Ipath to the sysctl.o build, and
the new magic -D to enable it.
update transmission (and -gtk, and -qt, and -common) to 4.1.3
Fixed a CORS bug that leaked the anti-CSRF nonce. (#8938)
Fixed a use-after-free bug in peer code. (#8921)
Fixed build error when compiling with fmt 12.2.0. (#8942)
Fixed a 4.1.2 build error in tests. (#8881)
Add new user.* nodes to sysctl
This adds the nodes (and documentation for them):
user.ostype = NetBSD
user.osrevision = 1199000600
user.osrelease = 11.99.6
user.built = 2026-07-10 02:46:18 UTC
to the sysctl mib (the values shown there just what happened for a test build).
The first three are more or less identical to the kern.* mib variables of the
same names - the difference is that these reflect userland, or at least, libc
so do not alter just because a new updated kernel is booted without updating
the rest of the system. The fourth gives either the date when libc was
built (as shown) or if the value contains a trailing "!" (after a space
after UTC) the value is the MKREPERO_TIMESTAMP for the build (keep building
with the same value and the date/time there won't alter). The date/time
are always in UTC.
[11 lines not shown]
Adding src/lib/libc/gen/grab-version.sh
A simple script that gets current system version information and
builds a header file containing it. To be used in a following commit.
bup: Rename -git to -snapshot
My opinion is that the point is not that bup is developed in git but
that the package is a snapshot of development rather than a release.
That's my story and I'm sticking with it at least all day today! But
seriously, it seems like a good plan in general.
libcares: updated to 1.34.8
c-ares version 1.34.8 - July 7 2026
This is a bugfix release.
Bugfixes:
* Revert "Mark parameters in callbacks as const" which shipped in 1.34.7.
Changing the parameter types of the `ares_callback`, `ares_host_callback`,
and `ares_nameinfo_callback` function pointer typedefs was an unintended
API break: existing applications with the historical non-const callback
signatures no longer compiled, particularly in C++ where function pointer
types must match exactly. The read-only nature of the callback parameters
is now documented instead.