From owner-freebsd-ports@FreeBSD.ORG Fri Jan 6 16:22:43 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 5632216A41F for ; Fri, 6 Jan 2006 16:22:43 +0000 (GMT) (envelope-from mikej@rogers.com) Received: from smtp103.rog.mail.re2.yahoo.com (smtp103.rog.mail.re2.yahoo.com [206.190.36.81]) by mx1.FreeBSD.org (Postfix) with SMTP id CCB0543D45 for ; Fri, 6 Jan 2006 16:22:39 +0000 (GMT) (envelope-from mikej@rogers.com) Received: (qmail 63624 invoked from network); 6 Jan 2006 16:22:38 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=s49vfbiO4BMCRjiSyaAwy5kXLb1d/OYPBJLGhFCnAdSwzJf4kBf7gRnF4+LKd1+XLT94bIanW28DIgFxOwjiogjeOCkfZcxh22Vr/vpOxyP2kDahU3HauqWdVDh+wSPJBjxpJiQbH1iHCZy6aSNlB0zmcG/EjuGYtwCPHOgSBG8= ; Received: from unknown (HELO ?70.30.133.184?) (mikej@rogers.com@70.30.133.184 with plain) by smtp103.rog.mail.re2.yahoo.com with SMTP; 6 Jan 2006 16:22:38 -0000 Message-ID: <43BE9988.1000404@rogers.com> Date: Fri, 06 Jan 2006 11:23:36 -0500 From: Mike Jakubik User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: "Koopmann, Jan-Peter" References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: koma2@lovepeers.org, freebsd-ports@freebsd.org Subject: Re: portupgrade hangs 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, 06 Jan 2006 16:22:43 -0000 Koopmann, Jan-Peter wrote: > Hi, > > after installing the latest portupgrade port all of its application hang. Portversion sometimes shows the first port in the database, most of the time it just hangs. portupgrade does not work either. This happens on all 4.x machines we upgraded it on. Any ideas? > Read the postings on this list, portupgrade 2.0.1 has problems handling moved ports. You may want to try running with --ignore-moved as a work around.