Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 27 Aug 2004 13:31:10 -0500
From:      "Brandon D. Valentine" <brandon@dvalentine.com>
To:        deischen@freebsd.org
Cc:        freebsd-ports@freebsd.org
Subject:   Re: portupgrade having problems bootstrapping new ports?
Message-ID:  <20040827183110.GB53788@brandon.dvalentine.com>
In-Reply-To: <Pine.GSO.4.43.0408271412320.29236-100000@sea.ntplx.net>
References:  <Pine.GSO.4.43.0408271412320.29236-100000@sea.ntplx.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Aug 27, 2004 at 02:21:48PM -0400, Daniel Eischen wrote:
> No matter what I tried, 'portupgrade -NR net/samba3' did
> nothing.  It went off and thought for a bit, then came back
> with the prompt -- no errors.  I tried net/samba (samba-2.x)
> and that worked.  After I manually built and installed
> samba3, 'portupgrade -fNR net/samba3' worked.

I have seen portupgrade behave this way in the past and everytime it
happens to me I find I have an out of date ports INDEX.  This might seem
obvious, but I infrequently find the INDEX update slipping my mind.  If
you haven't already, you might try 'portsdb -uU' on that system and then
see if you can use portupgrade to build and install those ports.

HTH,

Brandon D. Valentine
-- 
brandon@dvalentine.com                           http://www.geekpunk.net
Pseudo-Random Googlism:  summer is busiest season for emergency
                         departments



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040827183110.GB53788>