This one is a bit strange, but it is connected to how I am forced to use atuin.
Because a few systems of mine are not the latest and greatest releases of their respective distributions, I am unable to update or even use atuin due to “version `GLIBC_2.38’/`GLIBC_2.39’ not found” when trying to work with “x86_64-unknown-linux-gnu” releases.
In one of my cases it is a Debian 12.
The funny thing is, there is one platform that is statically linked. That is MUSL. Because it was build on the same x86_64 cpu architecture and is statically linked, it runs without problems on linux distros that only do libc.
As such, whenever “atuin update” is executed, it only looks up the OS platform which is “x86_64-unknown-linux-gnu”, tries to update and fails with:
```
./atuin-bak update
Checking for updates…
× failed to execute installer
╰─
Permission denied (os error 13)
```
Were the updater to actually consider that the binary was built with “x86_64-unknown-linux-musl” and tried to update with that platform in mind, it would probably not fail.
Either way, I do not expect anything from this as I have my little script that fixes the issue for me, but nonetheless a thought that could be considered.