misc/usd: Move to graphics/openusd
Rename to match upstream naming and moved to a more appropriate category
PR: 292497
Approved by: yuri (maintainer, timeout 1 month)
py-jupyterlab: updated to 4.5.4
4.5.4
Bugs fixed
Avoid using system clipboard in Notebook widget
Update CodeMirror versions, fixing a few selection issues
Fix debugger variable panel to render value 0 properly
Consider both the content type and pattern match in DocumentRegistry.getFileTypeForModel()
false in saveAs to avoid fetching file body
Maintenance and upkeep improvements
Bump Lumino packages to the 2026.2.5 release, fixing iframe resizing
Documentation improvements
Clarify notebook and cell metadata API changes in JupyterLab 4
[3 lines not shown]
py-pypika: updated to 0.51.1
0.51.1
typefix: Add explicit type annotations to table attribute for mypy compatibility
0.51.0
typefix: update parameter types in aggregate and function classes to use Term
0.50.0
New Features
JQL (Jira Query Language) support - New JiraQuery class for building Jira queries with isempty() and notempty() methods
QUALIFY clause - Filter rows based on window function results
Bitwise OR support - New bitwiseor() method on fields
ClickHouse DISTINCT ON - distinct_on() method for ClickHouse queries
ClickHouse LIMIT BY - limit_by() and limit_offset_by() methods
[44 lines not shown]
stand: compile ia32 EFI loader with -malign-double
The UEFI spec says:
> Structures are aligned on boundaries equal to the largest internal
> datum of the structure and internal data are implicitly padded to
> achieve natural alignment.
By default, structs containing members of type "long long" have 4 byte
alignment on i386. This caused some EFI structures to be subtly wrong.
Fix this by compiling the ia32 EFI loader with -malign-double, which
bumps the alignment up to 8 if such members are present.
MFC after: 3 days
py-test-httpserver: updated to 1.1.5
1.1.5
New Features
- Add ``bake()`` method to ``HTTPServer`` for creating pre-configured
request expectation proxies (``BakedHTTPServer``). This allows sharing
common keyword arguments (e.g. ``method``, ``headers``) across multiple
``expect_request()`` calls with last-wins merging semantics.
py-ipykernel: updated to 7.2.0
7.2.0
New features added
- Added kernel_protocol_version to kernelspec
- Replaced PUB socket with XPUB socket
Enhancements made
- Made IOPubThread constructor backward compatible
- Advertizes kernel protocol 5.5
- Upgrade to jupyter_client 8.8.0
- Implement kernel-side callstack filtering for internal frames
Bugs fixed
- add close event for wx timer app in loop_wx
[9 lines not shown]
PR/60002: Enji Cooper:
mq_open in FreeBSD and NetBSD both state that the path provided to the
target mqueue should (in the POSIX parlance of "should") start with a /.
In FreeBSD this proved to be more of an issue than NetBSD (especially
when `kyua debug` was involved). Instead of relying on a temp directory
which might exist outside the kyua sandbox, make the mqueue path
absolute to the prefix `/t_mqueue` (for consistency with the test), and
add the test PID to the path to avoid potential collisions between
back-to-back / concurrent test runs.
While here, explicitly cast the checked return value to `mqd_t`: this is
needed because some platforms--including FreeBSD--might define `mqd_t` as
an unsigned type instead of a signed type. Casting it to `mqd_t` helps
quell a valid compiler warning in that case.
graphics/podofo: fix build with libc++ >= 20
With libc++ 20 or higher graphics/podofo fails to build, with errors
similar to:
/wrkdirs/usr/ports/graphics/podofo/work/podofo-0.10.4/src/podofo/main/PdfColor.cpp:686:13: error: call to 'from_chars' is ambiguous
686 | if (std::from_chars(name.data() + 1, name.data() + name.size(), grayVal, chars_format::fixed).ec != std::errc())
| ^~~~~~~~~~~~~~~
/usr/include/c++/v1/__charconv/from_chars_floating_point.h:63:1: note: candidate function
63 | from_chars(const char* __first, const char* __last, double& __value, chars_format __fmt = chars_format::general) {
| ^
/wrkdirs/usr/ports/graphics/podofo/work/podofo-0.10.4/src/podofo/private/charconv_compat.h:34:30: note: candidate function
34 | inline from_chars_result from_chars(const char* first, const char* last,
| ^
This is because libc++ 20 started offering std::from_chars() for
floating point values, and pododo does not check for this. Correct the
WANT_FROM_CHARS check to correctly check for libc++ 20 or higher.
[5 lines not shown]
graphics/podofo: fix build with libc++ >= 20
With libc++ 20 or higher graphics/podofo fails to build, with errors
similar to:
/wrkdirs/usr/ports/graphics/podofo/work/podofo-0.10.4/src/podofo/main/PdfColor.cpp:686:13: error: call to 'from_chars' is ambiguous
686 | if (std::from_chars(name.data() + 1, name.data() + name.size(), grayVal, chars_format::fixed).ec != std::errc())
| ^~~~~~~~~~~~~~~
/usr/include/c++/v1/__charconv/from_chars_floating_point.h:63:1: note: candidate function
63 | from_chars(const char* __first, const char* __last, double& __value, chars_format __fmt = chars_format::general) {
| ^
/wrkdirs/usr/ports/graphics/podofo/work/podofo-0.10.4/src/podofo/private/charconv_compat.h:34:30: note: candidate function
34 | inline from_chars_result from_chars(const char* first, const char* last,
| ^
This is because libc++ 20 started offering std::from_chars() for
floating point values, and pododo does not check for this. Correct the
WANT_FROM_CHARS check to correctly check for libc++ 20 or higher.
[3 lines not shown]
devel/libddwaf: fix build with clang 21
With clang 21 devel/libddwaf fails to build, with errors similar to:
In file included from /wrkdirs/usr/ports/devel/libddwaf/work/libddwaf-1.30.1/src/vendor/fmt/format.cc:8:
/wrkdirs/usr/ports/devel/libddwaf/work/libddwaf-1.30.1/src/vendor/fmt/format-inl.h:61:19: error: call to consteval function 'ddwaf::fmt::basic_format_string<char, ddwaf::fmt::basic_string_view<char> &, const char (&)[3]>::basic_format_string<FMT_COMPILE_STRING, 0>' is not a constant expression
61 | format_to(it, FMT_STRING("{}{}"), message, SEP);
| ^
/wrkdirs/usr/ports/devel/libddwaf/work/libddwaf-1.30.1/src/vendor/fmt/format.h:1905:23: note: expanded from macro 'FMT_STRING'
1905 | #define FMT_STRING(s) FMT_STRING_IMPL(s, fmt::detail::compile_string, )
| ^
/wrkdirs/usr/ports/devel/libddwaf/work/libddwaf-1.30.1/src/vendor/fmt/format.h:1882:3: note: expanded from macro 'FMT_STRING_IMPL'
1882 | [] { \
| ^
/wrkdirs/usr/ports/devel/libddwaf/work/libddwaf-1.30.1/src/vendor/fmt/core.h:688:54: note: subexpression not valid in a constant expression
688 | format_str_.remove_prefix(detail::to_unsigned(it - begin()));
| ~~~^~~~~~~~~
/wrkdirs/usr/ports/devel/libddwaf/work/libddwaf-1.30.1/src/vendor/fmt/core.h:2639:5: note: in call to 'this->context_.advance_to(&"{}{}"[1])'
2639 | context_.advance_to(begin);
[64 lines not shown]
devel/libddwaf: fix build with clang 21
With clang 21 devel/libddwaf fails to build, with errors similar to:
In file included from /wrkdirs/usr/ports/devel/libddwaf/work/libddwaf-1.30.1/src/vendor/fmt/format.cc:8:
/wrkdirs/usr/ports/devel/libddwaf/work/libddwaf-1.30.1/src/vendor/fmt/format-inl.h:61:19: error: call to consteval function 'ddwaf::fmt::basic_format_string<char, ddwaf::fmt::basic_string_view<char> &, const char (&)[3]>::basic_format_string<FMT_COMPILE_STRING, 0>' is not a constant expression
61 | format_to(it, FMT_STRING("{}{}"), message, SEP);
| ^
/wrkdirs/usr/ports/devel/libddwaf/work/libddwaf-1.30.1/src/vendor/fmt/format.h:1905:23: note: expanded from macro 'FMT_STRING'
1905 | #define FMT_STRING(s) FMT_STRING_IMPL(s, fmt::detail::compile_string, )
| ^
/wrkdirs/usr/ports/devel/libddwaf/work/libddwaf-1.30.1/src/vendor/fmt/format.h:1882:3: note: expanded from macro 'FMT_STRING_IMPL'
1882 | [] { \
| ^
/wrkdirs/usr/ports/devel/libddwaf/work/libddwaf-1.30.1/src/vendor/fmt/core.h:688:54: note: subexpression not valid in a constant expression
688 | format_str_.remove_prefix(detail::to_unsigned(it - begin()));
| ~~~^~~~~~~~~
/wrkdirs/usr/ports/devel/libddwaf/work/libddwaf-1.30.1/src/vendor/fmt/core.h:2639:5: note: in call to 'this->context_.advance_to(&"{}{}"[1])'
2639 | context_.advance_to(begin);
[62 lines not shown]
