Many ports recently marked BROKEN/unfetchable that aren't broken?
Jan Beich
jbeich at FreeBSD.org
Fri Nov 15 16:27:43 UTC 2019
Matthew Seaman <matthew at 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)
More information about the freebsd-ports
mailing list