audio/mac: Install patched headers
While the headers in Source/Shared are built against, the copies in
Shared are the ones installed, so patch both.
Fixes: 11b21784e3cc audio/mac: Update to 11.62
MFH: 2025Q4
(cherry picked from commit 7775b61192af1982e534486fd3019531c3dc4bc9)
audio/mac: Update to 11.62
Fix runtime for little endian archs. At least on amd64, _BIG_ENDIAN is
defined somewhere in the toolchain, causing the byte order to be
reversed. [1]
Patch the correct "All.h" and apply DOS2UNIX to all patched files.
https://www.monkeysaudio.com/versionhistory.html
Reported by: <monochrome at twcny.rr.com> via private mail [1]
MFH: 2025Q4
(cherry picked from commit 11b21784e3cc078f3503d936a9966bd1b70c4288)
audio/mac: Install patched headers
While the headers in Source/Shared are built against, the copies in
Shared are the ones installed, so patch both.
Fixes: 11b21784e3cc audio/mac: Update to 11.62
MFH: 2025Q4
audio/mac: Update to 11.62
Fix runtime for little endian archs. At least on amd64, _BIG_ENDIAN is
defined somewhere in the toolchain, causing the byte order to be
reversed. [1]
Patch the correct "All.h" and apply DOS2UNIX to all patched files.
https://www.monkeysaudio.com/versionhistory.html
Reported by: <monochrome at twcny.rr.com> via private mail [1]
MFH: 2025Q4
databases/py-redisvl: Add port: Python client library and CLI for using Redis as a vector database
Redis Vector Library (RedisVL) is the production-ready Python client
for AI applications built on Redis. Lightning-fast vector search meets
enterprise-grade reliability.
Built for Modern AI Workloads:
- RAG Pipelines -> Real-time retrieval with hybrid search capabilities
- AI Agents -> Short term & long term memory and semantic routing for
intent-based decisions
- Recommendation Systems -> Fast retrieval and reranking
WWW: https://github.com/redis/redis-vl-python
mail/py-resend: Add port: Resend Python SDK
Resend is the email API for developers.
The best way to reach humans instead of spam folders. Deliver
transactional and marketing emails at scale.
WWW: https://github.com/resend/resend-python
databases/py-prisma: Add port: Type-safe database access for Python
Prisma Client Python is a next-generation ORM built on top of Prisma
that has been designed from the ground up for ease of use and
correctness.
Prisma is a TypeScript ORM with zero-cost type safety for your
database, although don't worry, Prisma Client Python interfaces with
Prisma using Rust, you don't need Node or TypeScript.
Prisma Client Python can be used in any Python backend
application. This can be a REST API, a GraphQL API or anything else
that needs a database.
WWW: https://github.com/RobertCraigie/prisma-client-py
Note:
Although the upstream repository has been archived, this port is
needed by LLM proxy functions of misc/py-litellm, which is in
preparation.
security/py-google-cloud-kms: Add port: Python client for Google Cloud Key Management Service
Google Cloud Key Management Service: a cloud-hosted key management
service that lets you manage cryptographic keys for your cloud
services the same way you do on-premises. You can generate, use,
rotate, and destroy AES256, RSA 2048, RSA 3072, RSA 4096, EC P256, and
EC P384 cryptographic keys. Cloud KMS is integrated with Cloud IAM and
Cloud Audit Logging so that you can manage permissions on individual
keys and monitor how these are used. Use Cloud KMS to protect secrets
and other sensitive data that you need to store in Google Cloud
Platform.
WWW: https://pypi.org/project/google-cloud-kms/
rb tree: remove strict aliasing violations
Rework internal RB macros to avoid assignments via type punned pointers.
RB uses low order pointer bits to encode information (whether children
are red), and was manipulating those values via (*(__uintptr_t *)&elm),
which leads to strict aliasing warnings.
In the kernel we use -fno-strict-aliasing, but this isn't necessarily
the case in user space. This quiets thousands of -Wstrict-aliasing
warnings in the user space build.
Reported by: GCC -Wstrict-aliasing
Reviewed by: dougm
Discussed with: kib
Differential Revision: https://reviews.freebsd.org/D52939
vmimage.subr: Sort METALOG before running makefs
When creating VM images from pkgbase, the METALOG may not be in order;
in particular, files may be listed before the directories which contain
them. This causes makefs to create directories with 000 permissions.
Interestingly, such VM images boot just fine, since root ignores those
permissions; the first sign of trouble was sshd refusing logins with an
error message which said absolutely nothing about /etc/ having
incorrect permissions or being unable to read files inside it.
Immediately prior to running makefs, sort the METALOG file. While
we're here, uniquify as well; this does not guarantee that we do not
have duplicate paths, but if there are duplicate paths with different
settings something else has gone wrong and we don't really have any
good way of solving the problem anyway.
Approved by: re (cperciva)
Reviewed by: ivy
[7 lines not shown]
vfs offset: fix assertion failure in face of racing ffofset and setfl locking
Both use the same 16 bit var to store their locked and waiters bits,
then this in file_v_unlock:
state = atomic_load_16(flagsp);
if ((state & lock_wait_bit) == 0 &&
atomic_cmpset_rel_16(flagsp, state, state & ~lock_bit))
return;
can fail if for example foffset is being unlocked while setfl is getting
locked.
Afterwards the code assumes there are blocked waiters on foffset.
Approved by: re (cperciva)
Reviewed by: kib, markj
Sponsored by: Rubicon Communications, LLC ("Netgate")
Differential Revision: https://reviews.freebsd.org/D52915
[2 lines not shown]
vmimage.subr: Sort METALOG before running makefs
When creating VM images from pkgbase, the METALOG may not be in order;
in particular, files may be listed before the directories which contain
them. This causes makefs to create directories with 000 permissions.
Interestingly, such VM images boot just fine, since root ignores those
permissions; the first sign of trouble was sshd refusing logins with an
error message which said absolutely nothing about /etc/ having
incorrect permissions or being unable to read files inside it.
Immediately prior to running makefs, sort the METALOG file. While
we're here, uniquify as well; this does not guarantee that we do not
have duplicate paths, but if there are duplicate paths with different
settings something else has gone wrong and we don't really have any
good way of solving the problem anyway.
Reviewed by: ivy
Hint from: imp
[5 lines not shown]
