Date: Thu, 30 Apr 2020 19:54:53 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 246066] Portsnap continuously fails with "snapshot corrupt" Message-ID: <bug-246066-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D246066 Bug ID: 246066 Summary: Portsnap continuously fails with "snapshot corrupt" Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: doctorwhoguy@gmail.com I've run "rm -rf /var/db/portsnap/*" and "rm -rf /usr/ports" to start with a clean slate. Then I ran "portsnap fetch extract". The extraction always fai= ls at the same point: ... /usr/ports/devel/py-oslo.versionedobjects/ /usr/ports/devel/py-oslo.versionedobjects1/ /usr/ports/devel/py-oslo.vmware/ /usr/ports/devel/py-oslo.vmware2/ files/472400e8914a19db7ad90d65cb635af1cbf07292271ea6b2e68801de91a6186b.gz n= ot found -- snapshot corrupt. I've had this "snapshot corrupt" issue several times in the past few months, but usually deleting portsnap's database and the ports tree then refetching= and extracting the snapshot resolves it (at least temporarily), but I have been unable to resolve it with the usual method for the past 2 or 3 days now. I tried pinging ec2-eu-west-1.portsnap.freebsd.org, sourcefire.portsnap.freebsd.org, your-org.portsnap.freebsd.org, ec2-ap-southeast-2.portsnap.freebsd.org, ec2-ap-northeast-1.portsnap.freebsd.org, and ec2-sa-east-1.portsnap.freebsd= .org to see which one was the fastest, but the your-org site was the only one th= at even responded (this is the one which portsnap uses automatically if I don't specify one). I don't know if this is why portsnap defaults to your-org, bu= t I do seem to be able to use other sites if I specify them on the command line. However, snapshots from other sites still fail (users in the forums who have had the "corrupt snapshot" issue sometimes claim that using a different ser= ver resolves the issue, but it didn't work for me). --=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-246066-7788>