-
-
Notifications
You must be signed in to change notification settings - Fork 37
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
[BUG] ERROR: archey.test.entries.test_archey_packages (unittest.loader._FailedTest) #101
Comments
Thanks for opening this up ! I'm preparing a patch to properly catch Thanks for your time 🙇 |
vas@apex-main> strace brew ~ as i said i never had brew installed only mention was in the oh my bash files had had some reference to a plugin but that plugin wasn't installed either |
So I can't see why you keep getting |
that fixed it , i ran a connection to the user instead of root and using su user and it worked |
Perfect, I think we properly narrowed this down, I'll publish the patch I was talking about and make it point to this issue. |
> The list of external `subprocess` calls concerned by this patch is 100% subjective, and it might be required to extend it in the future. > See #101 for rationale.
From https://aur.archlinux.org/packages/archey4/?O=10&PP=10#comment-825146.
getting this when trying to upgrade or clean install the latest build, any help ? thanks
Hi @vasilejianu, thanks for your feedback. Have you got brew installed on your system ? Can you run brew --cellar manually ? I don't get why it would raise
PermissionError
exception, but we can catch it upstream in the future if needed... Bye, waiting for your input.i don't have brew its weird is doing that
its a minimal arch install
Linux apex-main 5.13.13-arch1-1 #1
all i have is nginx,mariadb,php,named
@vasilejianu : so I've tried with
yay
myself against an Arch container, and thecheck()
part is really doing well... I think something is to blamed on your system (noexec
(?),yay
configuration(?), somehowbrew
is available underPATH
on yourvas
regular user(?), ...). If you find out, please let me know. If something is definitely wrong upstream, let me know too. Good luckthis is interesting
i have run the test manually under user priv it fails , under root privs it passes
@vasilejianu : could you try to run
which brew
under your regular user ? You can also use a (broad)find
if nothing comes out; I'm pretty sure you got a brew (apparently not executable) somewhere. Almost there !@vasilejianu : good one. Although I'm confused about catching
PermissionError
in this case, as all the other sub-process calls across the code base do not, whereas the same problem could occur. What do you think about that ? Do you think this exception should be caught elsewhere ?idk although that was the only ref to brew in the system i have uninstalled oh my bash and still getting the error
i have tried under a diff user too
@vasilejianu : have you tried under another BASH session without
brew
symbol exported by your previous plugin ? [...]yeah i have installed zsh, was previously using bash i have removed the user and added it again with a new zsh shell
The text was updated successfully, but these errors were encountered: