From owner-freebsd-current@FreeBSD.ORG Thu Oct 2 02:40:09 2014 Return-Path: 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 E988B7C2 for ; Thu, 2 Oct 2014 02:40:09 +0000 (UTC) Received: from mail-qc0-x230.google.com (mail-qc0-x230.google.com [IPv6:2607:f8b0:400d:c01::230]) (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 A5DF3242 for ; Thu, 2 Oct 2014 02:40:09 +0000 (UTC) Received: by mail-qc0-f176.google.com with SMTP id r5so1529273qcx.21 for ; Wed, 01 Oct 2014 19:40:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:message-id:user-agent:in-reply-to:references :mime-version:content-transfer-encoding:content-type; bh=ljXbklJPLhndeimpcFcDx8oXUdfDLLDR5DTC/reFcts=; b=HD1GvlySnRFSSDIIDem4hsG7U+P+OcZ0IMqRif0dDDSs28usuQ4cKIDBI1M2kIvCB2 nzqDluIbvgkR4Mu8cpTFzYAM1YNzf0YYqzqRRYGk7kpGD/CzytK9A1lrcrusuU+qQVd2 XrSAmUcvckmY41LDefTshgYJJCwZ6VTRlOHkMY/lGL0DZ97UmjFIy3DW184RYp8NAmIn 7cjE+zh6aIld2R/E96jw1X8JJqB1+Q/+28YDvmzebJ/gWlCvoAAAYKtyHNc8Cw1Qq+B2 Hy0chJZwlmDNW2TdhU/+oy3hODRzLCmPgrZyQFOLyQmR7g5KpYumd4virrZPBezLoKpc U8VQ== X-Received: by 10.224.115.14 with SMTP id g14mr44863759qaq.23.1412217608765; Wed, 01 Oct 2014 19:40:08 -0700 (PDT) Received: from blackbeast.localnet (173-26-254-198.client.mchsi.com. [173.26.254.198]) by mx.google.com with ESMTPSA id s4sm2238693qay.36.2014.10.01.19.40.08 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 01 Oct 2014 19:40:08 -0700 (PDT) From: Chuck Burns To: freebsd-current@freebsd.org Subject: Re: pkg/ports system terribly messed up? Date: Wed, 01 Oct 2014 21:40:35 -0500 Message-ID: <3029778.sRTk01SrzP@blackbeast> User-Agent: KMail/4.13.3 (Linux/3.10.17; KDE/4.13.3; x86_64; ; ) In-Reply-To: <542B9598.5030302@gwdg.de> References: <20140930081301.55bc5629.ohartman@zedat.fu-berlin.de> <4180223.sAzr7DGzUz@blackbeast> <542B9598.5030302@gwdg.de> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Oct 2014 02:40:10 -0000 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. > > > > > > > > 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" -- Chuck