Date: Tue, 13 Apr 2021 17:53:22 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 255029] portsnap fetch update corruption Message-ID: <bug-255029-7788-wo7Qd1QxcT@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-255029-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-255029-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D255029 --- Comment #6 from Ed Maste <emaste@freebsd.org> --- (In reply to jakub_lach from comment #4) I suspect the portsnap server is just overloaded due to the large size of t= he update and the large number of clients updating after the outage. I was successfully able to `portsnap fetch` and `portsnap update` on a test machine just now. It did take a while to run. root@freebsd-s-1vcpu-1gb-tor1-01:~ # portsnap fetch Looking up portsnap.FreeBSD.org mirrors... 4 mirrors found. Fetching snapshot tag from ipv4.aws.portsnap.freebsd.org... done. Fetching snapshot metadata... done. Updating from Tue Apr 13 15:24:58 UTC 2021 to Tue Apr 13 16:29:40 UTC 2021. Fetching 5 metadata patches. done. Applying metadata patches... done. Fetching 5 metadata files...=20 done. Fetching 18 patches.=20 (18/18) 100.00% done.=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 done. Applying patches...=20 done. Fetching 0 new ports or files... done. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-255029-7788-wo7Qd1QxcT>