net/zsync: Update 0.6.3 => 0.6.6, take maintainershipHEADmain

Change in 0.6.6
- Support and generate zsync 0.8 control files.
  - Support MD5 and SHA-224 block checksums.
  - Support SHA-256 file hash.
- Use OpenSSL for cryptgraphic digests.

Changes in 0.6.5
- Fix an incompatibility between zsync and the RFC7233 rules for
  multipart/byteranges. zsync was written to RFC2046 a long time ago,
  now obsolete; responses from newer HTTP servers following the newer
  standard could cause zsync to fail to parse the response. zsync also
  was not treating failing to find the MIME boundary as a hard error and
  retrying indefinitely; changed to report this as an error.

Changes in 0.6.4
- Support for looking inside gzip files is deprecated; all options
  related to compressed files are correspondingly deprecated except -Z.
  Gzip files are not commonly used for large downloads as they were 20
  years ago. Supporting looking inside gzip files was a specific case
  that required a lot of extra code, and greatly increases the potential
  surface area for bugs.
  zsync supports all files that are rsyncable, without needing any
  specific support for any file format or encoding. gzip files are still
  and always be supported if they were compressed with `--rsyncable`, so
  use that when compressing if you want to allow incremental updating.
  If you are hosting gzip downloads that should be incrementally
  updatable with zsync, for compatibility with future releases you
  should ensure that the gzip file is compressed with --rsyncable and
  run zsyncmake with -Z when creating the zsync control file.
- More tuning to fix some cases of poor performance scanning local data
  due to bad checksum distribution.

- Switch to https in MASTER_SITES and WWW.

PR:		297646
Sponsored by:	UNIS Labs
Co-authored-by:	Vladimir Druzenko <vvd@FreeBSD.org>

0 files changed, 0 insertions, 0 deletions