'babel install' problems about nimble HOT 9 CLOSED

That's odd. babel install nimgame works for me, as does babel install jester. I'm not sure what the problem is, can you show me the full output of those commands?

Where does npm install packages to?

from nimble.

Funny - in the meantime I installed gnome (I am on ubuntu server) and suddenly jester works. nimgame still doesn't and here is the full output:

ubuntu@ip-10-180-157-49:~/test$ babel install nimgame
Downloading nimgame into /tmp/babel/nimgame...
Executing git...
Already on 'master'
fatal: remote error:
  Repository not found.
FAILURE: Execution failed with exit code 256

Regarding jester, I will re-create the installation (obviously the missing directory has something to do with gnome), so that I can reproduce the error.

from nimble.

Try this:

cd /tmp/babel/nimgame
git pull

Does it give the same 'fatal' error?

Weird that gnome would affect it. Something odd is going on with git but i'm not sure what. What's your git version?

from nimble.

no, it says 'already up to date'. my git version is 1.7.9.5.

from nimble.

I was able to reproduce your intial error when installing nimgame and that is in fact correct: it checks out the v0.3 tag of the nimgame repo which does not contain a .babel file. But I have found a different bug thanks to you: on newer versions of git, --depth 1 seems to clone the repo without any tag information which is why I could not reproduce that error on my machine. The fatal: remote error is still puzzling though, is that the same error you get when trying to install jester?

from nimble.

Good to know that you could catch that!

No, the jester error was different: FAILURE: Execution failed with exit code 32768

from nimble.

Right, that doesn't tell me much. Can you give me the full output for Jester?

from nimble.

I started from a clean installation again, and I couldn't reproduce the jester issue - which probably means it was a side effect of my installation attempts. Still strange though.

from nimble.

Indeed, very weird. Thanks for reporting anyway, it helped me find a bug heh. Let me know if you encounter this again.

from nimble.