I submitted a Pull Request to update MacPorts' signify to 1.63 here:

https://github.com/macports/macports-ports/pull/31754

1 of 3 GitHub Continuous Integration checks passed (the other two are queued, but hopefully will complete without issues).

Not really much new here, more just syncing with upstream, which tagged a new release version for 7.9-beta.

tbh, I think this signify fork can probably ditch a lot of the OpenBSD keys? MacPorts (which also uses signify, from an older fork) does the same thing too. I looked into cleaning up that code a little bit to sync MacPorts' built-in signify, with this, but didn't get very far with it last time I gave it a go (there are some functions OpenBSD has, which older versions of OS X don't and someone else already did the heavy lifting for MacPorts' built-in signify a while ago and re-creating their work was more than I was able to bite off and chew on a Friday night the last time I went looking).

Anyway, assuming the other CI checks pass, it's up to someone else with commit access to merge it.

#signify #MacPorts #CryptographicSignatures #OpenSource
Welp, one of the GitHub Continuous Integration checks failed with:

"Installing MacPorts
Fetching base failed: 0
Extracting...
tar: Error opening archive: Failed to open 'MacPorts-2.12.4-25.tar.bz2'
Error: Process completed with exit code 1.
"

AMAZING! (sarcasm)

GitHub finds new ways to shit the bed!

Anyway, that's above my "pay" grade (no one is paying me for this BS, and AFAIK, no one is paying any of the other MacPorts' maintainers either. Regardless, I blissfully do not have access to fix that issue, or I would probably be tempted to waste more time digging more deeply. One of those moments where I am grateful I drew a line in the sand to not take on more responsibilities, because otherwise I would be staying up even later than I already am, when I have work in a few hours and should really be sleeping.).