Arch Linux User Repository

@marza I am having the same problem, it is an upstream issue i think.

I'm having an issue (with a workaround) where west fails to use git, apparently because the toolchain-manager shell sets up the env to use an older version of git:

➜ nrfutil toolchain-manager launch --shell
Initializing shell environment!

(v2.9.0) % west init -m  https://github.com/nrfconnect/sdk-nrf --mr v2.7.0
=== Initializing in /home/marza/tmp
--- Cloning manifest repository from https://github.com/nrfconnect/sdk-nrf, rev. v2.7.0
Cloning into '/home/marza/tmp/.west/manifest-tmp'...
/home/marza/ncs/toolchains/b77d8c1312/usr/local/libexec/git-core/git-remote-https: error while loading shared libraries: libunistring.so.2: cannot open shared object file: No such file or directory
FATAL ERROR: command exited with status 128: git clone --branch v2.7.0 https://github.com/nrfconnect/sdk-nrf /home/marza/tmp/.west/manifest-tmp
(v2.9.0) % which git
/home/marza/ncs/toolchains/b77d8c1312/usr/local/bin/git
(v2.9.0) % git --version
git version 2.37.3

[Exit out of the toolchain-manager shell]
➜ which git
/usr/bin/git

➜ git --version
git version 2.48.1

Same happens for eval "$(nrfutil toolchain-manager env --as-script)"

I "solved it" by just making a manual link from libunistring.so.2 to libunisting in /usr/lib, but this feels a bit dirty, and is probably prone to fail again if git and/or west is updated again. Not sure if there's an easy way to fix this in this package, but do you know of any other ways to do this, for instance making west use the system version of git rather than the one added by the toolchain-manager?