Date: Tue, 04 Oct 2011 13:32:45 +0300 From: Andriy Gapon <avg@FreeBSD.org> To: Colin Percival <cperciva@FreeBSD.org> Cc: FreeBSD-Current <freebsd-current@FreeBSD.org> Subject: portsnap5 problem, portsnap error handling Message-ID: <4E8AE0CD.8010805@FreeBSD.org>
next in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E8AE0CD.8010805>