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