Date: Mon, 6 Oct 2014 11:34:33 +0200 From: Rainer Hurling <rhurlin@gwdg.de> To: Chuck Burns <break19@gmail.com>, <freebsd-current@freebsd.org> Subject: Re: pkg/ports system terribly messed up? Message-ID: <54326229.2080204@gwdg.de> In-Reply-To: <3029778.sRTk01SrzP@blackbeast> References: <20140930081301.55bc5629.ohartman@zedat.fu-berlin.de> <4180223.sAzr7DGzUz@blackbeast> <542B9598.5030302@gwdg.de> <3029778.sRTk01SrzP@blackbeast>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54326229.2080204>