Date: Tue, 28 May 2013 01:01:43 +0300 From: Kimmo Paasiala <kpaasial@gmail.com> To: Bruce Cran <bruce@cran.org.uk> Cc: goksin.akdeniz@gmail.com, freebsd-ports@freebsd.org Subject: Re: Is latest portsnap snapshot corrupted? Message-ID: <CA%2B7WWSdgyywtTEhV7F82%2B5XiYd-H6geaxEH9-Asgx2urLUof%2Bg@mail.gmail.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 Tue, May 28, 2013 at 12:15 AM, Bruce Cran <bruce@cran.org.uk> wrote: > On 27/05/2013 22:13, G=C3=B6k=C5=9Fin 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. >> > > Is '# portsnap fetch update' not sufficient? It seemed to work here. > > -- > Bruce Cran > The portsdb tool is not part of the base system if anyone is wondering, it comes from ports-mgmt/portupgrade. Not everyone is using portupgrade so if you post any instructions like this make sure you mention the extra tools involved and what they relate to. -Kimmo
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2B7WWSdgyywtTEhV7F82%2B5XiYd-H6geaxEH9-Asgx2urLUof%2Bg>