I submitted a Pull Request to update MacPorts' signify to 1.62 here:
https://github.com/macports/macports-ports/pull/31080
GitHub Continuous Integration checks queued.
Hopefully they will run without issue?
If so, it's up to someone else with commit access to merge it.
This isn't very significant from the last PR I submitted from late October 2025 (upstream has a commit from early September 2025 so I am trailing by many months with this one) however, remarkable to me:
MacPorts' signify's version is now in alignment with upstream's versioning!
Yay!
I have no idea if that was true previously? My guess is: no, since I think jpouellet/Jean-Philippe Ouellet branched that out a long time ago and seemed to have iterated version tags haphazardly? Maybe I am mistaken though! There's a completely different Linuxism fork of signify which seems to have evolved (and versioned) very differently too.
That in particular has confused me with spurious repology.org out of date error messages for many months. I dunno if it has confused others, or if this version sync will make things less confusing, but hopefully? It makes things less confusing for me at least.
In tangential news, since I saw tedu in the man page, someone was wondering where he got off to a while ago and I don't think I saw a response. Hopefully he's doin OK? Please?
#signify #MacPorts #macOS #OpenSource #OpenBSD #cryptography
Discussion
Loading...
Thanks to some perspective here: https://trac.macports.org/ticket/73474#comment:2 I ended up closing that Pull Request and opened a different one after having added the legacysupport PortGroup, in hopes that it smooths things over on older versions of OS X:
https://github.com/macports/macports-ports/pull/31087
If that goes well, then the subsequent step would be to update the version of signify in MacPorts' base to be in closer alignment with upstream too.
fingers crossed
GitHub continues to confuse tf out of me and I do not have sufficient words for how much I dislike it, but I think maybe I set the default branch to the most recent release of macOS-signify so that it at least reflects the updated README.md correctly?
Maybe that will help others be less confused!
Doubtlessly, I will remain confused for various other reasons.
I opened a MacPorts' Trac issue related to signify's Port Health on versions of OS X older than Sierra here:
https://trac.macports.org/ticket/73474
I don't have a good way to test older OS X versions at the moment, so hopefully others will be able to assist?
MacPorts also uses signify internally, but it is not the same signify as the Portfile for which I submitted a Pull Request, and if older OS X versions are not building that correctly, I can't think of a good reason for MacPorts base to change either.
Hopefully, there's a simple fix for the Port Health stuff? That realm is rather opaque to me at present.