Seems like the changes for 1.8.7 were accidentally merged into the v1.8.2 branch, causing distfile breakage, see also: https://github.com/swills/vaultui/commit/b91a8bb9576c53fe5287312a3b48b6f403bc66d8#commitcomment-63640515
Until this get fixed by the maintainer, I'll fix this temporarily by switching upstream to a forked github repo (which will give the same hashes as before, so no worries about the content) under a build fix blanket.
A commit in branch 2022Q1 references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=594795be8a43497d402cbc72e2048d2860c574a0 commit 594795be8a43497d402cbc72e2048d2860c574a0 Author: Michael Gmelin <grembo@FreeBSD.org> AuthorDate: 2022-01-13 18:36:56 +0000 Commit: Michael Gmelin <grembo@FreeBSD.org> CommitDate: 2022-01-13 18:44:29 +0000 security/vault: Fix build Upstream broke v1.8.2 branch by accident, temporary fix by cloning upstream on github, resetting the repo hard, and changing github source. This way hashes in distinfo stay the same (only the filename changes). See also https://github.com/swills/vaultui/commit/b91a8bb9#commitcomment-63640515 PR: 261125 Approved by: build fix blanket (cherry picked from commit 8f5c169cc40eeb6b5b6b1b1720d47220a81dd9b7) security/vault/Makefile | 2 +- security/vault/distinfo | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-)
Thanks for fixing the build. As part of updating to 1.8.7 I have switched back to swills/vaultui.
(In reply to Brad Davis from comment #3) Thanks, that's what I was hoping for :) I think we can leave 1.8.2 in 2022Q1 on my fork until 2022Q2 will "rotate" it out automatically.