From owner-freebsd-amd64@FreeBSD.ORG Sun Mar 27 03:20:04 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 05F9716A4D6 for ; Sun, 27 Mar 2005 03:20:04 +0000 (GMT) Received: from blake.polstra.com (blake.polstra.com [64.81.189.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 79F8943D41 for ; Sun, 27 Mar 2005 03:20:03 +0000 (GMT) (envelope-from jdp@polstra.com) Received: from t30w.polstra.com (dsl081-189-078.sea1.dsl.speakeasy.net [64.81.189.78]) by blake.polstra.com (8.13.1/8.13.1) with ESMTP id j2R3K2qo094147 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 26 Mar 2005 19:20:02 -0800 (PST) (envelope-from jdp@mail.polstra.com) Received: from t30w.polstra.com (localhost [127.0.0.1]) by t30w.polstra.com (8.12.11/8.12.11) with ESMTP id j2R3K2d3000840; Sat, 26 Mar 2005 19:20:02 -0800 (PST) (envelope-from jdp@t30w.polstra.com) Received: (from jdp@localhost) by t30w.polstra.com (8.12.11/8.12.11/Submit) id j2R3K2Oc000839; Sat, 26 Mar 2005 19:20:02 -0800 (PST) (envelope-from jdp) Message-ID: X-Mailer: XFMail 1.5.5 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <2fd864e05032618419b6b2a5@mail.gmail.com> Date: Sat, 26 Mar 2005 19:20:02 -0800 (PST) From: John Polstra To: Astrodog X-Bogosity: No, tests=bogofilter, spamicity=0.000912, version=0.14.5 cc: amd64@freebsd.org Subject: Re: cvsup now broken for amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Mar 2005 03:20:04 -0000 On 27-Mar-2005 Astrodog wrote: > On Sat, 26 Mar 2005 18:36:09 -0800 (PST), John Polstra wrote: >> I would fix it if I knew how. All I did was add a patch; I wasn't >> expecting that to break anything. I didn't put in the binary-only >> amd64 stuff and I don't know how to fix it. >> >> If push comes to shove, I'll back out my commit and leave it at >> that. >> > What does the patch do? It fixes a bug that causes people's INDEX files to be deleted. The amd64 build is failing because it's binary-only, but it is still trying to apply the patch. John