From owner-freebsd-ports@FreeBSD.ORG  Mon Oct  6 09:39:10 2014
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@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 322E696F;
 Mon,  6 Oct 2014 09:39:10 +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 E3F57CF1;
 Mon,  6 Oct 2014 09:39:09 +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 1Xb4l1-00068p-6L; Mon, 06 Oct 2014 11:39:07 +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:39:06 +0200
Message-ID: <54326339.2050807@gwdg.de>
Date: Mon, 6 Oct 2014 11:39:05 +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: NGie Cooper <yaneurabeya@gmail.com>
Subject: Re: pkg/ports system terribly messed up?
References: <20140930081301.55bc5629.ohartman@zedat.fu-berlin.de>
 <CAGHfRMCC=g2bxuk4=Nh98-QLiOy9Saz62yrSxttCyyD_NZ0mjA@mail.gmail.com>
In-Reply-To: <CAGHfRMCC=g2bxuk4=Nh98-QLiOy9Saz62yrSxttCyyD_NZ0mjA@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
X-Spam-Level: -
X-Virus-Scanned: (clean) by clamav
Cc: FreeBSD CURRENT <freebsd-current@freebsd.org>,
 "O. Hartmann" <ohartman@zedat.fu-berlin.de>,
 FreeBSD Ports <freebsd-ports@freebsd.org>
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Oct 2014 09:39:10 -0000

Am 01.10.2014 um 22:17 schrieb NGie Cooper:
> On Mon, Sep 29, 2014 at 11:13 PM, O. Hartmann
> <ohartman@zedat.fu-berlin.de> 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.
>>
>> I'm running on the boxes in question most recent CURRENT.
>>
>> On one system, a subsequent start of updating ports starts to freak out when updateing
>> lang/gcc: it loops over and over on some ports already updated, especially
>> devel/binutils, but the port looping on isn't specific and varies.
>>
>> On every CURRENT box I tried this morning to update the ports again, I find this
>> frsutrating message (depends on installation, but it seems in principal the same, only
>> the affected ports in dependency chain varies):
> 
> Are you using portmaster? If so, it might be fallout from r272282.
> Cheers,

Yup, after defining

setenv PORTSDIR /usr/ports

my problems, described on my mail in this thread from 30th September,
completely went away.

Thanks for this hint. It helps a lot!

Regards,
Rainer Hurling