Date: Wed, 12 Apr 2006 11:02:15 +0400 From: "Andrew Pantyukhin" <infofarmer@gmail.com> To: "Colin Percival" <cperciva@freebsd.org> Cc: Wojciech Puchar <wojtek@tensor.3miasto.net>, freebsd-questions@freebsd.org Subject: Re: portsnap DOESN'T WORK Message-ID: <cb5206420604120002w7f5229buc9a8c94c9a0c14d6@mail.gmail.com> In-Reply-To: <443C1A4D.3050609@freebsd.org> References: <20060411202952.F59517@chylonia.3miasto.net> <443C1A4D.3050609@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4/12/06, Colin Percival <cperciva@freebsd.org> wrote: > Wojciech Puchar wrote: > > root@3miasto# portsnap fetch > > [...] > > Fetching 4 metadata files... /usr/sbin/portsnap: cannot open > > 4ad98b45a8fb7f262971491949ddd63be3fa066a31d5d09d53a9eddff3276698.gz: No > > such file or directory > > metadata is corrupt. > > > > tried cleaning /var/db/portsnap completely too. it fetched all data > > first and then got the same exactly > > > > what's wrong? > > What does "portsnap --debug fetch" report? > > Colin Percival > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.o= rg" > BTW, I didn't want to bother you, but I've had a similar problem on a very slow link. Portsnap tends to time out (in spite of the download is in progress, bytes are coming - just very slowly) and says that <something> is corrupt. I think time outs should be tuned.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?cb5206420604120002w7f5229buc9a8c94c9a0c14d6>