That is so strange. I'll dig deeper

Reply to this note

Please Login to reply.

Discussion

the binary at the url location is correct. see:

```

$ curl -o ./ngit.tar.gz -L -0 https://github.com/DanConwayDev/ngit-cli/releases/download/v1.4.3/ngit-x86_64-unknown-linux-gnu.tar.gz

% Total % Received % Xferd Average Speed Time Time Time Current

Dload Upload Total Spent Left Speed

0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0

100 8844k 100 8844k 0 0 2511k 0 0:00:03 0:00:03 --:--:-- 3133k

$ tar -xzvf ngit.tar.gz

ngit

$ sudo rm /bin/ngit

$ ngit

bash: /usr/bin/ngit: No such file or directory

$ chmod +x ngit

$ sudo cp ngit /bin/ngit

$ ngit --version

ngit 1.4.3

```

Ugh I know what happened. I have ~/.cargo/bin/ngit too (that one is 0.0.1) - for some reason that one was loaded before in $PATH. But weird that loads the zs version (1.4.3) in other terminal session. So the zapstore cli is working correctly. I'll look at the publishing hanging issue

I wonder whether zapstore should check if the binary already exists in the path and warn the user about the conflict?

Definitely! Will add as issue

I was going to do it for you but couldn't find you nostr git announcement ;-)

Also added as issue 🤣