无法将Composer要求解析为可安装的一组包

时间:2016-05-10 17:34:51

标签: composer-php symfony

我正在使用symfony3来构建一个Web应用程序,当我尝试安装几个外部包时,我得到了

  

您的要求无法解析为可安装的一组   包。

我尝试使用选项--ignore-platform-reqs,但同样的事情发生了。 这些捆绑仅适用于symfony2?我认为symfony3完全向后兼容? 作曲家是否有更多的配置才能进行安装?

PS:PHP 5.5.8

编辑:composer.json

{
  "name": "dell/.checkout",
  "license": "proprietary",
  "type": "project",
  "autoload": {
    "psr-4": {
      "": "src/"
    },
    "classmap": [
      "app/AppKernel.php",
      "app/AppCache.php"
    ]
  },
  "autoload-dev": {
    "psr-4": {
      "Tests\\": "tests/"
    }
  },
  "require": {
    "php": ">=5.5.9",
    "symfony/symfony": "3.0.*",
    "doctrine/orm": "^2.5",
    "doctrine/doctrine-bundle": "^1.6",
    "doctrine/doctrine-cache-bundle": "^1.2",
    "symfony/swiftmailer-bundle": "^2.3",
    "symfony/monolog-bundle": "^2.8",
    "sensio/distribution-bundle": "^5.0",
    "sensio/framework-extra-bundle": "^3.0.2",
    "incenteev/composer-parameter-handler": "^2.0",
    "symfony/assetic-bundle": "v2.8.0",
    "friendsofsymfony/jsrouting-bundle": "2.0.0-alpha1",
    "blackknight467/star-rating-bundle": "v2.0.1",
    "nomaya/social-bundle": "dev-master",
    "payum/payum-bundle": "2.0.1"
  },
  "require-dev": {
    "sensio/generator-bundle": "^3.0",
    "symfony/phpunit-bridge": "^3.0"
  },
  "scripts": {
    "post-install-cmd": [
      "Incenteev\\ParameterHandler\\ScriptHandler::buildParameters",
      "Sensio\\Bundle\\DistributionBundle\\Composer\\ScriptHandler::buildBootstrap",
      "Sensio\\Bundle\\DistributionBundle\\Composer\\ScriptHandler::clearCache",
      "Sensio\\Bundle\\DistributionBundle\\Composer\\ScriptHandler::installAssets",
      "Sensio\\Bundle\\DistributionBundle\\Composer\\ScriptHandler::installRequirementsFile",
      "Sensio\\Bundle\\DistributionBundle\\Composer\\ScriptHandler::prepareDeploymentTarget"
    ],
    "post-update-cmd": [
      "Incenteev\\ParameterHandler\\ScriptHandler::buildParameters",
      "Sensio\\Bundle\\DistributionBundle\\Composer\\ScriptHandler::buildBootstrap",
      "Sensio\\Bundle\\DistributionBundle\\Composer\\ScriptHandler::clearCache",
      "Sensio\\Bundle\\DistributionBundle\\Composer\\ScriptHandler::installAssets",
      "Sensio\\Bundle\\DistributionBundle\\Composer\\ScriptHandler::installRequirementsFile",
      "Sensio\\Bundle\\DistributionBundle\\Composer\\ScriptHandler::prepareDeploymentTarget"
    ]
  },
  "config": {
    "platform": {
      "php": "5.5.9"
    }
  },
  "extra": {
    "symfony-app-dir": "app",
    "symfony-bin-dir": "bin",
    "symfony-var-dir": "var",
    "symfony-web-dir": "web",
    "symfony-tests-dir": "tests",
    "symfony-assets-install": "relative",
    "incenteev-parameters": {
      "file": "app/config/parameters.yml"
    }
  }
}

1 个答案:

答案 0 :(得分:0)

根据this issue on Githubnomaya/social-bundle的所有者不打算支持Symfony 3,因此您可能会看到向后兼容性问题。可能会有更多,但这是我发现的第一个。

Symfony's Backwards Compatability Promise说:

  

确保项目顺利升级是我们的首要任务。   这就是为什么我们向所有未成年人承诺向后兼容(BC)的原因   Symfony发布。您可能将此策略视为语义   版本。简而言之,语义版本控制意味着只有主要版本   版本(例如2.0,3.0等)允许向后突破   兼容性即可。可能会引入次要版本(例如2.5,2.6等)   新功能,但必须这样做而不破坏现有的API   发布分支(前一个例子中的2.x)。