Update to nabud-1.4.1:
Upstream changes:
* Added a local copy of strlcpy(3) for platforms that do not include it
(some Linux systems, for example).
* Fixed a nabud crash when a connection has a Baud directive but no
StopBits directive.
* Fixed a nabud crash when a connection has a Channel directive that
does not match any configured channel.
py-pylint: updated to 4.0.4
4.0.4
False Positives Fixed
- Fixed false positive for ``invalid-name`` where module-level constants were incorrectly classified as variables when a class-level attribute with the same name exists.
- Fix a false positive for ``invalid-name`` on an UPPER_CASED name inside an ``if`` branch that assigns an object.
re2c: updated to 4.3.1
4.3.1 (2025-12-01)
- Fixed bugs:
(allow conditions that have no rules except for default rule)
(use unsigned character type in C/C++ examples)
(fix broken end of input rule $ with captures)
Add __HAVE_NEW_PMAP_68K glue:
- mac68k_init(): Use pmap_protect() to write-protect the kernel text
(with a comment explaining why we do this here).
- Add a machine_bootmap[] with entries for IOBase, ROMBase, and VIDBase.
In bootstrap_mac68k(), patch up machine_bootmap[] with run-time computed
values.
pmap_machine_check_bootstrap_allocations() and bootstrap_mac68k() are
independent of the pmap implementation; move them out of pmap_bootstrap.c
and into machdep.c
* Use the LFS_IFDIRTY flag to keep track of whether the Ifile has
ungathered changes during checkpoint. Modify LFS_WRITESEGENTRY and
make a new LFS_WRITEIENTRY macro to help track this. Prevents
an infinite loop in lfs_writeinode, previously caught with a panic.
* Fix a false-positive "negative bytes" panic when writing inodes into
the same segment they were in before, and consolidate the accounting
logic into new function lfs_subtract_inode.
* Ensure that we do not clean any inodes that were unavailable during
the first pass of cleaning, so that we never need to mix cleaning and
non-cleaning blocks (except for the Ifile) when writing.
* Straighten out the logic in lfs_writefile to make it more readable.
* Include IMNT_WANTRDONLY in tests for closing out writes, not just
IMNT_UNMOUNT.
* Keep track of whether the kernel cleaner is active on a file system
[2 lines not shown]
net/unison: Sync unison build targets with pkgsrc options
to avoid e.g. unison's build system trying to build the gui if lablgtk
is installed but not buildlinked.
unison-snapshot: Update to 2.53.8.51
Advance along master, including a merge of code to install a desktop file.
Sync unison build options with package options, to avoid e.g. unison's
build system trying to build the gui if lablgtk is installed but not
buildlinked.
textproc/treemd: update to 0.4.1
[0.4.1] - 2025-12-01
Fixed
Config file color_mode setting ignored - The color_mode setting in config.toml is now properly respected (#5)
Priority order: CLI flags > config file > auto-detection
Set color_mode = "rgb" or color_mode = "256" in config to override auto-detection
color_mode = "auto" (default) uses improved auto-detection
RGB auto-detection fails for truecolor terminals - Improved terminal color detection for Kitty, Alacritty, WezTerm, and other RGB-capable terminals (#5)
Now checks COLORTERM environment variable for truecolor or 24bit (primary standard per termstandard/colors)
Checks TERM for known truecolor terminals (kitty, alacritty, wezterm) and suffixes (-truecolor, -direct)
Checks TERM_PROGRAM for known apps (iTerm, Kitty, VS Code, Hyper, etc.)
Falls back to supports_color crate detection
Technical
Enhanced color detection (src/tui/terminal_compat.rs)
[164 lines not shown]
