mu: update to 1.14.4
Packaging updates:
- mu has chosen to remove a few libs from vendored in favor of using
meson's wrap. Therefore, there are some new depends for this.
Upstream updates:
*** mu
- experimental support for the Fish shell
*** mu4e
- New option ~mu4e-view-ignore-links~ to exclude links (by default,
no-reply-links) from ~mu4e-view-go-to-url~ and friends (1.14.4)
- Add some ~defalias~::
~mu4e-contact-matches-p~ => ~mu4e-message-contact-field-matches~,
~mpu4e-contact-matches-me-p~ =>
~mu4e-message-contact-field-matches-me~ and
~mu4e-subject-matches-p~ => ~mu4e-message-subject-matches~
[24 lines not shown]
CLI11: update to 2.7.2
2.7.2:
Changed
- The C++20 named module uses the precompiled implementation and we
lowered its floor from C++23 to C++20. CLI11::Module now works for
both find_package and add_subdirectory, and configure fails with a
clear message if CMake is older than 3.28.
- Removed <iostream>, <codecvt>, <iomanip>, <fstream>, and <locale>
from the declaration headers, so precompiled clients do not parse
them. App::exit() is now three overloads instead of one with stream
default arguments.
- Moved the remaining non-template function bodies out of App.hpp,
Option.hpp, Validators.hpp, TypeTools.hpp, ConfigFwd.hpp, and
FormatterFwd.hpp into the impl/*_inl.hpp files, so they compile
into the library in precompiled mode. Header-only mode is
unchanged.
Fixed
[131 lines not shown]
ruby-sass-embedded: Disable pre-compiled binaries.
As if this package wasn't evil enough already performing fetch and build
during the install stage(!), it also downloads pre-compiled binaries on
certain platforms, causing PLIST failures and increased security hazards.
textproc/agcre: update package to version 20261014
Upstream were very quick to merge the pkgsrc patch, so update to the
latest version, 20261014
agcre: various bug fixes, mainly relating to packaging:
Fix up the main Makefile, bump version number, don't install manual
pages that aren't ours
lima: Update to 2.2.1
Changes:
v2.2.1
Several bug fixes and dependency updates.
v2.2.0
Highlights:
- Experimentally support Windows server 2025 guests
- Experimentally support Windows 11 guests
- Experimentally allow opting out from password-less sudo
v2.1.4
- Cherry-picks from `master` to `release/2.1`
- Only add xorrisofs flag to the xorrisofs command
- fix(qemu): fallback from hvf to tcg on macOS
- nerdctl: update from v2.3.3 to v2.3.4
- templates: update
- templates/freebsd-15: support 9p mounts (#5172)
[25 lines not shown]
py-zensical: update to 0.0.70nb1.
In addition to the changes from below, this includes a post-release
bugfix, which is why it jumps to nb1 immediately.
0.0.70:
Zensical now supports the exclude_docs, draft_docs, and not_in_nav
settings from mkdocs.yml for excluding files, previewing drafts,
and keeping pages out of automatic navigation.
Additionally, the user interface is updated to v0.0.37, improving
search accessibility and reliability, adding draft markers and
discovery links for llms.txt and Markdown, and introducing 17 new
icons, including :simple-zensical:.
emacs*: load local-site-start from site-start.el
Since we now use site-start.el allow it to load a local-site-start.el
for those users who had their own use for it.
curl: update to 8.23.0.
curl and libcurl 8.23.0
This release includes the following changes:
o lib: CURL_GLOBAL_WIN32 -> CURL_GLOBAL_WINSOCK [64]
o SMB: drop support [63]
o tool_cb_wrt: inject the no-clobber number before the extension [21]
o tool_cb_wrt: try up to .9999 when no-clobbering [46]
This release includes the following bugfixes:
o apple-sectrust: check ocsp copy alloc [292]
o apple: shorten versions in `__builtin_available()` calls [251]
o apple: sync hash init calls, add comments [217]
o apple: sync up version guard macro style [263]
o base64: avoid repeated input loads when encoding [114]
o base64: optimize decode lookup table and quantum loop [88]
[277 lines not shown]
www/anubis: Update to 1.28.1
Changelog:
1.28.1:
* Revert systemd isolation change that worked fine in testing but failed in prod.
1.28.0:
This release adds WebAssembly based proof of work checks to Anubis. They are documented in the Proof of Work (WebAssembly) page. This uses Rust code compiled to WebAssembly to run proof of work code. When browsers support SIMD, the WASM will use hardware acceleration.
When clients are configured to disable WebAssembly, Anubis falls back to a pure JavaScript implementation of the WebAssembly-based check logic. As clients that disable WebAssembly usually disable the JavaScript JIT (the thing that makes JavaScript fast), this makes checks slower.
Additionally due to complicated facts and circumstances involving it being complicated to pass the messages from the wasm2js world back to JavaScript, the progress bar will not update while a wasm2js check is running. This is a known issue and will be fixed in a later release.
The difficulty values for the WebAssembly based checks are going to be much greater than the equivalent difficulty values for the JavaScript based checks. Generally these count the number of leading bits that much match instead of the number of leading nibbles that must match. Here's a rough translation table:
fast difficulty argon2id difficulty sha256 difficulty hashx difficulty
4 4 16 15
2 2 8 7
6 6 24 20
[111 lines not shown]
