From owner-freebsd-questions@FreeBSD.ORG Tue Dec 28 19:27:21 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0076B10656C2 for ; Tue, 28 Dec 2010 19:27:20 +0000 (UTC) (envelope-from igalgand@freemail.hu) Received: from mail00d.mail.t-online.hu (mail00d.mail.t-online.hu [84.2.42.5]) by mx1.freebsd.org (Postfix) with ESMTP id 64B8D8FC1D for ; Tue, 28 Dec 2010 19:27:20 +0000 (UTC) Received: from thinclient.snowboard.ice (5400D4B1.dsl.pool.telekom.hu [84.0.212.177]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail00d.mail.t-online.hu (Postfix) with ESMTPSA id 23BA77586D4 for ; Tue, 28 Dec 2010 20:07:52 +0100 (CET) Received: from thinclient.snowboard.ice (localhost [127.0.0.1]) by thinclient.snowboard.ice (8.14.4/8.14.4) with ESMTP id oBSJ7pCr082342 for ; Tue, 28 Dec 2010 20:07:51 +0100 (CET) (envelope-from igalgand@thinclient.snowboard.ice) Received: (from igalgand@localhost) by thinclient.snowboard.ice (8.14.4/8.14.4/Submit) id oBSJ7TQM082341 for freebsd-questions@freebsd.org; Tue, 28 Dec 2010 20:07:29 +0100 (CET) (envelope-from igalgand) Date: Tue, 28 Dec 2010 20:07:29 +0100 From: Istvan Galgand To: FreeBSD Message-ID: <20101228190729.GA82329@thinclient.snowboard.ice> References: <20101228075158.78687cc6@scorpio> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline In-Reply-To: <20101228075158.78687cc6@scorpio> User-Agent: Mutt/1.4.2.3i Subject: Re: Problem with 'portsnap' X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Dec 2010 19:27:21 -0000 On Tue, Dec 28, 2010 at 07:51:58AM -0500, Jerry wrote: > For the past few days, I have been having problems updating my ports > tree via 'portsnap'. It continually gives errors similar to the > following: > > > Looking up portsnap.FreeBSD.org mirrors... 5 mirrors found. > Fetching snapshot tag from portsnap2.FreeBSD.org... failed. > Fetching snapshot tag from portsnap6.FreeBSD.org... failed. > Fetching snapshot tag from portsnap1.FreeBSD.org... failed. > Fetching snapshot tag from portsnap5.FreeBSD.org... failed. > Fetching snapshot tag from portsnap4.FreeBSD.org... done. > Fetching snapshot metadata... fetch: http://portsnap4.FreeBSD.org/t/4816ec0c67a1c999c4d3875335b3d419a1a1a2497262158e661b9b5973b0453a: No address record > sha256: 4816ec0c67a1c999c4d3875335b3d419a1a1a2497262158e661b9b5973b0453a: No such file or directory > [: !=: unexpected operator > mv: rename 4816ec0c67a1c999c4d3875335b3d419a1a1a2497262158e661b9b5973b0453a 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. > > Dear All, For the past two days I experienced exactly the same phenomena. By this morning (CET, Tuesday) the normal operation has been restored. Istvan -- This mail was sent by Mutt-1.4.2.3_4, FreeBSD 8.1-RELEASE-#0, GENERIC i386