From owner-freebsd-current@FreeBSD.ORG  Tue Oct  4 10:32:51 2011
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 96068106566B;
	Tue,  4 Oct 2011 10:32:51 +0000 (UTC) (envelope-from avg@FreeBSD.org)
Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140])
	by mx1.freebsd.org (Postfix) with ESMTP id B7FC68FC12;
	Tue,  4 Oct 2011 10:32:50 +0000 (UTC)
Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua
	[212.40.38.100])
	by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id NAA15006;
	Tue, 04 Oct 2011 13:32:48 +0300 (EEST)
	(envelope-from avg@FreeBSD.org)
Received: from localhost ([127.0.0.1])
	by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD))
	id 1RB2Iq-000JWK-8D; Tue, 04 Oct 2011 13:32:48 +0300
Message-ID: <4E8AE0CD.8010805@FreeBSD.org>
Date: Tue, 04 Oct 2011 13:32:45 +0300
From: Andriy Gapon <avg@FreeBSD.org>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
	rv:7.0.1) Gecko/20111002 Thunderbird/7.0.1
MIME-Version: 1.0
To: Colin Percival <cperciva@FreeBSD.org>
X-Enigmail-Version: undefined
Content-Type: text/plain; charset=X-VIET-VPS
Content-Transfer-Encoding: 7bit
Cc: FreeBSD-Current <freebsd-current@FreeBSD.org>
Subject: portsnap5 problem, portsnap error handling
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Oct 2011 10:32:51 -0000


Not sure which list would be best for this, so using current@.

$ portsnap fetch && portsnap update
Looking up portsnap.FreeBSD.org mirrors... 5 mirrors found.
Fetching snapshot tag from portsnap5.FreeBSD.org... done.
Fetching snapshot metadata... fetch:
http://portsnap5.FreeBSD.org/t/c1bdea4c38cc6b417dedc1d0e75727118ed2ee08c41726ee49931f2c99288162:
Not Found
sha256: c1bdea4c38cc6b417dedc1d0e75727118ed2ee08c41726ee49931f2c99288162: No
such file or directory
[: !=: unexpected operator
mv: rename c1bdea4c38cc6b417dedc1d0e75727118ed2ee08c41726ee49931f2c99288162 to
tINDEX.new: No such file or directory
done.
grep: tINDEX.new: No such file or directory
look: tINDEX.new: No such file or directory

Portsnap metadata appears bogus.
Cowardly refusing to proceed any further.

First, it seems that portsnap5 host is missing at least one important file.
Second, it seems that portsnap should detect this kind of problem a little bit
earlier.  No need to call sha256, mv, etc if fetch clearly failed.
(Not sure, perhaps this is fetch not returning an error code).

-- 
Andriy Gapon