Resolution: Portmanager stuck in a loop

Josh Hanson JoshHanson at capriomgt.com
Mon Jun 30 16:25:36 UTC 2008


After some very helpful further discussions with Robert, I tried running
"portmanger -u -p -l -y" to re-build everything, with no success.
Further digging established that my pkg_info database was very confused.
(For example, pkg_info reported that cdrtools is required by xorg-server
and lots of x drivers, which it clearly is not.)

How it got that bad on such a fresh system is a mystery. I don't know
what I could have done to mess it up.

On a whim, I tried running "pkgdb -F" and "pkgdb -fU", but it didn't
make anything better.

Robert suggested that I run pkg_delete -a to start from scratch. I ran
it as an experiment, and it looks like it'd probably work, but as long
as I'm starting from scratch I might as well go all out and reinstall
FreeBSD. I don't yet have any data on this system, so I literally have
nothing to lose, and who knows what else I may have screwed up along the
way?  :)


-----Original Message-----
From: Robert Noland [mailto:rnoland at 2hip.net] 
Sent: Friday, June 27, 2008 10:56 AM
To: Josh Hanson
Cc: freebsd-ports at freebsd.org
Subject: RE: Portmanager stuck in a loop

On Fri, 2008-06-27 at 10:46 -0400, Josh Hanson wrote:
> Ok, so I tried running "portmanager -u -p -l -y".
> 
> It built a lot of ports, then got stuck again on xorg-server over and
> over. The log file looks the same as my first post.

Is the options screen being presented repeatedly?  If so, the options
are corrupt and/or not being stored properly.  The dialog box should
only be shown once and use the stored options after that.  You are
running as a user with permission to update /var/db/ports?

robert.

> -- Josh
> 
> 
> -----Original Message-----
> From: Robert Noland [mailto:rnoland at 2hip.net] 
> Sent: Friday, June 27, 2008 10:34 AM
> To: Josh Hanson
> Cc: freebsd-ports at freebsd.org
> Subject: Re: Portmanager stuck in a loop
> 
> 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 at 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 at freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> > To unsubscribe, send any mail to
> "freebsd-ports-unsubscribe at freebsd.org"
-- 
Robert Noland <rnoland at 2hip.net>
2Hip Networks



More information about the freebsd-ports mailing list