Laravel 无法使用composer更新依赖项

Laravel 无法使用composer更新依赖项,laravel,composer-php,jwt,guzzle,laravel-socialite,Laravel,Composer Php,Jwt,Guzzle,Laravel Socialite,我试图通过composer在生产服务器上安装程序包tymon/jwt auth,在解决依赖关系时出现错误 我已成功地将其安装在本地vagrant环境中,但在生产服务器上时,会出现以下输出 Your requirements could not be resolved to an installable set of packages. Problem 1 - Conclusion: don't install laravel/socialite 3.0.x-dev - Co

我试图通过composer在生产服务器上安装程序包tymon/jwt auth,在解决依赖关系时出现错误

我已成功地将其安装在本地vagrant环境中,但在生产服务器上时,会出现以下输出

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

  Problem 1
    - Conclusion: don't install laravel/socialite 3.0.x-dev
    - Conclusion: remove guzzlehttp/guzzle 6.2.x-dev|install laravel/socialite 3.0.x-dev
    - laravel/socialite v2.0.0 requires guzzlehttp/guzzle ~4.0 -> satisfiable by guzzlehttp/guzzle[4.x-dev].
    - laravel/socialite v2.0.1 requires guzzlehttp/guzzle ~4.0|~5.0 -> satisfiable by guzzlehttp/guzzle[4.x-dev, 5.3.0, 5.3.1, 5.3.2, 5.3.3, 5.3.x-dev].
    - laravel/socialite v2.0.2 requires guzzlehttp/guzzle ~4.0|~5.0 -> satisfiable by guzzlehttp/guzzle[4.x-dev, 5.3.0, 5.3.1, 5.3.2, 5.3.3, 5.3.x-dev].
    - laravel/socialite v2.0.3 requires guzzlehttp/guzzle ~4.0|~5.0 -> satisfiable by guzzlehttp/guzzle[4.x-dev, 5.3.0, 5.3.1, 5.3.2, 5.3.3, 5.3.x-dev].
    - laravel/socialite v2.0.4 requires guzzlehttp/guzzle ~4.0|~5.0 -> satisfiable by guzzlehttp/guzzle[4.x-dev, 5.3.0, 5.3.1, 5.3.2, 5.3.3, 5.3.x-dev].
    - Can only install one of: guzzlehttp/guzzle[5.3.0, 6.2.x-dev].
    - Can only install one of: guzzlehttp/guzzle[5.3.1, 6.2.x-dev].
    - Can only install one of: guzzlehttp/guzzle[5.3.2, 6.2.x-dev].
    - Can only install one of: guzzlehttp/guzzle[5.3.3, 6.2.x-dev].
    - Can only install one of: guzzlehttp/guzzle[5.3.x-dev, 6.2.x-dev].
    - Can only install one of: guzzlehttp/guzzle[4.x-dev, 6.2.x-dev].
    - Installation request for guzzlehttp/guzzle (locked at 6.2.x-dev, required as ~5.3|~6.0) -> satisfiable by guzzlehttp/guzzle[6.2.x-dev].
    - Conclusion: remove laravel/socialite 3.0.x-dev|install laravel/socialite v2.0.0|install laravel/socialite v2.0.1|install laravel/socialite v2.0.2|install laravel/socialite v2.0.3|install laravel/socialite v2.0.4
    - Can only install one of: laravel/socialite[2.0.x-dev, 3.0.x-dev].
    - Can only install one of: laravel/socialite[v2.0.10, 3.0.x-dev].
    - Can only install one of: laravel/socialite[v2.0.11, 3.0.x-dev].
    - Can only install one of: laravel/socialite[v2.0.12, 3.0.x-dev].
    - Can only install one of: laravel/socialite[v2.0.13, 3.0.x-dev].
    - Can only install one of: laravel/socialite[v2.0.14, 3.0.x-dev].
    - Can only install one of: laravel/socialite[v2.0.15, 3.0.x-dev].
    - Can only install one of: laravel/socialite[v2.0.16, 3.0.x-dev].
    - Can only install one of: laravel/socialite[v2.0.17, 3.0.x-dev].
    - Can only install one of: laravel/socialite[v2.0.18, 3.0.x-dev].
    - Can only install one of: laravel/socialite[v2.0.19, 3.0.x-dev].
    - Can only install one of: laravel/socialite[v2.0.20, 3.0.x-dev].
    - Can only install one of: laravel/socialite[v2.0.21, 3.0.x-dev].
    - Can only install one of: laravel/socialite[v2.0.22, 3.0.x-dev].
    - Can only install one of: laravel/socialite[v2.0.5, 3.0.x-dev].
    - Can only install one of: laravel/socialite[v2.0.6, 3.0.x-dev].
    - Can only install one of: laravel/socialite[v2.0.7, 3.0.x-dev].
    - Can only install one of: laravel/socialite[v2.0.8, 3.0.x-dev].
    - Can only install one of: laravel/socialite[v2.0.9, 3.0.x-dev].
    - Installation request for laravel/socialite (locked at 3.0.x-dev, required as ^2.0@dev) -> satisfiable by laravel/socialite[3.0.x-dev].
    - Installation request for laravel/socialite ^2.0@dev -> satisfiable by laravel/socialite[2.0.x-dev, v2.0.0, v2.0.1, v2.0.10, v2.0.11, v2.0.12, v2.0.13, v2.0.14, v2.0.15, v2.0.16, v2.0.17, v2.0.18, v2.0.19, v2.0.2, v2.0.20, v2.0.21, v2.0.22, v2.0.3, v2.0.4, v2.0.5, v2.0.6, v2.0.7, v2.0.8, v2.0.9].
我在服务器上通过运行composer update和composer require tymon/jwt auth进行了尝试

如何开始解决这个问题

提前谢谢

PS:这是我的composer.json文件

{
    "name": "laravel/laravel",
    "description": "The Laravel Framework.",
    "keywords": ["framework", "laravel"],
    "license": "MIT",
    "type": "project",
    "minimum-stability": "dev",
    "repositories": [
        {
            "type": "git",
            "url": "https://github.com/cholung/laravel-model-builder.git"
        },
        {
            "type": "git",
            "url": "https://github.com/vorodevops/l5scaffold.git"
        },
        {
          "type": "vcs",
          "url": "https://github.com/alnutile/l5scaffold.git"
        }
    ],
    "require": {
        "php": ">=5.5.9",
        "laravel/framework": "5.1.*",
        "ramsey/uuid": "^3.2",
        "intervention/image": "^2.3",
        "guzzlehttp/guzzle": "~5.3|~6.0",
        "laravel/socialite": "^2.0@dev",
        "predis/predis": "^1.1@dev",
        "pda/pheanstalk": "~3.0",
        "xinax/laravel-gettext": "3.x",
        "laravelcollective/html": "5.1.*",
        "doctrine/dbal": "^2.5",
        "moltin/laravel-cart": "^5.0",
        "jenssegers/date": "^3.2",
        "barryvdh/laravel-dompdf": "0.6.*",
        "maatwebsite/excel": "~2.1.0",
        "jenssegers/agent": "^2.3",
        "yajra/laravel-datatables-oracle": "~6.0",
        "wisembly/elephant.io": "^3.1",
        "dimsav/laravel-translatable": "^6.0",
        "sammyk/laravel-facebook-sdk": "^3.0"
    },
    "require-dev": {
        "fzaninotto/faker": "~1.4",
        "mockery/mockery": "0.9.*",
        "phpunit/phpunit": "~4.0",
        "phpspec/phpspec": "~2.1",
        "jimbolino/laravel-model-builder" : "dev-master",
        "laralib/l5scaffold": "dev-viewonly",
        "barryvdh/laravel-debugbar": "^2.0"
    },
    "autoload": {
        "classmap": [
            "database"
        ],
        "psr-4": {
            "App\\": "app/",
            "Artvisual\\Tools\\": "packages/artvisual/tools/src",
            "Artvisual\\Tools\\Providers\\": "packages/artvisual/tools/src/Providers",
            "Artvisual\\Payment\\": "packages/artvisual/payment/src"
        }
    },
    "autoload-dev": {
        "classmap": [
            "tests/TestCase.php"
        ]
    },
    "scripts": {
        "post-install-cmd": [
            "php artisan clear-compiled",
            "php artisan optimize"
        ],
        "pre-update-cmd": [
        ],
        "post-update-cmd": [
            "php artisan clear-compiled",
            "php artisan optimize"
        ],
        "post-root-package-install": [
            "php -r \"copy('.env.example', '.env');\""
        ],
        "post-create-project-cmd": [
            "php artisan key:generate"
        ]
    },
    "config": {
        "preferred-install": "dist"
    }
}

万一有人还需要解决这个问题。在这里,它说你应该

  • composer require
    旧版本的
    guzzle http/guzzle
    ,例如
    composer require guzzle http/guzzle:^5.3.0
  • composer require
    您首先希望安装的软件包,例如
    composer require laravel/socialite
  • composer-remove
    使用
    composer-remove-guzzle http/guzzle

  • 我在要求jonasva/google trends依赖项时遇到了这个错误,这为我解决了这个问题。

    以防有人仍然需要解决这个问题。在这里,它说你应该

  • composer require
    旧版本的
    guzzle http/guzzle
    ,例如
    composer require guzzle http/guzzle:^5.3.0
  • composer require
    您首先希望安装的软件包,例如
    composer require laravel/socialite
  • composer-remove
    使用
    composer-remove-guzzle http/guzzle

  • 我在要求使用
    jonasva/googletrends
    依赖项时遇到了这个错误,这为我解决了这个问题。

    你看了吗?有没有特殊原因你不在本地更新
    composer.lock
    文件,然后只运行
    composer安装
    来准备你的生产环境?@xabbuh因为我已经接管了在整个项目中,我意识到开发它的团队只是在推动
    composer.json
    ,而不是
    composer.lock
    。事实上,
    composer.lock
    在本地和服务器中看起来非常不同。我担心,如果我从我当地的环境中推出
    composer.lock
    ,然后安装
    composer
    ,一些人会认为它将开始不起作用,而这个项目非常大,开始进行如此大的更改。事实上,我在服务器上执行的所有
    composer update
    命令都带有
    --dry run
    标志,只是为了知道将要发生什么。@Kevin是的,我执行了,但这对我不起作用。无论如何,谢谢。然后将composer.lock从prod环境带回dev,并将其推送到代码存储库。不幸的是,您需要重新开始开发环境,但这是唯一的保存方法。如果您不使用composer.lock,那么项目迟早会崩溃。您看了吗?是否有特殊原因您不在本地更新
    composer.lock
    文件,然后只运行
    composer install
    来准备您的生产环境?@xabbuh因为我已经接管了整个项目,我意识到开发它的团队只是在推
    composer.json
    ,而不是
    composer.lock
    。事实上,
    composer.lock
    在本地和服务器中看起来非常不同。我担心,如果我从我当地的环境中推出
    composer.lock
    ,然后安装
    composer
    ,一些人会认为它将开始不起作用,而这个项目非常大,开始进行如此大的更改。事实上,我在服务器上执行的所有
    composer update
    命令都带有
    --dry run
    标志,只是为了知道将要发生什么。@Kevin是的,我执行了,但这对我不起作用。无论如何,谢谢。然后将composer.lock从prod环境带回dev,并将其推送到代码存储库。不幸的是,您需要重新开始开发环境,但这是唯一的保存方法。如果不使用composer.lock,项目迟早会在prod上中断