From owner-freebsd-current@FreeBSD.ORG  Mon Oct  6 09:34:36 2014
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id D2B0F7FD
 for <freebsd-current@freebsd.org>; Mon,  6 Oct 2014 09:34:36 +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 91F21CA8
 for <freebsd-current@freebsd.org>; Mon,  6 Oct 2014 09:34:36 +0000 (UTC)
Received: from um-excht-a01.um.gwdg.de ([134.76.11.221] helo=email.gwdg.de)
 by mailer.gwdg.de with esmtp (Exim 4.80)
 (envelope-from <rhurlin@gwdg.de>)
 id 1Xb4gc-00059D-HT; Mon, 06 Oct 2014 11:34:34 +0200
Received: from lt047.nfv (87.187.105.231) by email.gwdg.de (134.76.9.210) with
 Microsoft SMTP Server (TLS) id 14.3.195.1;
 Mon, 6 Oct 2014 11:34:34 +0200
Message-ID: <54326229.2080204@gwdg.de>
Date: Mon, 6 Oct 2014 11:34:33 +0200
From: Rainer Hurling <rhurlin@gwdg.de>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:31.0) Gecko/20100101 Thunderbird/31.1.2
MIME-Version: 1.0
To: Chuck Burns <break19@gmail.com>, <freebsd-current@freebsd.org>
Subject: Re: pkg/ports system terribly messed up?
References: <20140930081301.55bc5629.ohartman@zedat.fu-berlin.de>
 <4180223.sAzr7DGzUz@blackbeast> <542B9598.5030302@gwdg.de>
 <3029778.sRTk01SrzP@blackbeast>
In-Reply-To: <3029778.sRTk01SrzP@blackbeast>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
X-Spam-Level: -
X-Virus-Scanned: (clean) by clamav
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Oct 2014 09:34:36 -0000

Am 02.10.2014 um 04:40 schrieb Chuck Burns:
> On Wednesday, October 01, 2014 7:48:08 AM Rainer Hurling wrote:
>> 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.
>>>
>>> <snip>
>>>
>>> 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.
> 
> portmaster is just a (not-so-)simple shell script.  Kill portmaster (CTRL-C 
> a few times) then build the offending port with "make && make 
> deinstall reinstall clean"
> 
Thanks for your answer. I tried it, but unfortunately, this does not
change my problems with using portmaster for updating ports.