Date: Wed, 1 Oct 2014 13:17:57 -0700 From: NGie Cooper <yaneurabeya@gmail.com> To: "O. Hartmann" <ohartman@zedat.fu-berlin.de> Cc: FreeBSD CURRENT <freebsd-current@freebsd.org>, FreeBSD Ports <freebsd-ports@freebsd.org> Subject: Re: pkg/ports system terribly messed up? Message-ID: <CAGHfRMCC=g2bxuk4=Nh98-QLiOy9Saz62yrSxttCyyD_NZ0mjA@mail.gmail.com> In-Reply-To: <20140930081301.55bc5629.ohartman@zedat.fu-berlin.de> References: <20140930081301.55bc5629.ohartman@zedat.fu-berlin.de>
next in thread | previous in thread | raw e-mail | index | archive | help
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,
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGHfRMCC=g2bxuk4=Nh98-QLiOy9Saz62yrSxttCyyD_NZ0mjA>