Cannot install the sandbox about cmf-sandbox HOT 14 CLOSED

strange, i can not reproduce that. composer install does not complain about out of sync and installs happily.

are you using the latest version of composer, and the latest master branch of this repository? i think probably something of your stack is outdated.

from cmf-sandbox.

Same issue here, followed the docs, fresh install, latest version of composer.

from cmf-sandbox.

i did a fresh clone of the sandbox (from here, not any fork) and ran composer self-update, then composer install and it ran through smoothly. what confuses me most is that you say composer is complaining that the .lock file is out of sync.

from cmf-sandbox.

same issue on travis ci
http://travis-ci.org/#!/symfony-cmf/cmf-sandbox/jobs/1835522

from cmf-sandbox.

travis works again for the sandbox with jackrabbit: http://travis-ci.org/#!/symfony-cmf/cmf-sandbox

but somehow we still seem to run into weird composer bugs for all the other platforms. the "pagage not installed" bug is already reported: composer/composer#789

from cmf-sandbox.

I have exactly the same issue. Completely fresh installation and just following the instructions from the README file. After applying the following hackish patch the installation worked for me:

diff --git a/composer.lock b/composer.lock
index 415ea6a..e3b950a 100644
--- a/composer.lock
+++ b/composer.lock
@@ -88,24 +88,12 @@
         {
             "package": "jackalope/jackalope",
             "version": "dev-master",
-            "alias-pretty-version": "1.0.x-dev",
-            "alias-version": "1.0.9999999.9999999-dev"
-        },
-        {
-            "package": "jackalope/jackalope",
-            "version": "dev-master",
             "source-reference": "6ad592e9ccba23a2b43d85ddf67cee5897a66e6a",
             "commit-date": "1342006705"
         },
         {
             "package": "jackalope/jackalope-jackrabbit",
             "version": "dev-master",
-            "alias-pretty-version": "1.0.x-dev",
-            "alias-version": "1.0.9999999.9999999-dev"
-        },
-        {
-            "package": "jackalope/jackalope-jackrabbit",
-            "version": "dev-master",
             "source-reference": "3c4fb61bf0c0664d09ef520683842e6426c033e0",
             "commit-date": "1342006526"
         },

from cmf-sandbox.

does this issue still exist?

from cmf-sandbox.

Yes, it still exist . In the error message,I have One more Problem noticed on knp-menu-bundle :
Problem 3 - Installation request for knplabs/knp-menu-bundle == 1.1.0.0 -> satisfiable by knplabs/knp-menu-bundle v1.1.0. - sonata-project/admin-bundle dev-master requires knplabs/knp-menu-bundle dev-master -> satisfiable by knplabs/knp-menu-bundle dev-master. - Can only install one of: knplabs/knp-menu-bundle dev-master, knplabs/knp-menu-bundle v1.1.0. - Installation request for sonata-project/admin-bundle == 9999999-dev -> satisfiable by sonata-project/admin-bundle dev-master.

from cmf-sandbox.

i wonder if we should just rip the vendors script of symfony 2.0 to be able to lock a vendors dir as @lsmith77 or i myself have it right now (=working state) and reproduce it exactly. should not be that hard i think, worked ok for symfony 2.0. we would keep composer.json to go back to it once it works of course.

from cmf-sandbox.

the issue is caused by SonataAdminBundle having added a dependency on dev-master of KnpMenuBundle, which according to @stof is "barely useable" atm .. we are using 1.1.* atm already ... i will check with stof on some more details .. either we have to update to also use dev-master .. or SonataAdminBundle can hopefully revert ..

from cmf-sandbox.

well but it happened before and will again as long as we can not base
only on tagged releases or composer is fixed to store everything in the
.lock file it needs to really replay the installation.

from cmf-sandbox.

yeah .. i am just not sure if it helps us creating this or if we just have to suffer until @Seldaek comes back from vacation and fixes it at the source .. @naderman are you in the loop about the issue and can you give us an idea of when we can ideally expect a fix .. or if its better that we come up with some hack solution for now.

from cmf-sandbox.

the issue with going back to a deps file is that imho we cannot switch away from composer.json to define the dependencies so what we would need to do is make it possible to generate a lock file that includes the git repo url and sha1 hash and then we need to manually also deal with post install stuff. it seems like a huge mess to spend time on .. but yeah .. right now it makes the CMF unusable for new comers :(

from cmf-sandbox.

the change in SonataAdminBundle has been reverted .. i just did a "composer install" with a cleaned out vendor dir and it installed everything just fine.

from cmf-sandbox.