Date: Sat, 16 May 2020 10:44:19 +0200 From: Stefan Ehmann <shoesoft@gmx.net> To: freebsd-ports@freebsd.org Cc: "Edward Sanford Sutton, III" <mirror176@hotmail.com> Subject: Re: Are broken ports retested before performing scheduled removal? Message-ID: <15810795.vxEf1mJfsr@walrus.pepperland> In-Reply-To: <c0622ac7-d4bb-e133-ac71-35cc4de56d89@hotmail.com> References: <c0622ac7-d4bb-e133-ac71-35cc4de56d89@hotmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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=3Dunfetchable DEPRECATED=3DBroken 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 i= s a transient failure. Of course, unless someone opens a bug report.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15810795.vxEf1mJfsr>