-
Notifications
You must be signed in to change notification settings - Fork 77
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
busybox error #1
Comments
This problem also occurs in the ca-certificates package. |
I have the same problem as well:
So far I haven't been able to find out what exactly this error means. I keep getting it on both my armv8l asus chromebook and aarch64 android phone. |
I'm also getting this error. How can this be debugged? Is there way to make |
It looks like the trigger script works fine when executed manually:
So why does apk fail when executing this script? |
Finally I found the root cause and the problem is in proot so I will give a PR to proot and this problem will be solved after my PR merge |
My PR is merged now and just upgrade your proot and reinstall Alpine |
I'm still getting this error even though I have the new version of proot according to termux/termux-packages#2464 (revision 10)
I've done a fresh install of everything including termux itself. Any suggestions? |
I'm also still getting this error 😭 |
I am running into what looks like a similar error, but unrelated to Termux (I am not using it): proot-me/proot#191. |
Executing busybox-1.27.2-r8.trigger
ERROR: busybox-1.27.2-r8.trigger: script exited with error 127
3 errors; 101 MiB in 32 packages
The text was updated successfully, but these errors were encountered: