sync from OpenBSD CVS upstream since jpouellet vanished circa 2018.

[artkiver]

Basically re-ran make fetch locally against OpenBSD CVS December 12th, 2024.

Nothing too special, really.

[artkiver]

I didn't actually intend to close this PR, but I guess because I renamed that branch when I set it as default, GitHub in its "infinite" wisdom decided it was deleted and auto-closed the Pull Request? Way to completely not actually track history, which is sort of the fundamental property of a (D)VCS in theory?

Kvetching about GitHub/git aside, I submitted a Pull Request to update signify in MacPorts here:

macports/macports-ports#27046

Which, is basically similar to what this Pull Request was related too. Not much changed, I more or less tweaked the Makefile slightly to point to an OpenBSD anoncvs mirror that wasn't timing out, ran

make fetch

And voilà! Fresher signify source from upstream as of December 12th, 2024!

I really didn't do much else.

Well, OK, if you want to be exhaustive here's what else: making a tagged "release" for 1.5 in my forked branch (also renamed to signify-macOS because Apple renamed OS X in the intervening years) for the edification of MacPorts versioning even though signify isn't versioned upstream because signify has no -portable branch and is part of OpenBSD base, unlike OpenSSH or OpenSMTPD or GameOfTrees or other OpenBSD related projects that tend to get reused a lot of other places and do get versioned releases.

As an aside: I don't think repology.org knows how to deal with the discrepancies between the other "versions" of signify it tracks and MacPorts, but on the upshot, I guess that's how I noticed the discrepancy in the first place and what started this whole rabbit warren exploration.

https://repology.org/project/signify-openbsd/versions

Confusingly, Homebrew (which despite being a far inferior alternative to /usr/ports for macOS as contrasted with MacPorts [which was co-founded by jkh, who also co-founded FreeBSD and actually worked at Apple for over a dozen years FWIW]) seems to use the same reference, and thus is also presumably years behind upstream and is kind of off on its own in repology:

https://repology.org/project/signify-osx/versions

But I sure as it.sh am not going to do anything to ever encourage anyone to use Homebrew ever, because it has analytics on by default and uses a curl | install.sh paradigm which is a security disaster unto its own even if it weren't already a walking talking privacy violation.