BSD Commit Log Search

freetds: update to 1.5.14

maolan: add new package for testing

   Fix incorrect syntax for some shells

   In a world long vanished, the ascii char set did not have the |
   character (0x7c) as a standard member, and could not be relied
   upon existing.   In systems only found today in archaeological digs,
   that was handled by making '^' be the sh symbol for a pipe.

   That meant that the regular expression notation for negating a
   character class ([^stuff]) couldn't be used in shell patterns,
   and so ! was used there instead of the ^.   The ^ did not bother
   use in REs as those almost always need to be quoted when included
   in a shell command anyway - but quoting of shell patterns would
   defeat their use as a pattern, so couldn't be used there.

   In more modern times, this excuse for the difference has long gone,
   ^ isn't the pipe symbol in any shell that is likely to be encountered,
   and so most shells allow either ^ or ! to represent negation of a
   character class - ^ for compat with REs, and ! for compat with old
   scripts.

    [6 lines not shown]

Import wl-clipboard

grim: clean distinfo

slurp: fix depends

Import grim

Import slurp

   pkg-vulnerabilities: CVE-2025-12745 was backported in quickjs-20250913nb1

   py-sbws: use upstream fix instead of pkgsrc workaround

chromium: update to 145.0.7632.159

labwc: update to 0.9.5

   doc: Updated devel/jj-docs to 0.39.0

   jj-docs: update to 0.39.0.

   Match jj.

   doc: Updated devel/jj to 0.39.0

   jj: update to 0.39.0.

   ## [0.39.0] - 2026-03-04

   ### Release highlights

   * `jj arrange` command brings up a TUI where you can reorder and abandon
     revisions. [#1531](https://github.com/jj-vcs/jj/issues/1531)

   * `jj bookmark advance` automatically moves bookmarks forward to a
     target revision (defaults to `@`) using customization points
     `revsets.bookmark-advance-from` and `revsets.bookmark-advance-to`.
     It is heavily inspired by the longstanding community alias `jj tug`.

   ### Breaking changes

   * Dropped support for legacy index files written by jj < 0.33. New index files
     will be created as needed.


    [104 lines not shown]

   doc: Updated net/arti to 2.1.0

   arti: update to 2.1.0.

   # Arti 2.1.0 — 2 March 2026

   Arti 2.1.0 continues work on relay development,
   and introduces a new RPC backend with non-blocking IO
   in the `arti-rpc-client-core` library.

   As usual, there are also various under-the-hood improvements and bug fixes.

   doc: Updated www/palemoon to 34.1.0nb1

   palemoon-gtk3: Reset PKGREVISION.

   palemoon: Update to 34.1.0

   Improves JavaScript and CSS compatibility and includes several
   security fixes.

   reorder so we don't crash.

swayidle: fix typo

Import swayidle

Import swaylock

   Downgrade maybe-uninitialized to a warning for grid.c

   Otherwise aarch64 builds fail with:

   /home/source/ab/netbsd-10/src/external/bsd/tmux/dist/grid.c: In function 'grid_string_cells':
   /home/source/ab/netbsd-10/src/external/bsd/tmux/dist/grid.c:1070:22: error: 'size' may be used uninitialized in this function [-Werror=maybe-uninitialized]
    1070 |  size_t    len, off, size, codelen;
         |                      ^~~~

   but the code always initializes size before first use.

   Updated databases/postgresql-timescaledb

   postgresql-timescaledb: updated to 2.25.2

   2.25.2

   This release contains performance improvements and bug fixes since the 2.25.1
   release and a fix for a security vulnerability. You can check the security
   advisory for more information on the vulnerability and the platforms that are
   affected. We recommend that you upgrade as soon as possible.

   Updated textproc/py-tabulate, devel/py-inline-snapshot

   py-inline-snapshot: updated to 0.32.4

    0.32.4 — 2026-03-01

   Added

   - Added `context_managers` parameter to `Example.run_inline()`, allowing tests to inject context managers (e.g. `unittest.mock.patch`) that are active during `show_report()`.

   Fixed

   - Fixed `UsageError("unmanaged values can not be compared with snapshots")` raised during session teardown when using `-k` to filter tests. This was caused by inline-snapshot trying to update snapshots that were never compared. This is a rare edge case that caused problems when matchers were used, so it has been removed.