Core: An error occurred trying to clone ...

Created on 30 Aug 2017  Â·  10Comments  Â·  Source: adonisjs/core

I just tried this framework and got this error during installation.
`` npm i -g adonis-cli sam@DESKTOP-KQQ0A3T MINGW64 ~/lab $ adonis new adonis _ _ _ _ / \ __| | ___ _ __ (_)___ | |___ / _ \ / _ |/ _ \| '_ \| / __|_ | / __|
/ ___ \ (_| | (_) | | | | __ \ |_| __ \
/_/ ___,_|___/|_| |_|_|___/___/|___/

√ Your current Node.js & npm version match the AdonisJs requirements!

× An error occured while trying to clone master version of adonisjs/adonis-app blueprint.
Command failed: git clone -b master --single-branch https://github.com/adonisjs/adonis-app. git C:\Users\zorg\Google Drive\lab\adonis
fatal: Too many arguments.

usage: git clone [] [--] [

]

-v, --verbose         be more verbose
-q, --quiet           be more quiet
--progress            force progress reporting
-n, --no-checkout     don't create a checkout
--bare                create a bare repository
--mirror              create a mirror repository (implies bare)
-l, --local           to clone from a local repository
--no-hardlinks        don't use local hardlinks, always copy
-s, --shared          setup as shared repository
--recursive           initialize submodules in the clone
--recurse-submodules  initialize submodules in the clone
-j, --jobs <n>        number of submodules cloned in parallel
--template <template-directory>
                      directory from which templates will be used
--reference <repo>    reference repository
--reference-if-able <repo>
                      reference repository
--dissociate          use --reference only while cloning
-o, --origin <name>   use <name> instead of 'origin' to track upstream
-b, --branch <branch>
                      checkout <branch> instead of the remote's HEAD
-u, --upload-pack <path>
                      path to git-upload-pack on the remote
--depth <depth>       create a shallow clone of that depth
--shallow-since <time>
                      create a shallow clone since a specific time
--shallow-exclude <revision>
                      deepen history of shallow clone by excluding rev
--single-branch       clone only one branch, HEAD or --branch
--shallow-submodules  any cloned submodules will be shallow
--separate-git-dir <gitdir>
                      separate git dir from working tree
-c, --config <key=value>
                      set config inside the new repository
-4, --ipv4            use IPv4 addresses only
-6, --ipv6            use IPv6 addresses only

All 10 comments

Can u share the version of Git on your machine?

$ git --version
git version 2.11.1.windows.1

Would u mind upgrading it to the latest version, this seems to be quite a old one

Thanks. I went with express yesterday.

You still should not close it. There is nothing worse than a library that does not work out of the box. I consider this important issue. Your library not to work because not (node, npm) but git version is not good

Yes since git is used to clone the repo. You can clone it manually and then do npm install.

Also I am less interested in taking weird feedback, even when I am trying to help you with the process. You should stick to express

If you don't want to use up to date tools it's not Adonis fault. 😉

@RomainLanz I use everything from python, php and node stack ... just fine with my current version of git.

just fine with my current version of git.

You just overreact when we tell you that you should update your git version.
If you want to use an old version of a tool and you don't want to update it, it's not our problem.

Have a nice time using express

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

dezashibi picture dezashibi  Â·  4Comments

navdeepsingh picture navdeepsingh  Â·  3Comments

Extarys picture Extarys  Â·  4Comments

itsg2jakhmola picture itsg2jakhmola  Â·  3Comments

imperez picture imperez  Â·  4Comments