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

aftman self-install fails when /tmp is on a seperate filesystem #35

Open
Joshument opened this issue Oct 2, 2022 · 4 comments · May be fixed by #36
Open

aftman self-install fails when /tmp is on a seperate filesystem #35

Joshument opened this issue Oct 2, 2022 · 4 comments · May be fixed by #36

Comments

@Joshument
Copy link

When installing aftman on a unix-like operating system, aftman self-install will fail if /tmp is on a seperate filesystem (i.e. tmpfs)

[INFO  aftman::tool_storage] Updating all Aftman binaries...
Aftman error: failed to rename file from /home/josh/.aftman/bin/rojo to /tmp/.tmpaVMK5X/rojo

Caused by:
    Invalid cross-device link (os error 18)
@shadownetdev1
Copy link

I also have this problem

@RyanLua
Copy link

RyanLua commented Feb 22, 2024

I have the same issue on Debian.

@RyanLua ➜ /workspaces/Satchel (codespaces) $ aftman self-install
[INFO  aftman::tool_storage] Updating all Aftman binaries...
Aftman error: failed to rename file from /home/vscode/.aftman/bin/selene to /tmp/.tmp60yylN/selene

Caused by:
    Invalid cross-device link (os error 18)

@Geeboi-exe
Copy link

Geeboi-exe commented Oct 4, 2024

I run Pop!_Os 22.04 and i have been getting the exact same issue. My /home directory is mounted on a seperate filesystem as my /root directory, but both use ext4.

[INFO  aftman::tool_storage] Updating all Aftman binaries...
Aftman error: failed to rename file from /home/gabe/.aftman/bin/aftman to /tmp/.tmpnc3tQj/aftman

Caused by:
    Invalid cross-device link (os error 18)

I still get the exact same error after 2 years

@nooneisback
Copy link

nooneisback commented Dec 3, 2024

Aftman self-install never worked properly for me on Arch with this same error appearing if I try running it twice. It creates the .aftman directory, but doesn't update the PATH variable. I always got it working by just tossing it into /usr/local/bin/ and chmodding to be executable.

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

Successfully merging a pull request may close this issue.

5 participants