From owner-freebsd-current@FreeBSD.ORG Mon Oct 17 18:03:52 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2C505106566B for ; Mon, 17 Oct 2011 18:03:52 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id DAA178FC0A for ; Mon, 17 Oct 2011 18:03:51 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) with esmtp (envelope-from ) id <1RFrXT-0001EL-0Z>; Mon, 17 Oct 2011 20:03:51 +0200 Received: from e178041166.adsl.alicedsl.de ([85.178.41.166] helo=thor.walstatt.dyndns.org) by inpost2.zedat.fu-berlin.de (Exim 4.69) with esmtpsa (envelope-from ) id <1RFrXS-0004jl-PD>; Mon, 17 Oct 2011 20:03:51 +0200 Message-ID: <4E9C6E02.2060605@zedat.fu-berlin.de> Date: Mon, 17 Oct 2011 20:03:46 +0200 From: "Hartmann, O." User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:7.0.1) Gecko/20111013 Thunderbird/7.0.1 MIME-Version: 1.0 To: Eitan Adler References: <4E9C592F.5050600@zedat.fu-berlin.de> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Originating-IP: 85.178.41.166 Cc: freebsd-current Subject: Re: Help! Portsnap won't work on freeBSD 10.0-CURRENT/amd64! look: tINDEX.new: File too large X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Oct 2011 18:03:52 -0000 On 10/17/11 19:24, Eitan Adler wrote: > On Mon, Oct 17, 2011 at 12:34 PM, Hartmann, O. > wrote: >> Hello, >> since several days now I receive on FreeBSD 10.0-CURRENT/amd64 boxes >> this message: > A commit to look(1) broke portsnap. > cd /usr/src/usr.bin/look > svn up -r216370 > make > make install > and things should return to normal. > Ok ... the today's buildworld seems to have 'repaired' the problem. Thanks. Regards, Oliver