Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 27 Nov 2012 11:38:15 +0000
From:      RW <rwmaillists@googlemail.com>
To:        freebsd-questions@freebsd.org
Subject:   Re: how to correct portsnap corruption
Message-ID:  <20121127113815.24d69758@gumby.homeunix.com>
In-Reply-To: <50B4763E.6060506@qeng-ho.org>
References:  <000301cdcc63$179b3a50$46d1aef0$@shaw.ca> <50B4763E.6060506@qeng-ho.org>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Tue, 27 Nov 2012 08:13:50 +0000
Arthur Chance wrote:

> On 11/27/12 05:50, Dale Scott wrote:
> > Hi, I was running "portsnap fetch" on a remote terminal when my
> > connection failed. After connecting running portsnap again, it
> > appeared to complete correctly. However, when I run "portsnap
> > extract" I get the following error:
> >
> >
> >
> > casper# portsnap extract
> >
> > /usr/ports/.cvsignore
> >
> > /usr/ports/CHANGES
> >
> > /usr/ports/COPYRIGHT
> >
> > /usr/ports/GIDs
> >
> > /usr/ports/KNOBS
> >
> > /usr/ports/LASTCOMMIT.txt
> >
> > files/bfd9e7e5d0fff1e0c601614c35085494c8de06eb100b2fe025a6c9a226ec0e09.gz
> > not found -- snapshot corrupt.
> >
> > casper#
> >
> >
> >
> > How can I recover from this without losing any app configs I have
> > in the ports tree? (i.e. make config)
> 
> Port configs are stored in /var/db/ports/<portname>/options, not in 
> /usr/ports so are safe from any overwriting by portsnap.

In any case, it's the snapshot that needs replacing, i.e. the contents
of /var/db/portsnap.



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?20121127113815.24d69758>