From owner-freebsd-current@FreeBSD.ORG  Wed Oct  1 20:17:58 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 A5C23C3B;
 Wed,  1 Oct 2014 20:17:58 +0000 (UTC)
Received: from mail-ig0-x234.google.com (mail-ig0-x234.google.com
 [IPv6:2607:f8b0:4001:c05::234])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 6DEFBFD4;
 Wed,  1 Oct 2014 20:17:58 +0000 (UTC)
Received: by mail-ig0-f180.google.com with SMTP id uq10so1114638igb.13
 for <multiple recipients>; Wed, 01 Oct 2014 13:17:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type;
 bh=DLXcQXtJ0/dDQWHY7DOTeVrvti3bNAHZm9C4ptgXYD0=;
 b=W9cy/1idD21TMfjKpuC0Nj5+T8gqBp9NdKEMVYnB/qg161LbYMv6EeR5ytbZOJVYoQ
 i7HK+QSA6K4HWfzeIMSFc0k/esGAgjnewWR10c04jMWDzp37EvtQZYfSWcyfgRHNrRw+
 0zfDq/rLgEL9z4H0Mwkx6/xDTy6YXpN155Y/WnQV8JSRRGm9IxflQiwagfrktYPGtmth
 oXx8YP0f0DbmOr/n04/xbf8tkUluyVaAxxx9rLQwTmMQi+IVIZuZVr30GHX4txFRh2PB
 LqEvjNSuda+dwZ3h8rMFU7GvgJjg7FcSnS6XttjXO2jV4je38acNJ8gi7ugXz4jjcGgw
 0AFA==
MIME-Version: 1.0
X-Received: by 10.50.114.38 with SMTP id jd6mr23317212igb.26.1412194677914;
 Wed, 01 Oct 2014 13:17:57 -0700 (PDT)
Received: by 10.50.227.42 with HTTP; Wed, 1 Oct 2014 13:17:57 -0700 (PDT)
In-Reply-To: <20140930081301.55bc5629.ohartman@zedat.fu-berlin.de>
References: <20140930081301.55bc5629.ohartman@zedat.fu-berlin.de>
Date: Wed, 1 Oct 2014 13:17:57 -0700
Message-ID: <CAGHfRMCC=g2bxuk4=Nh98-QLiOy9Saz62yrSxttCyyD_NZ0mjA@mail.gmail.com>
Subject: Re: pkg/ports system terribly messed up?
From: NGie Cooper <yaneurabeya@gmail.com>
To: "O. Hartmann" <ohartman@zedat.fu-berlin.de>
Content-Type: text/plain; charset=UTF-8
Cc: FreeBSD CURRENT <freebsd-current@freebsd.org>,
 FreeBSD Ports <freebsd-ports@freebsd.org>
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: Wed, 01 Oct 2014 20:17:58 -0000

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,