From owner-freebsd-current@FreeBSD.ORG Fri Jun 3 21:31:44 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C7C0616A41C for ; Fri, 3 Jun 2005 21:31:44 +0000 (GMT) (envelope-from robbak@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3ABC143D49 for ; Fri, 3 Jun 2005 21:31:44 +0000 (GMT) (envelope-from robbak@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so872551wri for ; Fri, 03 Jun 2005 14:31:43 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=Z1902ygHNGJ/afTqDHXiRkE5bYWW+qiiczUtu9daWDR3G/faeQKIVRRpHhlnzBKfwsJ9/eT0uEpzsu/SWlM4PkQHiCCx3y+NR3lbIVTqUBaBQ3NrMP3PaK+/0IPwyiD7qlCIKbV59a8fvhXfs8mWYygT1YDR9btgiEB2kxnVDy0= Received: by 10.54.56.50 with SMTP id e50mr632954wra; Fri, 03 Jun 2005 14:31:43 -0700 (PDT) Received: by 10.54.130.5 with HTTP; Fri, 3 Jun 2005 14:31:43 -0700 (PDT) Message-ID: Date: Sat, 4 Jun 2005 07:31:43 +1000 From: Robert Backhaus To: FreeBSD Current Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: cvsup6.au.freebsd.org Horrendously out of date. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Robert Backhaus List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2005 21:31:44 -0000 I just 'updated' my ports and source trees unattended from cvsup6.au.freebsd.org, selected by fastest_cvsup, and discovered that I now had a source tree dated from December, 2004. Yikes!!! This server needs to be taked out of the loop urgently. This is not the first time that this has happened to me with this server, (yes, I am a sucker for punnishment - I thought that it would have been fixed by now!), so it is not a temporary error. Even if it is updated, I would question whether the server is reliable enough to continue in use.