Open Heus-Sueh opened 1 month ago
Bom dia Metheus!
Just tried with a fedora distro which did no show any issues. Your mise
version used seems a bit dated but that should not be the problem. I assume an existing environment variable might interfere.
$ docker run -it --rm fedora /bin/sh
$ yum install -y yum-utils
$ yum-config-manager --add-repo https://mise.jdx.dev/rpm/mise.repo
$ yum install -y mise
$ mise use -g go
$ mise x -- go version
go version go1.23.1 linux/arm64
Can you post your env
output?
Just tried with a fedora distro which did no show any issues.
I believe this bug affects the atomic version of Fedora, if mise is trying to install on /usr
it will not be able to install, because this directory is read-only for security
https://fedoraproject.org/atomic-desktops/
Can you post your
env
output?
env:
🞈 mise env
export JAVA_HOME=/var/home/heus/.local/share/mise/installs/java/17.0.2
export PATH='/var/home/heus/.local/share/mise/installs/java/17/bin:/var/home/heus/.local/share/mise/installs/python/3.12/bin:/var/home/heus/.local/share/mise/installs/watchexec/latest/bin:/var/home/heus/.local/share/mise/shims:/usr/lib64/ccache:/var/home/heus/.cargo/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/var/home/heus/.local/bin:/var/home/heus/.cargo/bin:/var/home/heus/.scripts/:/var/lib/flatpak/exports/bin:/var/home/heus/.local/share/flatpak/exports/bin:/usr/local/go/bin'
I believe this bug affects the atomic version of Fedora, if mise is trying to install on /usr it will not be able to install, because this directory is read-only for security
I guess in this case you need to set MISE_DATA_DIR (and maybe others) to a directory that is writable.
I believe this bug affects the atomic version of Fedora, if mise is trying to install on /usr it will not be able to install, because this directory is read-only for security
I guess in this case you need to set MISE_DATA_DIR (and maybe others) to a directory that is writable.
but by default it is already configured for the home which is not a problem, the problem would be being set in a system directory
I would be interested in your env
output (not mise env
). AFAIK mise
does not set GOPATH so its probably set by something else.
I would be interested in your
env
output (notmise env
). AFAIKmise
does not set GOPATH so its probably set by something else.
I managed to solve it by setting these paths manually in bashrc
export GOPATH=$HOME/.go
export GOMODCACHE=$HOME/.go/pkg/mod
but I have no idea where this "codelearning" user came from, I've already checked in /etc/environment
, /etc/profile
, bashrc
or zshrc
Describe the bug
go: GOPATH entry is relative; must be absolute path: "$HOME/Codelearning/go".
this user "codelearning" is not mineTo Reproduce
mise use -g go
in an immutable/atomic distro like Fedora AtomicExpected behavior go be installed
mise doctor
outputAdditional context I was trying to install go just to play around and I couldn't Trace-log.txt