From owner-freebsd-current@FreeBSD.ORG Wed Oct 1 05:48:16 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8098E1F9B for ; Wed, 1 Oct 2014 05:48:16 +0000 (UTC) Received: from fmailer.gwdg.de (fmailer.gwdg.de [134.76.11.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3F8E18E8 for ; Wed, 1 Oct 2014 05:48:15 +0000 (UTC) Received: from um-excht-a02.um.gwdg.de ([134.76.11.222] helo=email.gwdg.de) by mailer.gwdg.de with esmtp (Exim 4.80) (envelope-from ) id 1XZClo-0002kz-SN; Wed, 01 Oct 2014 07:48:12 +0200 Received: from pc028.nfv (134.76.242.1) by email.gwdg.de (134.76.9.211) with Microsoft SMTP Server (TLS) id 14.3.195.1; Wed, 1 Oct 2014 07:48:12 +0200 Message-ID: <542B9598.5030302@gwdg.de> Date: Wed, 1 Oct 2014 07:48:08 +0200 From: Rainer Hurling User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: Chuck Burns , Subject: Re: pkg/ports system terribly messed up? References: <20140930081301.55bc5629.ohartman@zedat.fu-berlin.de> <4180223.sAzr7DGzUz@blackbeast> In-Reply-To: <4180223.sAzr7DGzUz@blackbeast> Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Level: - X-Virus-Scanned: (clean) by clamav X-Mailman-Approved-At: Wed, 01 Oct 2014 11:05:22 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Oct 2014 05:48:16 -0000 Am 01.10.2014 um 05:44 schrieb Chuck Burns: > On Tuesday, September 30, 2014 8:13:01 AM O. Hartmann wrote: >> Hello. >> >> I just made the last update of the ports yesterday (I use portmaster -da >> performing this task) and obviously or superficially everything went all >> right. >> > > > > It's portmaster actually. While it -usually- works great, I've noticed that > occassionally it loops like that. > > kill the script, upgrade the port that is looping. Because it seems that I have the same problem as Oliver: What script you are talking about? > > That usually fixes it. >