OK, so it turns out the problem was not with Homebrew, but with cURL, which was only downloading 2 KB of whatever file I threw at it and then failing.
FUSE4X HOMEBREW UPDATE
Note: I did a brew update before running the above so I can attest to the fact that I do have the latest recipe for sshfs and that the MD5 checksum for the tarball in the recipe is correct and matches what gets downloaded from github. You can go ahead and update the recipe if you think your download is not corrupt. If it's different for your case it's likely your download is corrupt.
In my case the computed value for the download matches the value in the recipe. System "autoreconf", "-force", "-install" > cat /usr/local/Library/Formula/sshfs.rb The file to edit is /usr/local/Library/Formula/sshfs.rb. If it still complains about the hash value mismatch, you can edit the recipe and update the MD5 checksum for the file in the recipe and then install. You can remove /usr/local/Cellar/sshfs/2.4.0/sshfs_2_4_0, which is the cached tarball that Homebrew downloaded, and have Homebrew try downloading the package anew. More than likely though, if it still complains, is you've got a corrupt tarball download.
FUSE4X HOMEBREW INSTALL
If you're certain the downloaded tarball for sshfs is good can try to force Homebrew to install it with: brew install -f sshfs But if I let Homebrew try to fetch the file itself, the download ends prematurely after only a few kilobytes which corrupts the file and causes the hashes not to match. (To retry an incomplete download, remove the file above.)Įdit: If I download a package manually, and put it into /Library/Caches/Homebrew/ with the same filename that Homebrew expects, and then try to install, it works fine. I did this, and deleted the previously-downloaded package, but it doesn’t seem to have any effect: $ brew update The only answer I have found online is to do brew update beforehand. No program will install on its own-the expected hash signature never matches the actual one, for whatever reason.
0 kommentar(er)
