Date: Fri, 27 Jun 2008 17:21:21 +0100 From: RW <fbsd06@mlists.homeunix.com> To: freebsd-ports@freebsd.org Subject: Re: Portmanager stuck in a loop Message-ID: <20080627172121.453ceefc@gumby.homeunix.com.> In-Reply-To: <1214578557.63129.14.camel@squirrel.corp.cox.com> References: <7E88CE27089FBA4DAF28262B761808863FD6DB@MAIL01.caprio.corp> <1214577239.63129.7.camel@squirrel.corp.cox.com> <7E88CE27089FBA4DAF28262B761808863FD6FF@MAIL01.caprio.corp> <1214578557.63129.14.camel@squirrel.corp.cox.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 27 Jun 2008 10:55:57 -0400 Robert Noland <rnoland@2hip.net> wrote: > 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? If he wasn't then, presumably portmanager wouldn't detect a modification of options files. It sounds as if portmanager itself might not be at the root of this and it's just reacting to a problem with the ports, whereby one or more of them is spuriously bringing-up the options screen. I'd go to /var/db/ports and remove any directories that match the problem ports.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080627172121.453ceefc>