-
Notifications
You must be signed in to change notification settings - Fork 380
-
Notifications
You must be signed in to change notification settings - Fork 380
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
Alpine Linux: Tests failing on latest release (v2.9) #312
Comments
I believe container stuff (thus arping and ifup/ifdown) and getconf are now taken care of in master per the above two commits, but I'm not sure what to do about iconv. It doesn't seem to recognize any options whatsoever, just responds with "unrecognized option" with all |
I did some further digging, and apparently, there are functional differences between glibc and musl versions of iconv, (See: https://wiki.musl-libc.org/functional-differences-from-glibc.html#iconv). Is there a way to force-skip a test? Not very familiar with |
Sure, there may be that kind of functional differences but that doesn't mean it'd have to affect bash-completion in any way. Adding a skip for option completion because the musl one doesn't output an usage message we could use to parse options from: https://git.alpinelinux.org/aports/tree/main/musl/iconv.c |
Oh that's true. Sounds good to me! |
Such as on Alpine Linux (musl libc). Refs #312
Pretty much all of this should be taken care of in master, apart from killall/pidof failures which are tracked in #318. |
Thanks! |
Such as on Alpine Linux (musl libc). Refs scop#312
Could you make a release? NixOS with musl also suffers from this. |
I'm the maintainer of bash-completion for Alpine Linux,
and I have a few tests that are failing on the latest release:
NOTE: I'm developing in an LXC container, so I'm assuming that's why ifup/ifdown are failing, the log mentions something about failing to run due to being in a Docker container.
See: https://gitlab.com/oxr463/aports/issues/31
log.txt
The text was updated successfully, but these errors were encountered: