Date: Thu, 26 Jun 2008 15:54:11 -0400 From: "Josh Hanson" <JoshHanson@capriomgt.com> To: <freebsd-ports@freebsd.org> Subject: Portmanager stuck in a loop Message-ID: <7E88CE27089FBA4DAF28262B761808863FD6DB@MAIL01.caprio.corp>
next in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7E88CE27089FBA4DAF28262B761808863FD6DB>