From owner-freebsd-ports@freebsd.org  Fri Nov 15 16:27:43 2019
Return-Path: <owner-freebsd-ports@freebsd.org>
Delivered-To: freebsd-ports@mailman.nyi.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.nyi.freebsd.org (Postfix) with ESMTP id 18C521A9FEF
 for <freebsd-ports@mailman.nyi.freebsd.org>;
 Fri, 15 Nov 2019 16:27:43 +0000 (UTC)
 (envelope-from jbeich@freebsd.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
 [IPv6:2610:1c1:1:6074::16:84])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 server-signature RSA-PSS (4096 bits)
 client-signature RSA-PSS (4096 bits) client-digest SHA256)
 (Client CN "freefall.freebsd.org",
 Issuer "Let's Encrypt Authority X3" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 47F3fk5qMLz3DZS;
 Fri, 15 Nov 2019 16:27:42 +0000 (UTC)
 (envelope-from jbeich@freebsd.org)
Received: by freefall.freebsd.org (Postfix, from userid 1354)
 id 90818C25A; Fri, 15 Nov 2019 16:27:42 +0000 (UTC)
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?
References: <CAKOb=YZ_8DACTi7qVveDgETqFoLbfFZE2oov8MdKBwTjXOo3OA@mail.gmail.com>
 <e8d43aaa-f581-7580-0243-2b962706c07b@FreeBSD.org>
Date: Fri, 15 Nov 2019 17:27:40 +0100
In-Reply-To: <e8d43aaa-f581-7580-0243-2b962706c07b@FreeBSD.org> (Matthew
 Seaman's message of "Fri, 15 Nov 2019 15:44:29 +0000")
Message-ID: <36ep-w1dv-wny@FreeBSD.org>
MIME-Version: 1.0
Content-Type: text/plain
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Nov 2019 16:27:43 -0000

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)