Date: Fri, 15 Nov 2019 17:27:40 +0100 From: Jan Beich <jbeich@FreeBSD.org> To: Matthew Seaman <matthew@FreeBSD.org> Cc: freebsd-ports@freebsd.org Subject: Re: Many ports recently marked BROKEN/unfetchable that aren't broken? Message-ID: <36ep-w1dv-wny@FreeBSD.org> In-Reply-To: <e8d43aaa-f581-7580-0243-2b962706c07b@FreeBSD.org> (Matthew Seaman's message of "Fri, 15 Nov 2019 15:44:29 %2B0000") References: <CAKOb=YZ_8DACTi7qVveDgETqFoLbfFZE2oov8MdKBwTjXOo3OA@mail.gmail.com> <e8d43aaa-f581-7580-0243-2b962706c07b@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Matthew Seaman <matthew@FreeBSD.org> writes: > 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. Another copy maybe cached on FreeBSD mirrors. Here's how to check: $ make checksum TRYBROKEN= MASTER_SITE_BACKUP= DISTDIR=$(mktemp -dt distfiles)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?36ep-w1dv-wny>