From owner-freebsd-gnome@FreeBSD.ORG Fri Dec 16 21:00:52 2005 Return-Path: X-Original-To: freebsd-gnome@freebsd.org Delivered-To: freebsd-gnome@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A854816A41F for ; Fri, 16 Dec 2005 21:00:52 +0000 (GMT) (envelope-from knowtree@aloha.com) Received: from relay.pixi.com (relay.pixi.com [206.127.224.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id CDEFC43D73 for ; Fri, 16 Dec 2005 21:00:51 +0000 (GMT) (envelope-from knowtree@aloha.com) Received: from carter.pixi.com (carter.pixi.com [206.127.224.102]) by relay.pixi.com (8.13.4/8.13.4) with ESMTP id jBGL0omn000449 for ; Fri, 16 Dec 2005 11:00:50 -1000 (HST) Received: from Internal (206.127.224.41) by carter.pixi.com with SMTP; Fri, 16 Dec 2005 11:00:48 -1000 X-Titankey-e_id: Received: from yoda.pixi.com (yoda.pixi.com [206.127.224.41]) by yoda.pixi.com (8.11.6/8.11.6) with SMTP id jBGJuib09770 for ; Fri, 16 Dec 2005 09:56:44 -1000 Message-Id: <200512161956.jBGJuib09770@yoda.pixi.com> To: freebsd-gnome@freebsd.org From: knowtree@aloha.com Date: Fri, 16 Dec 2005 09:56:44 HST X-Posting-IP: 141.190.32.69 X-Mailer: Endymion MailMan Standard Edition v3.2.19 Subject: Cannot build portupgrade X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 21:00:52 -0000 While upgrading to 2.12 via the script the process fails at stage 2 when trying to upgrade sysutils/portupgrade. It is failing to fetch pkgtools-20051204.tar.bz2. Two sources are listed for this file, http://dists.lovepeers.org and ftp://ftp.iDaemons.prg. The first seems to be dead, and the second always times out. I poked around in ftp.freebsd.org but only found the previous release, 20041224, which I have. I sent mail to the port maintainer, but the address is koma2@lovepeers.org, and that servers appears to be down. I am running 5.4-RELEASE. Am I doing something stupid again? :-) Is there a work-around? Gary Dunn Honolulu