Skip to content
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

Closed
shams75 opened this issue Mar 6, 2018 · 9 comments
Closed

busybox error #1

shams75 opened this issue Mar 6, 2018 · 9 comments

Comments

@shams75
Copy link

shams75 commented Mar 6, 2018

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

@ghost
Copy link

ghost commented Apr 7, 2018

This problem also occurs in the ca-certificates package.

@djrivington
Copy link

djrivington commented Apr 8, 2018

I have the same problem as well:

[termux@alpine home]# apk add nmap
(1/4) Installing libgcc (6.4.0-r5)
(2/4) Installing libpcap (1.8.1-r1)
(3/4) Installing libstdc++ (6.4.0-r5)
(4/4) Installing nmap (7.60-r2)
Executing busybox-1.27.2-r6.trigger
ERROR: busybox-1.27.2-r6.trigger: script exited with error 127
OK: 16 MiB in 15 packages

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.

@pts
Copy link

pts commented Apr 27, 2018

I'm also getting this error. How can this be debugged? Is there way to make apk show the real error message?

@pts
Copy link

pts commented Apr 27, 2018

It looks like the trigger script works fine when executed manually:

# tar xvf scripts.tar busybox-1.27.2-r7.Q16KKkDenzjdRkzTB/WOw1mNRvBYo=.trigger
busybox-1.27.2-r7.Q16KKkDenzjdRkzTB/WOw1mNRvBYo=.trigger
# cat busybox-1.27.2-r7.Q16KKkDenzjdRkzTB/
cat: read error: Is a directory
# cat busybox-1.27.2-r7.Q16KKkDenzjdRkzTB/WOw1mNRvBYo\=.trigger 
#!/bin/sh

do_bb_install=

for i in "$@"; do
        case "$i" in
                /lib/modules/*)
                        if [ -d "$i" ]; then
                                /bin/busybox depmod ${i#/lib/modules/}
                        fi
                        ;;
                *) do_bb_install=yes;;
        esac
done

if [ -n "$do_bb_install" ]; then
        [ -e /bin/bbsuid ] && /bin/bbsuid --install
        [ -e /bin/busybox-extras ] && /bin/busybox-extras --install -s
        /bin/busybox --install -s
fi
# busybox-1.27.2-r7.Q16KKkDenzjdRkzTB/WOw1mNRvBYo\=.trigger  x          
# echo $?
0

So why does apk fail when executing this script?

@Hax4us
Copy link
Owner

Hax4us commented May 26, 2018

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

@Hax4us
Copy link
Owner

Hax4us commented May 29, 2018

My PR is merged now and just upgrade your proot and reinstall Alpine

@Hax4us Hax4us closed this as completed May 29, 2018
@grind086
Copy link

grind086 commented Jun 1, 2018

I'm still getting this error even though I have the new version of proot according to termux/termux-packages#2464 (revision 10)

$ apt install proot
Reading package lists... Done
Building dependency tree
Reading state information... Done
proot is already the newest version (5.1.107-10).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

I've done a fresh install of everything including termux itself. Any suggestions?

@gauloics
Copy link

I'm also still getting this error 😭

@probonopd
Copy link

I am running into what looks like a similar error, but unrelated to Termux (I am not using it): proot-me/proot#191.

@tmm1 tmm1 mentioned this issue May 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants