A new link for the source file to the broken package:
(In reply to Jørgen Asmussen from comment #0)
It seems that the file I'm linking to does not have the same sha256, nor the same size, so while it's technically the same software, the new link won't work due to not being the same.
It seems that the original source file has vanished into the void as the domain that once hosted it is no longer operational.
Is there anything I can do to get this package back to non-broken condition?
Or not... I should've validated the SHA256 on a fbsd system, which I now did and the SHA256 is the same. So it should be a valid new source for the port.
Created attachment 210498 [details]
Patch that enables fetching from new set of distfiles
A little patch that makes the port build. Timestamp has been updated, but checksum matches existing distfile on record.
The only concern I had is why is the SHA256 different on a non FreeBSD system?
Also probably need to submit the same update to security/pam_pseudo
Chrome unpacked the gzip on download, which I only noticed after I wrote this.
A few more sources for the file:
Created attachment 210522 [details]
New patch that adds more MASTER_SITES
I've added the MASTER_SITES listed, and since I was unsure that I checked whether it built, I went ahead and tested.
If it passes approval, please remember to set the maintainer flag, so we can get this done :)
Created attachment 210523 [details]
Build log from make build
Created attachment 210524 [details]
Fixed diff with only one MASTER_SITE
Whoops, I made a mistake and included (unofficial) FreeBSD distfile caches, so reverting to the originally uploaded diff.
User in question figured out another solution that doesn't involve reviving an expired port.