-
Notifications
You must be signed in to change notification settings - Fork 9
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
UBI downloads incompatible artifacts on MUSL systems #70
Comments
Thanks for the report. I should have a fix for the musl issue out soon. For Android, can you point me at something that releases Android artifacts? That'd be helpful. |
I see that chezmoi releaes for Android, but the artifact doesn't have "linux" in the name. It's "chezmoi_2.53.0_android_arm64.tar.gz". So that won't be an issue. If someone does release something like "project-v1.2.0-linux-android.tar.gz" then that would be a problem. Have you seen that pattern in use in the wild? |
The musl issue is fixed in v0.2.1, which I just released. I'll close this issue for now but if you can find an example of an issue with Android builds, please make a new issue. Thanks! |
I'll report the android issue whenever I can remember where it occurred. I genuinely still can't remember where it occurred but I distinctly remember seeing |
Note - I mostly tested this against a small wrapper program to download artifacts for multiple platforms quickly.
ubi tends to download GNU/glibc releases even when looking for files with a musl target. This seems to be caused by it falling back upon whichever artifact comes first alphabetically, and between
gnu
andmusl
,gnu
comes first alphabetically.I reproduced this with the following projects:
Also, while I don't have the specific project this occurred on, I had once instance of ubi downloading android artifacts, which very well could be the same issue given that
android
even comes beforegnu
alphabetically. If I can find where that occurred I'll mention it here.Debug output (for
cargo-bins/cargo-binstall
on arm64 alpine linux):The text was updated successfully, but these errors were encountered: