You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
...
==> Installing wine dependency: libusb
==> Downloading https://github.com/libusb/libusb/releases/download/v1.0.20/libus
==> Downloading from https://github-cloud.s3.amazonaws.com/releases/15120676/80d
######################################################################## 100,0%
==> ./configure --prefix=/usr/local/Cellar/libusb/1.0.20
==> make install
🍺 /usr/local/Cellar/libusb/1.0.20: 27 files, 666.2K, built in 20 seconds
==> Installing wine dependency: libusb-compat
==> Downloading https://downloads.sourceforge.net/project/libusb/libusb-compat-0
==> Downloading from http://downloads.sourceforge.net/#!/project/libusb/libusb-c
######################################################################## 100,0%
Error: SHA256 mismatch
Expected: 404ef4b6b324be79ac1bfb3d839eac860fbc929e6acb1ef88793a6ea328bc55a
Actual: 818a4b8bbcb50878a8b1b9f71b4274d242ab46bf860c74676e98dec1d0248821
Archive: /Users/sam/Library/Caches/Homebrew/libusb-compat-0.1.5.tar.bz2
To retry an incomplete download, remove the file above.
Tried to install libusb-compat before installing wine. It's succeeded. But then brew still tries to install it during wine installation.
The text was updated successfully, but these errors were encountered:
ipotseluev-softheme
changed the title
SHA256 mismatch on libusb-compat during wine installation
SHA256 mismatch on libusb-compat during wine installation on 10.11.5
Jul 13, 2016
Yup. Expect SourceForge installations to potentially fail in the short-term. There's not much we can do here beside wait out SourceForge, I'm afraid 😢. Worth keeping an eye on their Twitter to see when things are all clear again.
Run command:
brew install wine
Output:
Tried to install libusb-compat before installing wine. It's succeeded. But then brew still tries to install it during wine installation.
The text was updated successfully, but these errors were encountered: