From owner-freebsd-stable@FreeBSD.ORG Tue Jan 22 21:35:43 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E179716A417 for ; Tue, 22 Jan 2008 21:35:43 +0000 (UTC) (envelope-from jmlopez@disbase.com) Received: from mail.disbase.com (mail.disbase.com [213.149.254.161]) by mx1.freebsd.org (Postfix) with ESMTP id A46B613C4EA for ; Tue, 22 Jan 2008 21:35:43 +0000 (UTC) (envelope-from jmlopez@disbase.com) Received: from localhost (localhost.disbase.com [127.0.0.1]) by mail.disbase.com (Postfix) with ESMTP id D7CB1330884 for ; Tue, 22 Jan 2008 22:17:12 +0100 (CET) X-Virus-Scanned: amavisd-new at disbase.com Received: from mail.disbase.com ([127.0.0.1]) by localhost (disbase7.disbase.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id qYugmb64EEyL for ; Tue, 22 Jan 2008 22:17:05 +0100 (CET) Received: from r2d5.local (235.pool85-52-167.static.orange.es [85.52.167.235]) by mail.disbase.com (Postfix) with ESMTP id 899E733081D for ; Tue, 22 Jan 2008 22:16:59 +0100 (CET) Message-ID: <47965D4B.9020508@disbase.com> Date: Tue, 22 Jan 2008 22:16:59 +0100 From: Jose Miguel Lopez Coronado User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Portsnap update always says Ports tree is already up to date in 6.2 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jan 2008 21:35:44 -0000 Dear all. I have been trying to use portsnap update to update automatically the ports tree in a server running release 6.2, but I always receive the same message: 'Ports tree is already up to date' I know this is not true because I have other freeBSD 6.2 machines with newer ports. If I'm not wrong this have been happening since version 6.2 as release 6.1 did not give me these problems. I'm using 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Jan 12 11:05:30 UTC 2007 Any idea? Thanks in advance and best wishes.