Date: Sat, 28 Aug 2004 18:29:20 -0400 (EDT) From: Daniel Eischen <deischen@freebsd.org> To: Michael Nottebrock <michaelnottebrock@gmx.net> Cc: freebsd-ports@freebsd.org Subject: Re: portupgrade having problems bootstrapping new ports? Message-ID: <Pine.GSO.4.43.0408281823500.6036-100000@sea.ntplx.net> In-Reply-To: <200408282140.01336.michaelnottebrock@gmx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 28 Aug 2004, Michael Nottebrock wrote: > On Friday 27 August 2004 20:31, Brandon D. Valentine wrote: > > 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. > > At the moment, you're getting an outdated INDEX with every cvsup. I recently > raised this issue on another mailing list - hopefully it will be resolved > soon. Yes, that was the problem. I had expected the INDEX to be relatively up-to-date. I had also thought samba3 had been around for quite some time and it didn't occur to me that it wouldn't be in the index. Hmm, I just realized it was samba-devel prior to samba3. -- Dan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.43.0408281823500.6036-100000>