From owner-freebsd-ports@FreeBSD.ORG Fri Jun 27 14:34:11 2008 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 71BCF1065682 for ; Fri, 27 Jun 2008 14:34:11 +0000 (UTC) (envelope-from rnoland@2hip.net) Received: from gizmo.2hip.net (gizmo.2hip.net [64.74.207.195]) by mx1.freebsd.org (Postfix) with ESMTP id 451878FC15 for ; Fri, 27 Jun 2008 14:34:10 +0000 (UTC) (envelope-from rnoland@2hip.net) Received: from [192.168.166.46] ([68.0.14.34]) (authenticated bits=0) by gizmo.2hip.net (8.13.8/8.13.8) with ESMTP id m5REY4M0084777 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 27 Jun 2008 10:34:04 -0400 (EDT) (envelope-from rnoland@2hip.net) From: Robert Noland To: Josh Hanson In-Reply-To: <7E88CE27089FBA4DAF28262B761808863FD6DB@MAIL01.caprio.corp> References: <7E88CE27089FBA4DAF28262B761808863FD6DB@MAIL01.caprio.corp> Content-Type: text/plain Organization: 2Hip Networks Date: Fri, 27 Jun 2008 10:33:59 -0400 Message-Id: <1214577239.63129.7.camel@squirrel.corp.cox.com> Mime-Version: 1.0 X-Mailer: Evolution 2.22.1.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-0.6 required=5.0 tests=BAYES_00,RCVD_IN_SORBS_DUL autolearn=no version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on gizmo.2hip.net Cc: freebsd-ports@freebsd.org Subject: Re: Portmanager stuck in a loop X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jun 2008 14:34:11 -0000 On Thu, 2008-06-26 at 15:54 -0400, Josh Hanson wrote: > Hi, > > I'm setting up a fresh installation of freebsd, and portmanager keeps > getting stuck in a loop while trying to upgrade ports. > > I ran "portmanager -u -l" with several dozen ports to upgrade. It seemed > to successfully upgrade quite a few ports; for several ports, it brought > up the menu with configuration options, and I always just left the > defaults. > > Eventually, I noticed it brought up some familiar-looking configuration > screens. Soon, it was simply cycling through the same 3 ports' > configuration screens repeatedly. The log shows messages for each port > (repeatedly) saying, "options changed so returning [port name] to out of > date pool". Some of the port system optimizations caused a situation where a port can be left dependent on multiple versions of the same origin. (Through recursive dependencies) As a result, portmanager will continue to try and update the port. I need to do something of an overhaul of portmanager, but other projects are consuming most of my free time lately. If you use the -p (pristine) flag, portmanager will avoid this issue by ensuring that all ports are updated in order, no matter how deep in the dependency tree. FWIW, my usage of portmanager is "portmanager -u -p -l -y". robert. > I tried manually installing those 3 ports; each said it was already > installed, so I did a "make uninstall" then "make install" for each one, > and ran portmanager again. It continued to run just fine, upgrading more > ports, then hit the same sort of loop with another set of ports. I > upgraded those manually and tried again; each time I installed some > ports manually, portmanager would get stuck repeating one or more ports. > > Background: I had just done a full install from the freebsd CDs, > including every standard package except the source code. I then ran > portsnap, then installed both portupgrade and portmanager, but after a > bit of reading decided to use portmanager. Portmanager listed several > dozen installed ports with updates available. When I ran it, I > encountered the above issues. > > An excerpt from the most recent (odd-looking) log file is below. Notice > that it's repeating the same port over and over. > > PS: I'm fairly new to FreeBSD, so if I'm missing something obvious or > asking this question to the wrong place, please let me know. (Though, > even if I'm doing something wrong, there seems to be a bug in > portmanager, which is clearly not exhibiting the intended behavior.) > > -- Josh > > > Log file follows: > > ======================================================================== > portmanager 0.4.1_9 > FreeBSD noc.caprio.corp 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24 > 19:59:52 UTC 2008 > root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 > ------------------------------------------------------------------------ > autoConflicts 0 autoMoved 0 > backUp 0 buildDependsAreLeaves 0 > forced 0 interactive 0 > log 1 pmMode 0 > pristine 0 resume 0 > ------------------------------------------------------------------------ > Thu Jun 26 01:04:38 2008 > xorg-server-1.4_4,1 /x11-servers/xorg-server > OLD xorg-server-1.4.2,1 > /x11-servers/xorg-server > > Thu Jun 26 01:05:23 2008 > options changed so returning xorg-server-1.4_4,1 > /x11-servers/xorg-server to out of date pool > > > Thu Jun 26 01:05:31 2008 > xorg-server-1.4_4,1 /x11-servers/xorg-server > OLD xorg-server-1.4.2,1 > /x11-servers/xorg-server > > Thu Jun 26 01:05:36 2008 > options changed so returning xorg-server-1.4_4,1 > /x11-servers/xorg-server to out of date pool > > > Thu Jun 26 01:05:44 2008 > xorg-server-1.4_4,1 /x11-servers/xorg-server > OLD xorg-server-1.4.2,1 > /x11-servers/xorg-server > > Thu Jun 26 01:05:49 2008 > options changed so returning xorg-server-1.4_4,1 > /x11-servers/xorg-server to out of date pool > > > Thu Jun 26 01:05:57 2008 > xorg-server-1.4_4,1 /x11-servers/xorg-server > OLD xorg-server-1.4.2,1 > /x11-servers/xorg-server > > Thu Jun 26 01:06:01 2008 > options changed so returning xorg-server-1.4_4,1 > /x11-servers/xorg-server to out of date pool > > > _______________________________________________ > 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" -- Robert Noland 2Hip Networks