kk_KZ.PT154 locale: Add missing toupper/tolower mappings.
This was missing a tolower mapping (MAPLOWER) from the lower case
(ASCII) letters into themselves (which is required to work), and worse
was also missing a toupper mapping (MAPUPPER) from the lower case (ASCII)
letters into their upper case equivalents.
Whether the actual (non ASCII) letter upper/lower mappings are all
correct, I am not sure, but I very much doubt it.
Detected and reported by RVP@ in:
https://mail-index.netbsd.org/tech-userlevel/2026/08/15/msg015003.html
bsd.own.mk: Respect USE_FORT even if defined after bsd.own.mk.
Using (a chain of logic that boils down to)
.if ${USE_FORT:Uno} != "no"
CPPFLAGS+= -D_FORTIFY_SOURCE=2
.endif
expands USE_FORT eagerly, so if USE_FORT was not already defined before
including <bsd.own.mk>, it's too late after.
Using (a chain of logic that boils down to)
CPPFLAGS+= ${${USE_FORT:Uno} != "no":?-D_FORTIFY_SOURCE=2:}
expands USE_FORT lazily, so it's only when CPPFLAGS itself is expanded
-- usually in a recipe, after all variable assignments, prerequisite
lists, and .directives have been processed -- that USE_FORT is
expanded.
[9 lines not shown]
ssp.h: Stop creating references to useless __ssp_protected_* symbols.
The ssp wrappers are useful _only_ when they are actually used for
inline function call expansion; if the function is used for anything
else like a function pointer, only the underlying library symbol
should be used.
To pacify linker complaints about spurious references to
__ssp_protected_getcwd/read/readlink, we added equally spurious
definitions of those symbols to libc without understanding why; it
turns out it only happened because the ssp wrappers declared, e.g.:
extern inline read(...) __RENAME(__ssp_protected_read);
extern inline read(...) { <ssp check>; return __ssp_real_read(...); }
The declaration with __RENAME caused the compiler to generate
references, required by the linker to be resolved, to the symbol
`__ssp_protected_read' when compiling code that takes the address of
the function read() to pass around a function pointer. Instead, the
[15 lines not shown]
Add and enable editors/eh, version 1.9.0, to the packages collection
A minimalist version of vi(1). It is an example of the "Buffer Gap"
method outlined in the The Craft Of Text Editing used by many Emacs
style editors.
Create or read a text file to edit. Text files consists of lines of
printable UTF-8 text, tabs, or newline characters. A physical line
can be of arbitrary length and is delimited by either a newline or the
end of file. Tab stops are every eight columns. The behaviour of
non-printable characters may vary depending on the implementation of
the Curses library, stty(1) settings, or terminal emulator.
eh was the winner of IOCCC28, catalogued as 2024/howe
lua-language-server: update to 3.19.1.
Un-BROKENs this package, patches were merged.
Over two years of development.
Provided by Sunil Nimmagadda in PR 60857.
py-uv: update to 0.12.23.
0.12.23
Python
Add CPython 3.15.0rc3 (#22164)
Preview features
Sync from uv.lock without a workspace manifest using uv sync --frozen with frozen-lockfile (#22018)
Export from uv.lock without a workspace manifest using uv export --frozen with frozen-lockfile (#22007)
Inspect dependency trees from uv.lock without a workspace manifest using uv tree --frozen with frozen-lockfile (#22016)
Inspect workspace metadata and optionally sync its environment from uv.lock without a workspace manifest using uv workspace metadata --frozen with frozen-lockfile (#22017, #22018)
Bug fixes
Reject alternate sources for workspace members across conflicting dependency selections, avoiding lockfiles that cannot be installed (#22153)
Allow x86-64 Python interpreters running under emulation on Windows ARM64 to install compatible win_amd64 wheels instead of building from source (#22099)
[40 lines not shown]
