databases/jrrd: belatedly bump portrevision for deprecation
Extend the expiration_date with a month to give (unexpected) users
some more time to give feedback.
Approved-by: no maintainer
[LifetimeSafety] Reorganize diagnostic groups and remove confidence-based warnings (#179309)
Reorganized lifetime safety diagnostic groups to be more granular and
renamed diagnostic messages for better clarity.
- **Diagnostic Group Restructuring**: Split lifetime safety warnings
into more specific categories:
- `lifetime-safety-use-after-scope` and
`lifetime-safety-use-after-scope-moved` for scope-related issues
- `lifetime-safety-return-stack-addr` and
`lifetime-safety-return-stack-addr-moved` for return address issues
- `lifetime-safety-dangling-field` and
`lifetime-safety-dangling-field-moved` for field reference issues
- Added new umbrella groups `lifetime-safety-validations` and
`lifetime-safety-all`
- **Diagnostic Message Updates**: Renamed warning diagnostics from
generic "loan expires" terminology to more specific messages like "use
after scope" and "return stack addr"
- **Code Cleanup**: Removed `Confidence` logic (based on possible vs
[22 lines not shown]
[OpenMP][OMPIRBuilder] Support parallel in Generic kernels
This patch introduces codegen logic to produce a wrapper function argument for
the `__kmpc_parallel_51` DeviceRTL function needed to handle arguments passed
using device shared memory in Generic mode.
[analyzer] New checker: optin.core.UnconditionalVAArg (#175602)
Add a new optin checker which reports variadic functions that
unconditionally use `va_arg()`. It would be undefined behavior to call
such functions without passing any variadic arguments, so the SEI-CERT
rule EXP47-C says that this pattern should be avoided.
As this part of this SEI-CERT rule focuses on a very narrow area, I
aimed to write a simple and stable checker that can report basic "clear"
occurrences of this fault. It would be possible to cover some additional
corner cases, but it isn't worth the effort.
sysutils/podman: Revert "Allow setting ownership on auto-created socket"
This works functionally, but is being managed by the incorrect daemon.
Podman alone simply ensures auto-start of containers; podman_service
provides the API. This will be corrected in an upcoming commit.
This reverts commit 2c53428ae117108d41eb4e19935ed98b478f4f7f.
py-requests: relax chardet version requirements.
requests can use chardet if available (though is not a forced dependency)
and, if installed, it checks the version number. relax this check to allow
updating chardet. from upstream.
py-requests: relax chardet version requirements.
requests can use chardet if available (though is not a forced dependency)
and, if installed, it checks the version number. relax this check to allow
updating chardet. from upstream.
x11/mrxvt: Mark DEPRECATED
- Upstream unmaintained
- Known vulnerabilities [1]
- Set EXPIRATION_DATE 2026-03-31
1. https://nvd.nist.gov/vuln/detail/CVE-2021-33477
If someone needs this port feel free to undeprecate and takeover
maintainership.
sysutils/tmate: Mark DEPRECATED
- Upstreaam unmaintained
- WWW unavailable
- Set EXPIRATION_DATE 2026-03-31
If someone needs this port feel free to undeprecate and takeover
maintainership.
sysutils/tmate-ssh-server: Mark DEPRECATED
- Upstreaam unmaintained
- WWW unavailable
- Set EXPIRATION_DATE 2026-03-30
If someone needs this port feel free to undeprecate and takeover
maintainership.
