[NEW PORT] security/py-k5test: Library for setting up self-contained Kerberos 5 environments
Co-authored-by: Michael Osipov <michaelo at FreeBSD.org>
PR: 278820
[Clang] Let isAnyArgInstantiationDependent handle Null template arguments (#174698)
Unused template parameters, though never referenced during substitution,
must remain in the MLTAL to preserve consistent template parameter
indices.
The null type placeholder plays this role, while
isAnyArgInstantiationDependent() doesn't properly handle this case when
checking nested constraints.
There is no release note because this is a regression from concept
parameter mapping.
Fixes https://github.com/llvm/llvm-project/issues/174667
[libc++] Correct `optional<T&>` implementation (#174537)
Resolves #174350
- Several issues were found in the current implementation of
`optional<T&>`
- `value()`, `operator*()`, `and_then()`, `transform()`, `operator->()`
still provided their ref-qualified versions for rvalues and `const&`.
- Using the listed methods on an rvalue `optional<T&>` would cause a
compile failure due to a mismatch in return types.
- On the latter, `operator*`, `operator->` would return `const` for a
`optional<T&>`, which is an incorrect deep const.
- A few constructors were missing (`optional<U>&`), and most
constructors relevant to `optional<T&>` were missing `noexcept`
- Constructors and `emplace` were not correctly constructing a `T&` as
specified in _`convert-ref-init-val`_
- Also corrects the behavior of `value_or` which should return
`remove_cv_t<T>` (in our case `decay_t<_Tp>`)
- Add several test cases to verify behavior, update `value_or` tests
[flang][OpenMP] Prevent `omp.map.info` ops with user-defined mappers from being marked as parial maps
The following test was triggering a runtime crash **on the host before launching the kernel**:
```fortran
program test_omp_target_map_bug_v5
implicit none
type nested_type
real, allocatable :: alloc_field(:)
end type nested_type
type nesting_type
integer :: int_field
type(nested_type) :: derived_field
end type nesting_type
type(nesting_type) :: config
allocate(config%derived_field%alloc_field(1))
[39 lines not shown]
Reapply "[llvm-exegesis] Add AArch64 operand initializers, SetRegTo" (#174729) (#174944)
This reverts commit f68774fd1ad570fef850439ac163b61dc96b98f1. The
original PR broke the sanitizer-aarch64-linux-bootstrap-asan builder:
https://lab.llvm.org/buildbot/#/builders/24/builds/16298
The cause of the failure was exegesis producing inconsistent results
across libc++ implementations when seeded with
'--random-generator-seed=<seed>'. The failing Buildbot does a 2-stage
build, in the 1st stage it builds LLVMs libc++ then builds LLVM with it
in the 2nd stage. The exegesis implementation relies on
uniform_int_distribution which doesn't guarantee consistent results
across implementations.
The tests seeded the RNG because FileCheck can't handle the wrap around
constraint of the register pairs, e.g. { v31.1d, v0.1d }. The test is
updated to no longer rely on '--random-generator-seed'. Unfortunately
the tests aren't particularly good anymore, but not sure what else can
be done for now.
devel/py-dbus: Decouple from pydbus-common and enable testing
These ports were split more than 10 years ago in a1fb7d3e4ebf09080fe48ea40b2cb801a56cf710
to support both Python 2 and Python 3. Later the py3-dbus variant got removed,
so there is no point in having devel/pydbus-common now.
git archeology by: jhale
## [0.37.0] - 2026-01-07
### Release highlights
* A new syntax for referring to hidden and divergent change IDs is available:
`xyz/n` where `n` is a number. For instance, `xyz/0` refers to the latest
version of `xyz`, while `xyz/1` refers to the previous version of `xyz`.
This allows you to perform actions like `jj restore --from xyz/1 --to xyz` to
restore `xyz` to its previous contents, if you made a mistake.
For divergent changes, the numeric suffix will always be shown in the log,
allowing you to disambiguate them in a similar manner.
### Breaking changes
* [String patterns](docs/revsets.md#string-patterns) in revsets, command
arguments, and configuration are now parsed as globs by default. Use
`substring:` or `exact:` prefix as needed.
[115 lines not shown]
release: make sh the default shell
The default shell for root has been changed to sh(1) followup changing
in release images sh(1) the shell for the "freebsd" user.
MFC After: 1 week
Reviewed by: manu, emaste (re)
Approved by: manu, emaste (re)
Differential Revision: https://reviews.freebsd.org/D54602
