Bug 192040 - portsnap corrupt
Summary: portsnap corrupt
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Ports Framework (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Many People
Assignee: Colin Percival
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-07-22 18:21 UTC by Tony Hain
Modified: 2015-01-06 06:58 UTC (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tony Hain 2014-07-22 18:21:08 UTC
The default portsnap server is corrupt. "portsnap fetch" shows ~4xMB, then extract terminates with a truncated gz, while "portsnap -s portsnap2 fetch" shows ~6xMB and completes the extract.
Comment 1 John Marino freebsd_committer freebsd_triage 2014-07-22 18:40:54 UTC
Colin is probably the right guy to look at this.
Comment 2 Kubilay Kocak freebsd_committer freebsd_triage 2014-07-22 23:07:50 UTC
Peter is looking after addressing service impacts due to an attack on ISC where some of our services are hosted, which may be related and was announced on developers@ yesterday
Comment 3 Tony Hain 2014-07-25 23:16:58 UTC
While the size of the portsnap now matches, I have been getting 
pkg-static: invalid chunk added
pkg: invalid chunk added
when trying to build or use /usr/ports/pkg-mgmt/pkg on a fresh 10.0 system.
Dumping /usr/ports & doing a new extract from portsnap2 has the same result.
I don't know if this is something to report to the port maintainer, or is related to the mirror problem. Systems built on the 8th don't have that problem.
Comment 4 Harrison Grundy 2015-01-06 06:58:31 UTC
This should be fixed per cperciva

Please file another PR if this recurs.