Date: Tue, 18 Aug 2015 16:33:25 +0000 From: Koichiro IWAO <meta@vmeta.jp> To: questions@freebsd.org Subject: freebsd-update checksum mismatch (why not resume?) Message-ID: <0000014f41a87ca2-9d19cfb6-4c46-444e-8308-6631cdea701e-000000@us-west-2.amazonses.com>
next in thread | raw e-mail | index | archive | help
Hi, Why freebsd-update does not resume previous run with same arguent? I tried to upgrade my FreeBSD system with freebsd-update. However, applying patch phase stops by checksum mismatch. See following output. I ran "freebsd-update upgrade" 5 times. Finally 5th try went smoothly. It looks each n-th run of freebsd-update fetches and patches at the beginning. What a waste of time! Refetching file with incorrect hash is enough, right? Refetching all files in order to refetch only single file with incorrect hash is waste of time and network. Why don't you implement resume in freebsd-update? Isn't it a good idea? # freebsd-update upgrade -r 10.2-RELEASE Looking up update.FreeBSD.org mirrors... none found. Fetching metadata signature for 10.1-RELEASE from update.FreeBSD.org... done. Fetching metadata index... done. Fetching 2 metadata patches.. done. Applying metadata patches... done. Inspecting system... done. The following components of FreeBSD seem to be installed: kernel/generic src/src world/base world/lib32 The following components of FreeBSD do not seem to be installed: world/doc world/games Does this look reasonable (y/n)? y Fetching metadata signature for 10.2-RELEASE from update.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.1-RELEASE for merging... done. Preparing to download files... done. Fetching 41390 patches.....<snip>..41380....41390 done. Applying patches... done. Fetching 8464 files... 0820ce82763e357f692678c6dcddd0a217a9a411888f25d999177164df8a7dd0 has incorrect hash. -- `whois vmeta.jp | nkf -w` meta <meta@vmeta.jp>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0000014f41a87ca2-9d19cfb6-4c46-444e-8308-6631cdea701e-000000>