www/webkit-gtk41: Document experiments; say no to ninja
This commit:
- drops the previous setting to force sqlite3 library path
- sets CMAKE_GENERATORS_INCOMPATIBLE to ninja
When building with ninja (not default, but many do), the NEEDED entry
in the webkit library is broken, differently depending on if the
sqlite3 library path is forced or not. The commit adds excruciating
comments documenting this on NetBSD 10 amd64.
(It would be great if someone found and fixed the bug, but for now,
just roll with "ninja building this package doesn't work".)
Note that when not building with PKG_DEVELOPER, the resulting
problems, which might or might not be fatal at runtime, are not
detected.
libuuid, libblkid, mcookie: update to 2.42.3.
util-linux 2.41 Release Notes
=============================
libuuid:
- Now supports RFC9562 UUIDs.
libblkid:
- Made many changes to improve detection, including exfat, GPT, LUKS2, bitlocker, etc.
util-linux 2.42 Release Notes
=============================
libblkid:
- dos validate EBR data and links within extended partition (by Karel Zak)
- fix stale comment in version.c (by Karel Zak)
- add LIBBLKID_VERSION to blkid.h, remove redundant config.h versions (by Karel Zak)
- add debug message for private DM device skip (by Karel Zak)
[86 lines not shown]
tailscale: update to 1.102.4
- Resolved an issue that could cause a loss in connectivity when a
netmap update occurs near the time of reauthentication.
- Resolved an issue that could prevent exit nodes from appearing when
using a custom coordination server on Darwin.
Updated sysutils/xenkernel420 to 20260911
Updated sysutils/xentools420 to 20260911
Updated sysutils/xenstoretools to 20260911
Updated sysutils/xenkernel418 to 20260911
Updated sysutils/xentools418 to 20260911
dpkg: updated to 1.23.11
dpkg (1.23.11) unstable; urgency=medium
* dpkg: Improve maintscript abort-* execution diagnostics.
* dpkg-shlibdeps: Do not validate existence of -l option argument.
* Code internals:
- dpkg: Use a proper conditional instead of a ternary operator for
f_triggers.
- dpkg: Refactor tarobject_describe_type() into a new function.
- dpkg-split: Refactor depot handling functions out of do_auto().
strawberry: updated to 1.2.30
1.2.30
Bugfixes
Fixed an out-of-bounds memory access in HMAC signing when using keys longer than the hash's block size, affecting request signing for Discogs and Musixmatch
Fixed the build failing when the tag fetcher (AcoustID) is disabled
Changed API credentials for Spotify for production use
py-matrix-nio: updated to 0.26.0
0.26.0
Breaking Changes
* Replace libolm/python-olm with vodozemac for end-to-end encryption
The e2e extra now depends on vodozemac instead of python-olm, and libolm is no longer required as a system dependency.
Existing encryption stores are migrated automatically on load. Stores created with a libolm pickle version older than 4 (roughly, pre-December 2021) can only be migrated if the optional python-olm >= 3.2.7 package is installed at upgrade time; without it, those pickles cannot be read.
hmac-sha256 is no longer offered as a SAS message authentication code; only hkdf-hmac-sha256 is supported.
Account.remove_one_time_keys() has been removed, as it is no longer supported by the underlying library.
* Drop support for end-of-life python3.8 and python3.9; the minimum supported version is now python3.10
Features
* Add unread_thread_notifications to SyncResponse
Bug Fixes
[2 lines not shown]
py-vodozemac: added version 0.10.0
Python bindings for vodozemac.
vodozemac is a pure Rust implementation of the Olm and Megolm cryptographic
ratchets, offering a high-level API for straightforward creation of secure
communication channels using these ratchets.
py-wrapt: updated to 2.4.1
2.4.1
Bugs Fixed
The C extension implementation of PartialCallableObjectProxy did not expose the bound positional and keyword arguments supplied when the proxy was created, whereas the pure Python implementation makes them available as the _self_args and _self_kwargs attributes. The C extension implementation now provides read only _self_args and _self_kwargs attributes so that both implementations behave the same.
inspect.signature() applied to a PartialCallableObjectProxy reported the full signature of the wrapped callable, including the parameters that the bound positional and keyword arguments already supply, whereas for functools.partial those parameters are removed. The proxy did not define __signature__, so inspect followed __wrapped__ back to the callable and reported its signature unchanged. The proxy now provides __signature__ on instances, in both the pure Python and C extension implementations, giving the same result as for an equivalent functools.partial, including a ValueError when more positional arguments are bound than the callable accepts.
This also affected wrapper functions used with FunctionWrapper and @wrapt.decorator. When a wrapped method is called via its class with the instance passed explicitly, the wrapper function receives a PartialCallableObjectProxy with the instance bound, and args without the instance. A wrapper which bound args and kwargs against inspect.signature(wrapped) would fail for such calls with a TypeError about a missing argument, while working for calls made via the instance. The reported signature now omits the bound instance so the binding succeeds.
The signature of a partial whose wrapped callable is itself an already bound method is still reported incorrectly, for reasons outside of the control of wrapt. See the “Known Issues” documentation for details.
The C extension intercepts the __module__ and __doc__ attributes by name in its attribute get and set slots so that they are forwarded to the wrapped object. The name was compared by identity against an interned string, which relied on the attribute name having been interned. Names originating from Python source code always are, but a name constructed at runtime, for example by string concatenation or by decoding, is not, and for such a name the interception was skipped. Getting the attribute then returned the value captured when the proxy was created rather than the current value on the wrapped object, and setting it stored the value on the proxy rather than the wrapped object. The comparison now falls back to comparing by value when the identity check fails, guarded by a length check so that the cost for non matching names is unchanged.
