Problems installing the bundle #34

Closed
Defcon0 opened this Issue Jun 5, 2012 · 5 comments

Projects

None yet

2 participants

@Defcon0
Defcon0 commented Jun 5, 2012

Hello,

I'm having trouble installing the migrations bundle (some weeks ago it worked like a charm). I think it corresponds with the changed namespace/git url. (Symfony 2.0.12)

php bin/vendors install --reinstall gives me:

fatal: ambiguous argument '2.0': unknown revision or path not in the working tree.

origin/2.0 gives me the same message.

Any help would be great. Thanks!!

deps:

[DoctrineMigrationsBundle]
git=http://github.com/doctrine/DoctrineMigrationsBundle.git
target=/bundles/Symfony/Bundle/DoctrineMigrationsBundle
version=2.0

AppKernel.php:

new Symfony\Bundle\FrameworkBundle\FrameworkBundle(),
new Symfony\Bundle\SecurityBundle\SecurityBundle(),
new Symfony\Bundle\TwigBundle\TwigBundle(),
new Symfony\Bundle\MonologBundle\MonologBundle(),
new Symfony\Bundle\SwiftmailerBundle\SwiftmailerBundle(),
new Symfony\Bundle\DoctrineBundle\DoctrineBundle(),
new Symfony\Bundle\AsseticBundle\AsseticBundle(),
new Sensio\Bundle\FrameworkExtraBundle\SensioFrameworkExtraBundle(),
new JMS\SecurityExtraBundle\JMSSecurityExtraBundle(),
new Symfony\Bundle\DoctrineMigrationsBundle\DoctrineMigrationsBundle(),
new Wuw\SearchBundle\WuwSearchBundle(),
new FOS\JsRoutingBundle\FOSJsRoutingBundle(),
new Bazinga\ExposeTranslationBundle\BazingaExposeTranslationBundle(),
new Sonata\AdminBundle\SonataAdminBundle(),
new Sonata\UserBundle\SonataUserBundle(),
new FOS\UserBundle\FOSUserBundle(),
new Sonata\EasyExtendsBundle\SonataEasyExtendsBundle(),
new Sonata\BlockBundle\SonataBlockBundle(),
new Sonata\CacheBundle\SonataCacheBundle(),
new Sonata\jQueryBundle\SonatajQueryBundle(),
new Knp\Bundle\MenuBundle\KnpMenuBundle(),
new Sonata\DoctrineORMAdminBundle\SonataDoctrineORMAdminBundle(),

autoload.php:

'Symfony' => array(DIR.'/../vendor/symfony/src', DIR.'/../vendor/bundles'),
'Sensio' => DIR.'/../vendor/bundles',
'JMS' => DIR.'/../vendor/bundles',
'Doctrine\Common' => DIR.'/../vendor/doctrine-common/lib',
'Doctrine\DBAL' => DIR.'/../vendor/doctrine-dbal/lib',
'Doctrine' => DIR.'/../vendor/doctrine/lib',
'Monolog' => DIR.'/../vendor/monolog/src',
'Assetic' => DIR.'/../vendor/assetic/src',
'Metadata' => DIR.'/../vendor/metadata/src',
'Doctrine\DBAL\Migrations' => DIR.'/../vendor/doctrine-migrations/lib',
'Doctrine\DBAL' => DIR.'/../vendor/doctrine-dbal/lib',
'FOS' => DIR.'/../vendor/bundles',
'Bazinga' => DIR.'/../vendor/bundles',
'Sonata' => DIR.'/../vendor/bundles',
'Exporter' => DIR.'/../vendor/exporter/lib',
'Knp\Bundle' => DIR.'/../vendor/bundles',
'Knp\Menu' => DIR.'/../vendor/knp/menu/src',

@stof
Member
stof commented Jun 5, 2012

if you changed the url in the deps file, you need to remove the folder in your vendor dir so that the dependency is cloned again with the new url. The vendors script does not reset the url each time.

@Defcon0
Defcon0 commented Jun 5, 2012

Isn't that done with --reinstall?

@stof
Member
stof commented Jun 5, 2012

it is. But take care also to use origin/2.0 as 2.0 is indeed wrong.

@Defcon0
Defcon0 commented Jun 5, 2012

Removing the folders did the job. Thanks a lot for the hint!! The question is, why reinstall didn't do that by itself.

@stof
Member
stof commented Jun 5, 2012

no idea. I don't use the deps file myself.

@stof stof closed this Jun 5, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment