Date: Sun, 8 Oct 2017 12:04:25 +0100 From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-stable@freebsd.org Subject: Re: 10.4 release - is the binary update corrupt? Message-ID: <17d76f7d-4b9a-6a3e-ffae-ee3c2ffd27b0@FreeBSD.org> In-Reply-To: <201710081227.35629.dr.klepp@gmx.at> References: <B3C507A4-2955-465C-A355-C38B22569843@truespeed.com> <201710081227.35629.dr.klepp@gmx.at>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --d5iJuR7deWFLe082wJvePQT4f1kpSgT8O Content-Type: multipart/mixed; boundary="IdsBkijSIViNxNIJwghnXVeVhGehqRlPd"; protected-headers="v1" From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-stable@freebsd.org Message-ID: <17d76f7d-4b9a-6a3e-ffae-ee3c2ffd27b0@FreeBSD.org> Subject: Re: 10.4 release - is the binary update corrupt? References: <B3C507A4-2955-465C-A355-C38B22569843@truespeed.com> <201710081227.35629.dr.klepp@gmx.at> In-Reply-To: <201710081227.35629.dr.klepp@gmx.at> --IdsBkijSIViNxNIJwghnXVeVhGehqRlPd Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: quoted-printable On 08/10/2017 11:27, Dr. Nikolaus Klepp wrote: > Hi! >=20 > My notes suggest for this case: >=20 > pkg clean # cleans /var/cache/pkg/ > rm -rf /var/cache/pkg/* # just remove it all > pkg update -f # forces update of repository catalog > rm /var/db/pkg/repo-*.sqlite # removes all remote repository catalogs > pkg bootstrap -f # forces reinstall of pkg >=20 > Do NOT delete /var/db/pkg/local.sqlite! It contains the database with y= our installed packages. If you remove it the system will think you have n= othing installed.=20 >=20 > Nik >=20 > Am Sonntag, 8. Oktober 2017 schrieb Dr Josef Karthauser: >> Hi, >> >> I=E2=80=99m having trouble upgrading a 10.3 machine to 10.4: looks lik= e something is corrupt: >> >> Fetching metadata signature for 10.4-RELEASE from update4.freebsd.org.= =2E. 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....8= 0....90....100....110....120....130....140=E2=80=A6 >> [cut] >> Applying patches... done. >> Fetching 9266 files... >> gunzip: (stdin): unexpected end of file >> efb4027db1ae440353955aa1bcfc9c69d1cafbdb53b4bfc6584d64b1e1bfd209 has i= ncorrect hash. >> >> Has anyone else also seen this? >> >> Cheers, >> Joe >> =E2=80=94=20 >> Dr Josef Karthauser >> Chief Technical Officer >> (01225) 300371 / (07703) 596893 >> www.truespeed.com <http://www.truespeed.com/>; >> / theTRUESPEED <http://www.facebook.com/theTRUESPEED>=20 >> @theTRUESPEED <https://twitter.com/thetruespeed>; >> =20 >> This email contains TrueSpeed information, which may be privileged or = confidential. It's meant only for the individual(s) or entity named above= =2E If you're not the intended recipient, note that disclosing, copying, = distributing or using this information is prohibited. If you've received = this email in error, please let me know immediately on the email address = above. Thank you. >> We monitor our email system, and may record your emails. How exactly does blowing away your package cache or destroying your package DB help with sorting out freebsd-update(8)? That is fixing the wrong problem... To answer the OPs actual query -- yes, something is wrong with at least one of the patches you have downloaded with freebsd-update(8). You should be able to find that broken patch file by name somewhere under /var/db/freebsd-update -- simply removing that patch file and trying again with 'freebsd-update fetch' _should_ get you an uncorrupted copy of that particular patch. In principle you can check all the patches for correctness as the patch filename is the SHA hash of the contents, although you'll have to work out exactly which SHA variant is being used, and whether the checksum has been calculated on the compressed patch as downloaded or on the de-compressed content. 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@... 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. Cheers, Matthew --IdsBkijSIViNxNIJwghnXVeVhGehqRlPd-- --d5iJuR7deWFLe082wJvePQT4f1kpSgT8O Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQJ8BAEBCgBmBQJZ2gZBXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkATcWwQAJQN106BUNmViF1SB277/sUN pafmjaeKAJpsDvcogmuqyDe893gY6p2LX/3/+7+zlttGQmsqbdK0IesF4+Yo5j20 iXZWdd/Yfu5W9buneciKnv3M5i0AeGr7nMqYn0xpIdSmMIzw1FYITrJRXfaWBQOm qxu5wFTdPfM9pAwW6zUdvCs3biHpwP/IXbq8U+EYg1nfOknKwXFif49paK+tYPa0 j6i6UENfWSJRgO+lDoPduPQ+/0+mSZr0c5UrvmW5/kDfV/4YA1vua1fsPq2FHgTx fsqVdyU4MUhjuwYBcEmkKDfraFjxANDdcMjKEBFPNI8M4bCmMp9bbEvG66CLPQ0E ZVNKFC2j6aXjv0aJIpuNUfZswii3qS02LUK6Nz14aMRBJHVoN/36YmA7d4Hdzo65 f6P9eQaqd49Huh+shToZcMJniunB6Ul1FMk8w4Sj7osKRhjMVxyPLH1+yV3JCoky uqAaaMrrfQfQoatihecU3wPy1IYCHJL+I7/tQraDokBKPgCeM+OvjmhkY3IjT/7r FcKq5H5YmRn767evbL2C0gMr6Wufi0Z/FyTrn78UFUhnkYfw+DRHmkL7DrCXG6FM g0mjC/aEkv5L/7J53fMgZPsH2dNubWv2v/ambjhQ+oLNwVigtK+pSL+HNtWwfd1M JbbAL7CagJxv/bBWmamE =7Rxe -----END PGP SIGNATURE----- --d5iJuR7deWFLe082wJvePQT4f1kpSgT8O--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?17d76f7d-4b9a-6a3e-ffae-ee3c2ffd27b0>