Skip to content

Commit

Permalink
Fix doctrine/mongodb dependency
Browse files Browse the repository at this point in the history
  • Loading branch information
@jmikola
jmikola committed Jul 5, 2012
1 parent f4280d7 commit 0aee133
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion composer.json
View file
Expand Up @@ -15,7 +15,7 @@
"symfony/yaml": ">=2.0",
"symfony/console": ">=2.0",
"doctrine/common": ">=2.2.0",
"doctrine/mongodb": "@dev"
"doctrine/mongodb": "master@dev"
},
"autoload": {
"psr-0": { "Doctrine\\ODM\\MongoDB": "lib/" }
Expand Down

7 comments on commit 0aee133

@superdweebie
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jmikola The master@dev syntax seems to break my attempts to composer install, while master-dev works. Is there something I'm doing wrong?

@superdweebie
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry, I should clarify that, dev-master works (not master-dev)

@ulrichsg
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I second this complaint. Here's the error message from composer:

Your requirements could not be solved to an installable set of packages.

Problem 1
- doctrine/mongodb-odm dev-master requires doctrine/mongodb master@dev -> no matching package found.
- doctrine/mongodb-odm dev-master requires doctrine/mongodb master@dev -> no matching package found.
- Installation request for doctrine/mongodb-odm dev-master -> satisfiable by doctrine/mongodb-odm dev-master.

Potential causes:

@jmikola
Copy link
Member Author

@jmikola jmikola commented on 0aee133 Jul 9, 2012

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I recently changed master@dev to @dev, as the latter will support released versions in the future instead of being restricted to the master branch; however, neither should be the cause of this problem.

I think you may need to specify minimum-stability: "dev" in your Composer project files, as I did in doctrine/DoctrineMongoDBBundle@73223d8. Even if you require a package with dev stability, Composer doesn't enforce that stability level for any indirect dependencies. I'm unsure if that's intentional or just an oversight/bug, but the only workaround I found was to allow dev packages at my project level (or the bundle in this case).

@jmikola
Copy link
Member Author

@jmikola jmikola commented on 0aee133 Jul 9, 2012

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, do make sure that your composer.phar file is up-to-date, otherwise the @ syntax might not even be supported (another possible reason for why you can't find the package).

@ulrichsg
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

minimum-stability: "dev" works for me. Thanks!

@superdweebie
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

minimum-stability: "dev" works for me too. :)

Please sign in to comment.