Date: Fri, 5 May 2006 06:00:35 -0500 From: "Donald J. O'Neill" <duncan.fbsd@gmail.com> To: freebsd-questions@freebsd.org Cc: Peggy Wilkins <enlil65@gmail.com> Subject: Re: Why do I have to keep doing "portsnap extract"? Message-ID: <200605050600.35936.duncan.fbsd@gmail.com> In-Reply-To: <1789c2360605042306s11d6790ctd910cdf9cf468f86@mail.gmail.com> References: <1789c2360605041440p462ada3clb8c35d17d0d3e43d@mail.gmail.com> <445ACD04.5030505@freebsd.org> <1789c2360605042306s11d6790ctd910cdf9cf468f86@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday 05 May 2006 01:06, Peggy Wilkins wrote: > On 5/4/06, Colin Percival <cperciva@freebsd.org> wrote: > > Peggy Wilkins wrote: > > > On 5/4/06, Jason Morgan <jwm-freebsd-questions@sentinelchicken.net> wrote: > > >> Did you run `extract' after your original `fetch'? > > > > > > Yes, I did; I followed the instructions exactly. I ran portsnap > > > for the first time a couple weeks ago after which I successfully > > > did a bunch of portupgrades. Then the ports tree sat there on my > > > disk untouched for a couple of weeks until I ran "portsnap fetch > > > update" today. For some reason it insisted that I needed to run > > > "extract" when as far as I can tell that shouldn't have been > > > necessary. > > > > Do you have a ".portsnap.INDEX" file in your ports tree? > > Yes; I don't know if it was there before I ran portsnap today, > though. > > -rw-r--r-- 1 root wheel 1230186 May 4 16:39 .portsnap.INDEX > > plw > _______________________________________________ Have you stopped using cvsup for updating your ports? If you do, you're going to have to use extract the next time you use portsnap. Don
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200605050600.35936.duncan.fbsd>