Are broken ports retested before performing scheduled removal?

[Stefan Ehmann]

On Thursday, May 14, 2020 1:24:17 AM CEST Edward Sanford Sutton, III wrote:
>   games/oneko was recently removed as it was marked broken due to being
> unfetchable. I tried an old copy of the ports tree I had where it was
> marked as such and `make fetch -DTRYBROKEN` succeeded. Was there an
> error recorded for this and was it ever retested? Is this just a side
> effect of having a failure and no maintainer?
>   If being removed as unfetchable, wouldn't a better MOVED entry be to
> say it was unfetchable (for more than 6 months) instead of just broken
> for more than 6 months?
> Thanks for feedback

I've recently asked myself the same question:

multimedia/gpac-mp4box is flagged
BROKEN=unfetchable
DEPRECATED=Broken for more than 6 months

multimedia/gpac-libgpac uses the same distfile from the same mirror and is not
marked broken.

I figured once a port is marked unfetchable, it will be deleted, even it is a
transient failure. Of course, unless someone opens a bug report.