Date: Fri, 15 Nov 2019 15:44:29 +0000 From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-ports@freebsd.org Subject: Re: Many ports recently marked BROKEN/unfetchable that aren't broken? Message-ID: <e8d43aaa-f581-7580-0243-2b962706c07b@FreeBSD.org> In-Reply-To: <CAKOb=YZ_8DACTi7qVveDgETqFoLbfFZE2oov8MdKBwTjXOo3OA@mail.gmail.com> References: <CAKOb=YZ_8DACTi7qVveDgETqFoLbfFZE2oov8MdKBwTjXOo3OA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 15/11/2019 15:25, Nick Rogers wrote:
> For me the affected ports were sysutils/pftop, sysutils/zfs-stats, and
> sysutils/stress, which worked just fine before this commit. Apologies if I
> am missing something, but it seems like they are not actually broken?
If you were building these ports previously, then you probably have the
distfiles in your local distfiles cache already. That will give the
impression that everything is fine if you just try and build the port.
If you didn't have a cached copy of the distfiles, then you'ld probably
have a rather different experience.
Although if you can show that the distfiles are now fetchable, eg. by:
make distclean
make fetch
then by all means please do report it. A PR with patches is preferred,
but any reasonable mechanism for bringing it to the attention of
developers is acceptable.
Cheers,
Matthew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e8d43aaa-f581-7580-0243-2b962706c07b>