10.4 release - is the binary update corrupt?

[Dr Josef Karthauser]

> On 8 Oct 2017, at 12:04, Matthew Seaman <matthew at FreeBSD.org> wrote:
> 
>> Am Sonntag, 8. Oktober 2017 schrieb Dr Josef Karthauser:
>>> Hi,
>>> 
>>> I’m having trouble upgrading a 10.3 machine to 10.4: looks like something is corrupt:
>>> 
>>> Fetching metadata signature for 10.4-RELEASE from update4.freebsd.org... done.
>>> Fetching metadata index... done.
>>> Fetching 1 metadata patches. done.
>>> Applying metadata patches... done.
>>> Fetching 1 metadata files... done.
>>> Inspecting system... done.
>>> Fetching files from 10.3-RELEASE for merging... done.
>>> Preparing to download files... done.
>>> Fetching 38573 patches.....10....20....30....40....50....60....70....80....90....100....110....120....130....140…
>>> [cut]
>>> Applying patches... done.
>>> Fetching 9266 files...
>>> gunzip: (stdin): unexpected end of file
>>> efb4027db1ae440353955aa1bcfc9c69d1cafbdb53b4bfc6584d64b1e1bfd209 has incorrect hash.
>>> 
>>> Has anyone else also seen this?
>>> 
> 
> With luck you've only got a problem with that one patch file, but if the
> corruption is much wider, then moving aside your existing
> /var/db/freebsd-update and starting again from scratch is probably a
> good idea.
> 
> If you consistently get broken patch files from whichever of the update
> servers you get directed to, that probably means that update server
> needs some TLC.  Please do report that to clusteradm at ... While waiting
> for them to sort out the problems, you can play with the 'ServerName'
> parameter in /etc/freebsd-update.conf to point yourself towards some
> other server.

I’ve upgrade from 10.1 today to 10.2, then 10.3; and only had this problem
moving to 10.4. I can’t see how a file could have become corrupt in transit
- TCP protects against that kind of thing. :)

I’ll try moving the damaged file aside and see if that fixes anything and
report back.

Cheers,
Joe