From owner-freebsd-ports@FreeBSD.ORG Sun Mar 9 14:54:34 2008 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4F0A81065672 for ; Sun, 9 Mar 2008 14:54:34 +0000 (UTC) (envelope-from simon@zaphod.nitro.dk) Received: from mx.nitro.dk (zarniwoop.nitro.dk [83.92.207.38]) by mx1.freebsd.org (Postfix) with ESMTP id 02A198FC23 for ; Sun, 9 Mar 2008 14:54:33 +0000 (UTC) (envelope-from simon@zaphod.nitro.dk) Received: from zaphod.nitro.dk (unknown [192.168.3.39]) by mx.nitro.dk (Postfix) with ESMTP id 72A9D1E8C07; Sun, 9 Mar 2008 14:38:57 +0000 (UTC) Received: by zaphod.nitro.dk (Postfix, from userid 3000) id A271B11493; Sun, 9 Mar 2008 15:38:58 +0100 (CET) Date: Sun, 9 Mar 2008 15:38:53 +0100 From: "Simon L. Nielsen" To: Rene Ladan Message-ID: <20080309143850.GB1097@zaphod.nitro.dk> References: <20080309090407.01316de7@scorpio> <47D3E7F1.500@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <47D3E7F1.500@gmail.com> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: gerard@seibercom.net, freebsd-ports@freebsd.org Subject: Re: Portsnap: Cowardly Gives Up After Failure X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Mar 2008 14:54:34 -0000 On 2008.03.09 14:36:49 +0100, Rene Ladan wrote: > Gerard schreef: > > I just saw this 'portsnap' error message for the first time. > > > > > > Looking up portsnap.FreeBSD.org mirrors... 4 mirrors found. > > Fetching snapshot tag from portsnap2.FreeBSD.org... done. > > Latest snapshot on server is older than what we already have! > > Cowardly refusing to downgrade from Fri Mar 7 15:23:43 EST 2008 > > to Fri Mar 7 10:15:54 EST 2008. > > > I see this happening about half the times I run portsnap. The > erroneous image is always from March 7. The most likely cause of the problem is that the data portsnap is trying to fetch is out of date either bacause of the mirror being (partially?) broken or e.g. a broken proxy in between. Is the working or non-working related to a particular portsnap server? -- Simon L. Nielsen Hat: portsnap co-admin