Date: Sat, 17 Sep 2016 19:41:07 +0100 From: RW <rwmaillists@googlemail.com> To: freebsd-questions@freebsd.org Subject: Re: portsnap question Message-ID: <20160917194107.519a48f4@gumby.homeunix.com> In-Reply-To: <20160917140920.GA2033@e733> References: <b3664960-c54d-07f6-e766-52beed4ce45c@hiwaay.net> <20160917140920.GA2033@e733>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 17 Sep 2016 17:09:20 +0300 Aleksander Alekseev wrote: > > [root@kabini1, /etc, 8:10:30am] 353 % portsnap fetch update > > Looking up portsnap.FreeBSD.org mirrors... 7 mirrors found. > > Fetching snapshot tag from your-org.portsnap.freebsd.org... done. > > Fetching snapshot metadata... done. > > Updating from Sat Aug 27 01:19:19 MCDT 2016 to Sat Sep 17 04:21:58 > > MCDT 2016. > > Fetching 5 metadata patches... done. > > Applying metadata patches... done. > > Fetching 5 metadata files... /usr/sbin/portsnap: cannot open > > 39ffac906fafd69bfbba7c63d15dccb8ccbc8adaa755a212be13200b41f1d215.gz: > > No such file or directory > > metadata is corrupt. > > Same issue here (11.0-RC2). Must be some sort of race condition or > something in portspap since second execution of `portsnap fetch > update` always works flawlessly. It doesn't sound too serious then. Under other circumstances I'd suggest deleting everything under /var/db/portsnap/, but that allows the possibility of the portsnap MITM attack, which I don't think has been fixed yet.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160917194107.519a48f4>