search

sonata-project / SonataAdminBundle

The missing Symfony Admin Generator
https://docs.sonata-project.org/projects/SonataAdminBundle
MIT License
2.11k stars 1.26k forks source link

Not a git repository #379

Closed mgws closed 12 years ago

mgws commented 12 years ago

Hi, I have a problems with the update of the bundles with "bin/vendors install" like describe in the documentation guide here http://sonata-project.org/bundles/admin/master/doc/reference/installation.html

I have inserted in the deps file the directives: [SonatajQueryBundle] git=http://github.com/sonata-project/SonatajQueryBundle.git target=/bundles/Sonata/jQueryBundle

[SonataUserBundle] git=http://github.com/sonata-project/SonataUserBundle.git target=/bundles/Sonata/UserBundle

[SonataAdminBundle] git=http://github.com/sonata-project/SonataAdminBundle.git target=/bundles/Sonata/AdminBundle

[MenuBundle] git=http://github.com/knplabs/KnpMenuBundle.git target=/bundles/Knp/Bundle/MenuBundle

[KnpMenu] git=https://github.com/knplabs/KnpMenu.git target=/knp/menu

When I launch the command "sudo php bin/vendors install" in the command line, it update symfony and other plugin, but when it arrive to the Sonata Admin-Jquery-User-KnpMenu Bundle it give me these errors:

Installing/Updating SonatajQueryBundle fatal: Not a git repository (or any of the parent directories): .git Installing/Updating SonataUserBundle fatal: Not a git repository (or any of the parent directories): .git Installing/Updating SonataAdminBundle fatal: Not a git repository (or any of the parent directories): .git Installing/Updating MenuBundle fatal: Not a git repository (or any of the parent directories): .git Installing/Updating KnpMenu fatal: Not a git repository (or any of the parent directories): .git

The SonataDoctrineORMAdminBundle, also added in the deps file, is updated correctly.... Why this?

Thnx!

rande commented 12 years ago

I can't help on this, it is not an issue with the bundle.

crazytonyi commented 12 years ago

I'm sorry. You are probably totally right, rande. But just saying it's not a problem isn't a real answer at all. At least provide some kind of test log or attempts to reproduce.

rande commented 12 years ago

@crazytonyi : the error here is coming from git and cloning each repository individually just works. I cannot do more, and users are more than welcome to improve the documentation or provide more detailed information about their issues.

crazytonyi commented 12 years ago

Exactly. What you just said was way more informative. This was the first repo forum I found when I googled that error, and I thought this was the bug reporter for all of GitHub at first. So now that I've seen the issue on 5 different repos, for sure it's a github thing. But it would help the people posting the problem and the wayward googler to put "I can't fix this because it's a github problem. I'm not seeing any issue on this repo. blah blah". anyways, now I just sound opinionated. Sorry. Thanks for following up so quickly.