From owner-freebsd-questions@FreeBSD.ORG Sat Jan 7 05:25:56 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3B61516A41F for ; Sat, 7 Jan 2006 05:25:56 +0000 (GMT) (envelope-from rperry@gti.net) Received: from apollo.gti.net (apollo.gti.net [199.171.27.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id E6C6243D46 for ; Sat, 7 Jan 2006 05:25:55 +0000 (GMT) (envelope-from rperry@gti.net) Received: from [192.168.1.15] (morr0661.gti.net [208.216.122.61]) by apollo.gti.net (mail) with ESMTP id 78CE53632E for ; Sat, 7 Jan 2006 00:22:20 -0500 (EST) Message-ID: <43BF5118.5030105@gti.net> Date: Sat, 07 Jan 2006 00:26:48 -0500 From: "Robert H. Perry" User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051223) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Resolved: Need Assistance Upgrading Ethereal-0.10.13_3 to 0.10.14 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Jan 2006 05:25:56 -0000 -------- Original Message -------- Subject: Need Assistance Upgrading Ethereal-0.10.13_3 to 0.10.14 Date: Sat, 31 Dec 2005 00:52:21 -0500 From: Robert H. Perry To: freebsd-questions@freebsd.org FreeBSD sphinx.my.domain 5.4-RELEASE FreeBSD 5.4-RELEASE #0: Ran into the following error while running portupgrade on ethereal: ==> applying extra patch /usr/ports/net/ethereal/files/extra-patch-capture_loop.c ***Error code 1 Stop in usr/ports/net/ethereal. Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade43330.26 make ** Fix the problem and try again. The recommendation "Fix the problem and try again." seems relatively straightforward, however... Is this an error I should know how to easily fix? Please advise. Thnx Just want to report that the error noted above did not re-occur during this week's upgrade. Have no idea how, or why. Bob Perry