mail/maildrop: Fix INOTIFY option
- FreeBSD 14.5 and up include inotify implementation in libc, so update checks to not depend on the ports implementation ion this case
- When using the ports provided libinotify link using the dynamic library
- Also add one file that needs patching for a successful build
While here, pet portclippy/portfmt.
Reported by: Ewout1 (Excite/BlueTie) <ewout1 at bluetiehome.com> (via mailing list)
MFH: 2026Q3
mail/courier-imap: Update version check for INOTIFY option
FreeBSD 14.5 includes the inotify implementation in libc. Update
the version check to avoid linkingg to the ports provided library
in this case.
MFH: 2026Q3
[Mips] Fix O32 lowering on 64-bit CPUs (#224937)
Use 32-bit GPR lowering for O32 while preserving the selected ISA and
FPR mode. Handle FP64 transfers through the stack when high-half moves
are unavailable.
[AMDGPU] Remove dead function and method declarations (NFC) (#224889)
createLowerWWMCopiesPass:
Added on July 28, 2023 in commit
4d42e8b5d1fa87e49768d100dd1bc53515391e89 without a definition or any
callers.
createAMDGPUReserveWWMRegsPass:
Added on September 30, 2024 in commit
ac0f64f06d67a93817ccd9a3c529ad40920115c9 without a definition or any
callers.
createAMDGPUStructurizeCFGPass:
The definition and callers were removed on June 19, 2013 in commit
d46fce11412636ec9cca038e1f2b1addf1690f00.
AMDGPUTargetLowering::LowerSTORE:
The definition was split into R600TargetLowering::LowerSTORE and
SITargetLowering::LowerSTORE on February 11, 2016 in commit
[55 lines not shown]
Validate VM and container UUIDs the way libvirt does
## Problem
`UUIDv4String` did neither thing its name implies. `uuid.UUID(value, version=4)` overwrites the version and variant bits on a throwaway object rather than asserting them, so nothing was ever checked; and the validator returned the caller's original string, so every spelling of a UUID was stored verbatim. Two things went wrong as a result.
The stored string is the libvirt identity — it is written to both `<name>` and `<uuid>` of the domain XML, and domains are looked up by name. Because the create-time uniqueness check was a datastore filter, i.e. SQL `=` against a BINARY-collated column, two rows spelling one UUID differently both got in. Domains are only defined at start, so nothing went wrong until the second one was started, at which point libvirt refused it while quoting the first row's uuid. `uuid` is immutable after creation, so that row cannot be repaired.
Separately, Python and libvirt disagree about what a UUID even looks like. `uuid.UUID()` strips braces and a `urn:uuid:` prefix; libvirt's parser takes 32 hexadecimal digits with hyphens ignored and nothing else. A VM created with either of those spellings was accepted and then could never be defined at all.
## Solution
- **Accept libvirt's grammar, store libvirt's form.** `LibvirtUUID` replaces `UUIDv4String`: 32 hexadecimal digits, hyphens ignorable, stored as the canonical lowercase form. The braced and `urn:uuid:` spellings are now rejected at create rather than turning into a VM that cannot start. Normalising also means a caller-supplied uuid ends up in the same shape auto-generated ones have always had, which matters because the value is a path component for the pid file and the container runtime tree.
- **Version 4 is deliberately not enforced, and a test says so.** The field exists so an operator can preserve a guest's SMBIOS identity when importing from elsewhere, and real UUIDs from VMware, Hyper-V, Proxmox, EC2 and GCE are mostly not v4 — the version nibble is not even stable, since SMBIOS stores the first fields little-endian and the same identifier reads as v1 or v4 depending which way it was rendered. Enforcing it would reject most of what that workflow needs to carry over.
- **Strict on create, plain `str` on the entry.** The entry models are what `query` validates stored rows against, and a row that fails there is dropped from the result rather than reported. They also feed the update write-back, so a normalising validator on the entry would rewrite the uuid on every unrelated update and desync us from a defined domain. This restores the split the older API versions had before the type was shared.
- **Compare uuids by value.** New `same_uuid()` used by both `validate()` methods, falling back to string equality for stored values that are not UUIDs at all, which is reachable through the column's empty-string default and through an uploaded configuration database.
Round out zfs.resource with list, update and the dataset parity methods
## Problem
`zfs.resource` is replacing `pool.dataset`, but it had no way to change a property, its listing method was called `query` while taking a single object rather than the `(filters, options)` that name implies everywhere else, and the choices methods, the zvol blocksize recommendation and the processes family still lived only under `pool.dataset`, so retiring that namespace would have taken those capabilities with it.
## Solution
**`query` becomes `list`.** The behaviour is unchanged - a single object describing what to walk, a flat result unless `nest_results` is set - but the name no longer promises a filterable query it never was. Its primitive is `list_impl`, so the private entry point reads as the method it serves. This is a hard rename with no compatibility shim, so 25.10.x and 26.0 clients lose `zfs.resource.query`; that needs a release note.
**`update` is new.** It takes `{path, properties, user_properties, inherit}` and returns the updated entry, rather than splitting into the `set` and `inherit` that `zfs(8)` uses. A dataset edit is one save, the underlying handle already performs the property set, the user-property set and the per-property inherit in a single pass, and splitting the API would only export sequencing and partial rollback to every caller. Its property vocabulary subclasses the create model so the public/private split is inherited rather than restated, minus what ZFS cannot change after creation. It is the one public method whose role the decorator does not force, so an integration test holds `ZFS_RESOURCE_WRITE` to granting it and `ZFS_RESOURCE_READ` to being refused.
**The write primitive lives on `zfs.resource`.** `update_impl` takes untyped keyword arguments, since internal callers legitimately write property names outside the public vocabulary, and like `create_impl` and `destroy_impl` it refuses snapshot paths and, unless the caller passes `bypass`, protected paths - a private method is still reachable over the wire, and every system dataset, apps and pool-import writer now funnels through this one call. `pool.dataset.update_impl` is a shim that unpacks its existing argument dict onto the primitive with `bypass` set, since those writers reach it that way; the dict stays intact as the HA wire format it is and its callers are untouched. `zfs.tier` calls the primitive directly through a typed call, also with `bypass`, because it is the only way to re-tier an internal dataset once tiering owns `special_small_blocks`, and moves onto the `ZFS_RESOURCE_*` roles that match its namespace - a custom privilege built on `DATASET_*` alone therefore loses `zfs.tier`, which also needs a release note. `pool.dataset.update` keeps its own policy layer and is not shimmed onto the new method; dedup licensing, the acltype-versus-SMB-share block and the LUN resync side effects belong above the raw ZFS layer, not on it.
**`rename` and `promote` become public**, typed and single-object, held by `ZFS_RESOURCE_WRITE`, with the private entry points renamed `rename_impl` and `promote_impl`. `rename` requires `force` as the same acknowledgement `pool.dataset.rename` requires and drops `recursive`, which a dataset rename can never be; the message for that moved to the `pool.dataset.rename` shim so the caller-visible error is unchanged. `pool.snapshot.rename` is re-pointed at the snapshot implementation, which is where snapshot renames actually live - it has been dead since the rename guard landed.
**The read-parity methods move** to `zfs.resource` behind one-line `pool.dataset` shims that keep their existing models and roles, with the pure parts split into modules that need no service or filesystem access.
**Fixes carried along.** Normalising sources no longer dereferences a null `properties`; the overlapping-path check now runs whenever the walk descends rather than only when `get_children` is set, and names the option that actually triggered it; `max_depth` is bounded below at zero; and nesting no longer raises when a parent's `children` is absent because the walk never descended into it.
