From owner-freebsd-ports@FreeBSD.ORG Thu Jun 26 20:06:21 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 07558106566C for ; Thu, 26 Jun 2008 20:06:21 +0000 (UTC) (envelope-from JoshHanson@capriomgt.com) Received: from mail.capriomgt.com (mail.capriomgt.com [74.9.81.233]) by mx1.freebsd.org (Postfix) with ESMTP id B1AF08FC24 for ; Thu, 26 Jun 2008 20:06:20 +0000 (UTC) (envelope-from JoshHanson@capriomgt.com) X-MimeOLE: Produced By Microsoft Exchange V6.5 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable x-cr-puzzleid: {076C7F3D-D257-4F5C-A492-909186B58B74} Content-class: urn:content-classes:message x-cr-hashedpuzzle: ABRB BC/e Bk6L CbJy CqHI EG2O FzgZ GSbt Gc4x Gq8u HfIB IujJ JPwT J26a K1rg LKey; 1; ZgByAGUAZQBiAHMAZAAtAHAAbwByAHQAcwBAAGYAcgBlAGUAYgBzAGQALgBvAHIAZwA=; Sosha1_v1; 7; {076C7F3D-D257-4F5C-A492-909186B58B74}; agBvAHMAaABoAGEAbgBzAG8AbgBAAGMAYQBwAHIAaQBvAG0AZwB0AC4AYwBvAG0A; Thu, 26 Jun 2008 19:54:11 GMT; UABvAHIAdABtAGEAbgBhAGcAZQByACAAcwB0AHUAYwBrACAAaQBuACAAYQAgAGwAbwBvAHAA Date: Thu, 26 Jun 2008 15:54:11 -0400 Message-ID: <7E88CE27089FBA4DAF28262B761808863FD6DB@MAIL01.caprio.corp> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Portmanager stuck in a loop Thread-Index: AcjXxmdprQr23mJLSeGUIxPqhnK93w== From: "Josh Hanson" To: Subject: 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: Thu, 26 Jun 2008 20:06:21 -0000 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". 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: =20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 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 =20 OLD xorg-server-1.4.2,1 /x11-servers/xorg-server =20 Thu Jun 26 01:05:23 2008 options changed so returning xorg-server-1.4_4,1 =20 /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 =20 OLD xorg-server-1.4.2,1 /x11-servers/xorg-server =20 Thu Jun 26 01:05:36 2008 options changed so returning xorg-server-1.4_4,1 =20 /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 =20 OLD xorg-server-1.4.2,1 /x11-servers/xorg-server =20 Thu Jun 26 01:05:49 2008 options changed so returning xorg-server-1.4_4,1 =20 /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 =20 OLD xorg-server-1.4.2,1 /x11-servers/xorg-server =20 Thu Jun 26 01:06:01 2008 options changed so returning xorg-server-1.4_4,1 =20 /x11-servers/xorg-server to out of date pool