Date: Wed, 7 Nov 2007 20:39:30 -0600 From: Novembre <novembre@gmail.com> To: "Colin Percival" <cperciva@freebsd.org> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: portsnap question Message-ID: <3b47caa90711071839p427c0e9dj83acdaf262af0388@mail.gmail.com> In-Reply-To: <47326831.9000205@freebsd.org> References: <3b47caa90711071729n597054c5h7e83e08a82a91c34@mail.gmail.com> <47326831.9000205@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Nov 7, 2007 7:36 PM, Colin Percival <cperciva@freebsd.org> wrote: > Novembre wrote: > > Looking up portsnap.FreeBSD.org mirrors... 4 mirrors found. > > Fetching snapshot tag from portsnap3.FreeBSD.org... done. > > Fetching snapshot metadata... done. > > Updating from Fri Oct 5 16:39:29 CDT 2007 to Wed Nov 7 17:22:07 CST 2007. > > Fetching 4 metadata patches... done. > > Applying metadata patches... done. > > Fetching 4 metadata files... done. > > Fetching 2125 patches.....10....20....30....40....50....60....70....80....90....100....110....120....130....140....150....160....170....180....190....200....210....220....230....240....250....260....270....280....290....300....310....320....330....340....350....360....370....380....390... > > done. > > Applying patches... done. > > Fetching 1882 new ports or files... done. > > > > I'm wondering why it says 'fetching 2125 patches...' and then > > downloading only 396 of them. > > Probably there was either a glitch on the mirror or you're behind a > "transparent" HTTP proxy which misbehaved. Portsnap falls back to > downloading complete files if it can't fetch or apply patches (which > is why the 1882 new ports or files is such a large number), so all > this means is that a bit more bandwidth was used than necessary. > > > I have not run 'portsnap update' yet since I was afraid it might ruin > > my ports tree. Is there anyway to force portsnap fetch a new snapshot > > without telling me 'no updates needed'? > > Don't worry, you can run `portsnap update` safely. > > Not relevant in this case, but for the benefit of the archives: In the > rare case where portsnap's locally stored snapshot becomes corrupt (most > often as a result of filesystem not being unmounted cleanly), deleting > everything inside /var/db/portsnap will result in portsnap downloading a > complete new snapshot the next time `portsnap fetch` is run. > > Colin Percival > > Thanks for the reply. I read the man page for portsnap and realized that it stores the snapshots in /var/db/portsnap and wanted to delete everything there and run 'portsnap fetch' again, but decided to post a question and ask first (hoping that there's a shortcut). It's good to hear that nothing went wrong...I'll run 'portsnap update' then.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3b47caa90711071839p427c0e9dj83acdaf262af0388>