Unable to install - conflicting composer requirements

[MichaelMackus]

Looks like the compose requirements all lead to conflicting package versions.

[MichaelMackus]

Here's the error I get on a fresh composer.json:

  Problem 1
    - sylius/sylius v1.0.0-alpha.1 requires doctrine/phpcr-odm ^1.3 -> satisfiable by doctrine/phpcr-odm[1.3.0, 1.3.0-rc, 1.3.0-rc2, 1.3.0-rc3, 1.3.0-rc4, 1.3.1, 1.3.2, 1.4.0, 1.4.1, 1.4.2, 1.4.3, 1.4.4, 1.4.x-dev].
    - Can only install one of: doctrine/phpcr-odm[2.0.x-dev, 1.3.0].
    - Can only install one of: doctrine/phpcr-odm[2.0.x-dev, 1.3.0-rc].
    - Can only install one of: doctrine/phpcr-odm[2.0.x-dev, 1.3.0-rc2].
    - Can only install one of: doctrine/phpcr-odm[2.0.x-dev, 1.3.0-rc3].
    - Can only install one of: doctrine/phpcr-odm[2.0.x-dev, 1.3.0-rc4].
    - Can only install one of: doctrine/phpcr-odm[2.0.x-dev, 1.3.1].
    - Can only install one of: doctrine/phpcr-odm[2.0.x-dev, 1.3.2].
    - Can only install one of: doctrine/phpcr-odm[2.0.x-dev, 1.4.0].
    - Can only install one of: doctrine/phpcr-odm[2.0.x-dev, 1.4.1].
    - Can only install one of: doctrine/phpcr-odm[2.0.x-dev, 1.4.2].
    - Can only install one of: doctrine/phpcr-odm[2.0.x-dev, 1.4.3].
    - Can only install one of: doctrine/phpcr-odm[2.0.x-dev, 1.4.4].
    - Can only install one of: doctrine/phpcr-odm[2.0.x-dev, 1.4.x-dev].
    - lakion/cms-plugin dev-master requires doctrine/phpcr-odm ^2.0@dev -> satisfiable by doctrine/phpcr-odm[2.0.x-dev].
    - Conclusion: remove symfony/console v4.0.4
    - Installation request for lakion/cms-plugin dev-master -> satisfiable by lakion/cms-plugin[dev-master].
    - Conclusion: don't install symfony/console v4.0.4
    - Conclusion: don't install symfony/symfony v4.0.4
    - lakion/cms-plugin dev-master requires sylius/sylius ^1.0 -> satisfiable by sylius/sylius[1.0.x-dev, 1.1.x-dev, 1.2.x-dev, v1.0.0, v1.0.0-alpha.1, v1.0.0-alpha.2, v1.0.0-beta.1, v1.0.0-beta.2, v1.0.0-beta.3, v1.0.0-rc.1, v1.0.0-rc.2, v1.0.1, v1.0.2, v1.0.3, v1.0.4, v1.0.5, v1.0.6, v1.0.7, v1.0.8].
    - sylius/sylius v1.0.0-alpha.2 requires symfony/symfony ^2.8 -> satisfiable by symfony/symfony[2.8.x-dev, v2.8.0, v2.8.0-BETA1, v2.8.1, v2.8.10, v2.8.11, v2.8.12, v2.8.13, v2.8.14, v2.8.15, v2.8.16, v2.8.17, v2.8.18, v2.8.19, v2.8.2, v2.8.20, v2.8.21, v2.8.22, v2.8.23, v2.8.24, v2.8.25, v2.8.26, v2.8.27, v2.8.28, v2.8.29, v2.8.3, v2.8.30, v2.8.31, v2.8.32, v2.8.33, v2.8.34, v2.8.4, v2.8.5, v2.8.6, v2.8.7, v2.8.8, v2.8.9].
    - sylius/sylius v1.0.0-beta.1 requires symfony/symfony ^3.2 -> satisfiable by symfony/symfony[3.2.x-dev, 3.3.x-dev, 3.4.x-dev, v3.2.0, v3.2.0-BETA1, v3.2.0-RC1, v3.2.0-RC2, v3.2.1, v3.2.10, v3.2.11, v3.2.12, v3.2.13, v3.2.14, v3.2.2, v3.2.3, v3.2.4, v3.2.5, v3.2.6, v3.2.7, v3.2.8, v3.2.9, v3.3.0, v3.3.0-BETA1, v3.3.0-RC1, v3.3.1, v3.3.10, v3.3.11, v3.3.12, v3.3.13, v3.3.14, v3.3.15, v3.3.16, v3.3.2, v3.3.3, v3.3.4, v3.3.5, v3.3.6, v3.3.7, v3.3.8, v3.3.9, v3.4.0, v3.4.0-BETA1, v3.4.0-BETA2, v3.4.0-BETA3, v3.4.0-BETA4, v3.4.0-RC1, v3.4.0-RC2, v3.4.1, v3.4.2, v3.4.3, v3.4.4].
    - sylius/sylius v1.0.0-beta.2 requires symfony/symfony ^3.2 -> satisfiable by symfony/symfony[3.2.x-dev, 3.3.x-dev, 3.4.x-dev, v3.2.0, v3.2.0-BETA1, v3.2.0-RC1, v3.2.0-RC2, v3.2.1, v3.2.10, v3.2.11, v3.2.12, v3.2.13, v3.2.14, v3.2.2, v3.2.3, v3.2.4, v3.2.5, v3.2.6, v3.2.7, v3.2.8, v3.2.9, v3.3.0, v3.3.0-BETA1, v3.3.0-RC1, v3.3.1, v3.3.10, v3.3.11, v3.3.12, v3.3.13, v3.3.14, v3.3.15, v3.3.16, v3.3.2, v3.3.3, v3.3.4, v3.3.5, v3.3.6, v3.3.7, v3.3.8, v3.3.9, v3.4.0, v3.4.0-BETA1, v3.4.0-BETA2, v3.4.0-BETA3, v3.4.0-BE

...

(Rest of it looks similar, redacted)

EDIT: Just realized this isn't very helpful. I tried this on a site with Sylius 1.0 already installed, and got lots of similar conflicts. I had to work through them for about 1-2 hours before I realized the entire plugin is broken due to #68 :(

[stefandoorn]

I'm running this one on 1.0.7 and that works for me. Not sure about Sylius v1 alpha, never used it. What is your minimum stability? I remember setting it to 'dev' once, not sure that still applies.

[stefandoorn]

How does your composer.json look in your last test?

[MichaelMackus]

Here's a working-ish snippet from my composer.json (although I was stopped in my tracks due to #68, unable to get this working):

        "sylius/sylius": "1.0.7",

         "symfony/symfony": "^3.3.13",
         "symfony-cmf/seo-bundle": "~2.0",
         "symfony-cmf/block-bundle": "^2.1@dev",
         "symfony-cmf/core-bundle": "~2.0",
         "symfony-cmf/content-bundle": "~2.0",
         "symfony-cmf/media-bundle": "dev-master",
         "symfony-cmf/menu-bundle": "^2.1@dev",
         "symfony-cmf/routing-bundle": "~2.0",
         "doctrine/phpcr-odm": "^2.0@dev",
         "doctrine/phpcr-bundle": "^2.0@dev",
         "jackalope/jackalope": "~1.3",
         "jackalope/jackalope-doctrine-dbal": "~1.3",
         "lakion/cms-plugin": "dev-master#6d4edcc"

[MichaelMackus]

NOTE: In order to get this working, I had to manually copy the phpcr-odm and phpcr-bundle from the composer.lock file in this repository, over to my composer.lock file. Otherwise, I'd get a strange error invalid reference to the PHPCR metadata XML driver class.

I think this repository just needs a better composer.json file specifying the exact tagged versions (not minimum version), since the updated ones do not work properly with this plugin and the current settings lead to conflicts without a composer.lock file.