From owner-freebsd-ports@FreeBSD.ORG Wed Sep 8 22:15:39 2010 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EE59910656BD for ; Wed, 8 Sep 2010 22:15:39 +0000 (UTC) (envelope-from freebsd-ports.user@seibercom.net) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 929968FC13 for ; Wed, 8 Sep 2010 22:15:39 +0000 (UTC) Received: by gwb15 with SMTP id 15so91513gwb.13 for ; Wed, 08 Sep 2010 15:15:38 -0700 (PDT) Received: by 10.101.33.12 with SMTP id l12mr439175anj.175.1283984137742; Wed, 08 Sep 2010 15:15:37 -0700 (PDT) Received: from scorpio.seibercom.net (cpe-071-070-147-230.nc.res.rr.com [71.70.147.230]) by mx.google.com with ESMTPS id r20sm629583anf.27.2010.09.08.15.15.36 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 08 Sep 2010 15:15:37 -0700 (PDT) Received: from seibercom.net (zeus [192.168.1.1]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: freebsd-ports.user@scorpio.seibercom.net) by scorpio.seibercom.net (Postfix) with ESMTPSA id CBB2DE54857 for ; Wed, 8 Sep 2010 18:15:35 -0400 (EDT) Date: Wed, 8 Sep 2010 18:15:35 -0400 From: Jerry To: freebsd-ports@freebsd.org Message-ID: <20100908181535.0bb7d329@seibercom.net> In-Reply-To: <4C88030C.1030505@telenix.org> References: <4C75C308.5060506@telenix.org> <4C75F8F9.3060704@DataIX.net> <4C88030C.1030505@telenix.org> Organization: seibercom.net X-Mailer: Claws Mail 3.7.6 (GTK+ 2.20.1; amd64-portbld-freebsd8.1) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAG1BMVEX3/uPVnZf2/v9ejGkqHB74++H///+cHCT3m6cgqYvfAAACbElEQVQ4jWXTQW/bIBQAYJLJuRMn8TVCss9zTdrrXJ6bHe1Ej/bossF9EpJ3nbapf3sP8JxOQ4qV8OU9HvjBROWcYNlKHtxlQ1/huBaOBiMwQtgHhbokMLIT76Acps5hvy61+6WsjkCZzNEW0+fcQ7Nl5uoPCegjjjhN5/MEABd89k9hXkQoX6cwPIDKCt8tYG5wpmdrxAyuolTPqpiVoEpVCWvl6e00RAD4JBJQnO4lvv0O4Cnd3WUGevYNFohxFYAy7jCCtW39LaQK8BgDAgiHVinVJlCiFKlcqgEHfwb1EuG+DwFGMO3oCIuJIEYoa8KJECBB+UBldgm0MQmEGz7GQr8XYRPKzYNO1zZ8mgdAu4BG5Ke/4KFboM8458UScViAAvYD93OAsu+Bc3zxCU7ZAjT74+dQv9K7oO0d1wuscop48Pc50O5bcVwgGzh/mXzaizJuAWERh8k3eaxKmxu4kV1p2XOEg3i3c8M+EKR93P0D1KATpC55vMHaGqFf5f/AwhlrhHgg8DTezopt6I3o3Qx4q4q6YaPxK8RxcClXeFGhTTS++QR6TS/oBs7l4WhzuNMubZG6hIBkF4qqZVdWczIqSrjKVF/i4o26IP2oElBGFy5CXKSnf6UWDTC6zKSqoAvzsakjjBvdzLKnmxdhY8eRsX7VSCUBdgD1hVJpx6y2OOS1DNDILYmqdWUJ+oHvd0rRvAqX5kpxQMR6yxHzPV6VlPFyWE7LKc36keNQI64gLP8Ybgtmg+zYuBl4fuI8VqW2RqDGE8Uzu7GxGa803whDdxx3bSZbRhfQUSxvmnpLZWpRFqHz7v8AvsBe0S1zv9UAAAAASUVORK5CYII= Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: Re: portmanager endlessly looping in x11 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-ports@freebsd.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Sep 2010 22:15:40 -0000 On Wed, 08 Sep 2010 17:41:32 -0400 Chuck Robey articulated: > On 08/26/10 01:17, jhell wrote: > > On 08/25/2010 21:27, Chuck Robey wrote: > >> I have an interesting thing here: I seem to have found an endless > >> loop in portmanager. It's *entirely* possible that I'm myself > >> causing this, so I'll explain, and if you can come up with any > >> hints, I'll be happy to test them, because I really do like using > >> portmanager. > >> > > > > > CC: of ports-mgmt/portmanager is a good start. > > Maybe He/She can give you some insight of the working of > > portmanager. I am not sure how portmanager keeps the package > > database up to date but sometimes dependencies can get messed up in > > the database that can cause a loop and if not handled correctly by > > the upgrade process can cause a lot of grief. In portmaster you > > could be using --check-depends and in portupgrade you could use > > -Ffu but you don't seem to be using any of the suggested ports-mgmt > > upgrade utilities so good luck. ``emphasis on portmaster'' -- > > written by dougb@, so you know it works!. > > The problem I saw, I'm pretty sure is caused by a discrepancy (in > portmanager) between how deeply it looks for dependencies versus how > deeply it looks it looks to decide to actually rebuild those > discovered dependencies. Merely noting the need to rebuild seems not > to be the same thing as actually doing it. It found things maybe 3 > levels deep, but if it's less than 2 levels down, it won't rebuild > it, it'll merely realize that it *should* do it. I switched to using > portmaster (this looks alike, I'm making no mistake tho, moved from > portmanager to portmaster) which doesn't seem to have this uneveness, > so while it takes a whole lot longer to work than portmanager (it > uses slow but sure shell utils for it's databases) it really does a > far more reliable job of things. You could get to rely on it. > > It sure took me a good while to track down the reasons that > portmanager was fixing on, in deciding that something was out of > date, and the frustration was sufficient to cause me to forgive the > way that portmaster is much more slow. One really big irritation was > how portmanager would rebuild something completely successfully 3 > times, but since it would fail its dependency scans, it never would > recognize that any of those looping apps had been rebuilt. Very > puzzling, until I realized about the dependency problems. > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports To > unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" Portmanager did have a nasty bug that involved looping. It was fixed ages ago though. Are you running the latest version; i.e., "0.4.1_9" on your system? Run "portmanager -v" to confirm. Without the '-p' option, portmanager only looks 1 level deep. with the '-p' option, it will search the entire dependency chain. I always use the '-p' option and never experience any problems described by you. -- Jerry ✌ FreeBSD-Ports.user@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________