Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 4 Nov 2019 18:48:12 +0200
From:      Christos Chatzaras <chris@cretaforce.gr>
To:        freebsd-questions@freebsd.org
Subject:   Re: Portsnap metadata corruption
Message-ID:  <52BDAEAB-2F44-44DE-B6D5-E0939EB6A1D3@cretaforce.gr>
In-Reply-To: <20191104164328.11a35df1@gumby.homeunix.com>
References:  <CANR6Wa4BTq2TmEzCFORsgvrhy4-jSz5yb8zELnY0Q6GF%2BUWqvw@mail.gmail.com> <20191104164328.11a35df1@gumby.homeunix.com>

next in thread | previous in thread | raw e-mail | index | archive | help


> On 4 Nov 2019, at 18:43, RW via freebsd-questions =
<freebsd-questions@freebsd.org> wrote:
>=20
> On Mon, 4 Nov 2019 09:12:17 +0000
> Arthur Barlow wrote:
>=20
>> When trying to fetch the latest update for portsnap today I got the
>> following message:
>>=20
>> Fetching 4 metadata files... /usr/sbin/portsnap: cannot open
>> adce305cc15ca8f18dc8ca52e8c91a04ac3f49638d405e5f96abdb01fd70f501.gz:
>> No such file or directory
>> metadata is corrupt.
>=20
> You can delete the contents of /var/db/portsnap/ and it will be
> recreated by downloading a new snapshot tarball.
>=20
> Any information about the ports directory is in the ports directory
> itself, so you don't need to delete it or do a new 'extract'.


Had the same issue today. I will try again tomorrow.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52BDAEAB-2F44-44DE-B6D5-E0939EB6A1D3>