-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix obsolete auto-tools scripts #28
Comments
Yeah, autotools is a complete mess. I don't understand why maintainer doesn't provide tarball with autotools configure script generated. It's a mess. |
Good point. Let me try to do that over the weekend. |
Indeed, as the 0.1.7 version was released with generated |
Sorry for the late reply. I have replaced the github libusb-compat-0.1 release with the tarballs with autotools configure script generated. Please report if there is an issue. Thanks. |
Sourceforge release has also been updated. |
PRs to fix the old scripts are welcome. |
upstream rebuild the release tarball without changing version. libusb/libusb-compat-0.1#28 (comment) switch to .tar.gz so we avoid distfiles cache problems
[ commit 3d1e3285bea8390e53ab085b806936d89e5aeed2 ] upstream rebuild the release tarball without changing version. libusb/libusb-compat-0.1#28 (comment) switch to .tar.gz so we avoid distfiles cache problems
Upstream re-released the v0.1.8 tarballs with autotools related stuff. [1] That makes the hash test to fail: ERROR: while checking hashes from package/libusb-compat//libusb-compat.hash ERROR: libusb-compat-0.1.8.tar.bz2 has wrong sha256 hash: ERROR: expected: 698c76484f3dec1e0175067cbd1556c3021e94e7f2313ae3ea6a66d900e00827 ERROR: got : b692dcf674c070c8c0bee3c8230ce4ee5903f926d77dc8b968a4dd1b70f9b05c ERROR: Incomplete download, or man-in-the-middle (MITM) attack Update the hash and drop LIBUSB_COMPAT_AUTORECONF. [1] libusb/libusb-compat-0.1#28 (comment) [Peter: use .tar.gz to not conflict with s.b.o] Signed-off-by: Sébastien Szymanski <[email protected]> Signed-off-by: Peter Korsgaard <[email protected]>
There are quite some warnings now.
Example from github action Linux build.
The text was updated successfully, but these errors were encountered: