-
Notifications
You must be signed in to change notification settings - Fork 14
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
bluefin-cli brew install PACKAGE error no file or directory #111
Comments
Bluefin-cli uses its own brew installation and is using brew packaged by Wolfi which is slightly different in implementation from brews default installation method. This was done prior to having homebrew on the bluefin image. |
Looks like it might have a broken brew installation. It seems to be cp command having a "." at the end. Instead of copying folder name to folder name it's trying to copy folder contents into a folder which doesn't exist.
To figure this out I monitored /tmp with inotifyd to see the tmp files were getting created. Freezing the command I was able to verify that it was extracting properly. I then manually stepped through the process it was trying to do and realized there was that extra dot in the copy command.
That makes since and helps explain what I was reading on the introduction page and why the other two work. |
I found same issue. Does it still happen to you @lethedata? |
Yeah, still broken. I tried a lot of different things but it always gets stuck on copying files. Manually doing it works which confuses me. The |
Did you run using |
Distrobox assemble via ujust scripts and systemd quadlet. Same issue on both. I took a peak at brews code snd the This means brew is supposed to create folders before moving tho the debug doesn't really show that. I think the next thing to look at is if wolfi has this problem to see if its some packaging issue. |
Has anyone ever gotten bluefin-cli and brew to work? I got hit by this today. |
I just tried it again, but still not working. At least the host-installed brew accessible from container, that's enough for not duplicating brew. |
True, that's what I am using right now. But I'd really like only having brew in a container, since I absolutely hate it clobbering system-wide components like |
I think I got to the bottom of this - the culprit seems to be the With
Removing
This seems to be related/is this issue upstream: uutils/coreutils#6671 If it were me, I'd drop the |
It looks nice, need to try it later. |
When trying to install any package with brew via bluefin-cli on bluefin-dx I'm receiving the following error with slightly different paths:
Verbosing the command reveals it's theTesting with the Fedora and Ubuntu toolboxes work fine and even have access to tools that are already installed./tmp/homebrew-unpackXXXXXXXX-XXXXX-XXXXXX/
not existing which is causing tar to fail.The other thing I noticed is that this box doesn't see any brew applications installed by the host tho this might actually be expected.
Brew Version:
Homebrew >=4.1.0 (shallow or no git repository)
The text was updated successfully, but these errors were encountered: