Date: Tue, 28 May 2013 00:15:55 +0100 From: RW <rwmaillists@googlemail.com> To: ports@freebsd.org Subject: Re: Is latest portsnap snapshot corrupted? Message-ID: <20130528001555.1f14c42c@gumby.homeunix.com> In-Reply-To: <51A3CCF1.2080706@cran.org.uk> References: <1369665048044-5815448.post@n5.nabble.com> <CAA96eVvU0bU7-RVZE9RviZOrd05qC8q0aRLsJJ7AT=Qk_s6ecQ@mail.gmail.com> <1369679542074-5815520.post@n5.nabble.com> <20130528001340.393804429748c30d19c02ce3@gmail.com> <51A3CCF1.2080706@cran.org.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 27 May 2013 22:15:29 +0100 Bruce Cran wrote: > On 27/05/2013 22:13, G=F6k=FEin Akdeniz wrote: > > Ia am not a dev, but portstree snapshot is fixed. Simply run > > > > '# portsnap fetch extract && portsdb -u' > > > > and you will get a fresh snapshot of ports tree. > > >=20 > Is '# portsnap fetch update' not sufficient? It seemed to work here. >=20 Extract shouldn't be needed, the problem was in the snapshot, not the portstree.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130528001555.1f14c42c>