From owner-freebsd-ports@FreeBSD.ORG Thu Dec 13 16:56:37 2012 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 40A9FDA for ; Thu, 13 Dec 2012 16:56:37 +0000 (UTC) (envelope-from lists@pingle.org) Received: from chloe.pingle.org (unknown [IPv6:2605:8000:d:1:40::1]) by mx1.freebsd.org (Postfix) with ESMTP id 005208FC1C for ; Thu, 13 Dec 2012 16:56:36 +0000 (UTC) Received: from chloe.pingle.org (unknown [127.0.0.1]) by chloe.pingle.org (Postfix) with ESMTP id 4BAF945095 for ; Thu, 13 Dec 2012 11:56:35 -0500 (EST) X-Virus-Scanned: amavisd-new at pingle.org Received: from chloe.pingle.org ([127.0.0.1]) by chloe.pingle.org (chloe.pingle.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ryovTryTFOpH for ; Thu, 13 Dec 2012 11:56:34 -0500 (EST) Received: from [IPv6:2001:470:1f11:e1c:dead:beef:c0de:cafe] (unknown [IPv6:2001:470:1f11:e1c:dead:beef:c0de:cafe]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jim) by chloe.pingle.org (Postfix) with ESMTPSA id C30B84508F for ; Thu, 13 Dec 2012 11:56:34 -0500 (EST) Message-ID: <50CA08BD.7090304@pingle.org> Date: Thu, 13 Dec 2012 11:56:29 -0500 From: Jim Pingle User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: freebsd-ports@freebsd.org Subject: Ports "make fetchindex" still getting outdated INDEX-9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Dec 2012 16:56:37 -0000 I saw a thread last month about the servers that build INDEX files being down since the security incident - is that still the case? The files obtained via make fetchindex are still out of date, so I assume they're still off, but a while back they were just missed after some maintenance as well so part of me hoped that it may be the case yet again. Any ETA on when that service might return? I can always build the index manually or use portsnap, but fetchindex is really convenient and I'd love to see it brought back to life. Perhaps the fetchindex target could be altered to print a brief message in the interim so people know that it's not currently being updated? Jim