>>> # pkg update -f >>> Updating FreeBSD repository catalogue... >>> Fetching meta.txz: 100% 944 B 0.9kB/s 00:01 >>> Fetching packagesite.txz: 100% 6 MiB 2.2MB/s 00:03 >>> Processing entries: 100% >>> FreeBSD repository update completed. 32029 packages processed. >>> All repositories are up to date. >>> # freebsd-update fetch >>> Looking up update.FreeBSD.org mirrors... 2 mirrors found. >>> Fetching metadata signature for 11.1-RELEASE from update5.freebsd.org... >>> done. >>> Fetching metadata index... done. >>> Inspecting system... done. >>> Preparing to download files... done. >>> Fetching 2 patches.. done. >>> Applying patches... done. >>> Fetching 2 files... >>> 104969ef03336523729ea1df2547267441a13cb040c778e971b74103e88dbc77 has >>> incorrect hash. >> >> this is now over two weeks. still multiple systems on public net, v4 >> and dual stack. > > The other brute-force approach is: > > rm -rf /var/db/freebsd-update/*
work0.psg.com:/root# rm -rf /var/db/freebsd-update/* work0.psg.com:/root# freebsd-update --not-running-from-cron fetch Looking up update.FreeBSD.org mirrors... 2 mirrors found. Fetching public key from update5.freebsd.org... done. Fetching metadata signature for 11.1-RELEASE from update5.freebsd.org... done. Fetching metadata index... done. Fetching 2 metadata files... done. Inspecting system... done. Preparing to download files... done. Fetching 66 patches.....10....20....30....40....50....60... done. Applying patches... done. Fetching 3 files... 104969ef03336523729ea1df2547267441a13cb040c778e971b74103e88dbc77 has incorrect hash. _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[email protected]"
