From owner-freebsd-ports@FreeBSD.ORG Fri Mar 31 16:43:47 2006 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CE8B716A400 for ; Fri, 31 Mar 2006 16:43:47 +0000 (UTC) (envelope-from pauls@utdallas.edu) Received: from smtp1.utdallas.edu (smtp1.utdallas.edu [129.110.10.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8480D43D46 for ; Fri, 31 Mar 2006 16:43:47 +0000 (GMT) (envelope-from pauls@utdallas.edu) Received: from utd59514.utdallas.edu (utd59514.utdallas.edu [129.110.3.28]) by smtp1.utdallas.edu (Postfix) with ESMTP id 2A2DB38933B; Fri, 31 Mar 2006 10:43:47 -0600 (CST) Date: Fri, 31 Mar 2006 10:43:24 -0600 From: Paul Schmehl To: Florent Thoumie Message-ID: <0914BF61B90385ED2EA5C47D@utd59514.utdallas.edu> In-Reply-To: <1143796773.65237.8.camel@mayday.esat.net> References: <19B4FEF7616674F09DF8BF90@Paul-Schmehls-Computer.local> <1143796773.65237.8.camel@mayday.esat.net> X-Mailer: Mulberry/4.0.0b4 (Linux/x86) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=sha1; protocol="application/pkcs7-signature"; boundary="==========3E347D8B4D9BF5E2907E==========" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-ports@freebsd.org Subject: Re: freebsd-update broken? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Mar 2006 16:43:47 -0000 --==========3E347D8B4D9BF5E2907E========== Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --On Friday, March 31, 2006 10:19:33 +0100 Florent Thoumie =20 wrote: > On Thu, 2006-03-30 at 20:09 -0600, Paul Schmehl wrote: >> security/freebsd-update is supposed to work for amd64, however: >> >> freebsd-update fetch >> Fetching public key... >> fetch: http://update.daemonology.net/amd64/6.0/pub.key: Not Found >> Error fetching updates >> >> There is not amd64 directory on the server. > > There's no support (at the moment) for !i386 archs. Why is this in the Makefile then? # The RSA code has been tested and works on these platforms. On other # platforms, it either doesn't work or hasn't been tested. ONLY_FOR_ARCHS=3D i386 amd64 alpha sparc64 And shouldn't it refuse to install on a non-i386 box? Paul Schmehl (pauls@utdallas.edu) Adjunct Information Security Officer The University of Texas at Dallas http://www.utdallas.edu/ir/security/ --==========3E347D8B4D9BF5E2907E==========--