but these conflict with your requirements or minimum-stability

后端 未结 6 883
梦如初夏
梦如初夏 2020-12-14 00:11

I am creating my own slackbot. I decided to use project as a library to help me.

https://github.com/sagebind/slack-client/issues?utf8=%E2%9C%93&q=stability

相关标签:
6条回答
  • 2020-12-14 00:40

    Add minimum-stability and prefer-stable to your composer.json (not composer.lock):

    {
        "name": "coderstephen/slack-client",
        "keywords": ["slack", "api", "realtime"],
        "license": "MIT",
        "description": "A better Slack client, with RTM API support",
        "authors": [{
            "name": "Stephen Coakley",
            "email": "me@stephencoakley.com"
        }],
        "require": {
            "php": ">=5.5",
            "devristo/phpws": "dev-master",
            "evenement/evenement": "2.0.*",
            "guzzlehttp/guzzle": "~6.0",
            "react/event-loop": "^0.4.1",
            "react/promise": "^2.2"
        },
        "require-dev": {
            "phpunit/phpunit": "~4.6",
            "fzaninotto/faker": "~1.4",
            "apigen/apigen": "^4.1"
        },
        "autoload": {
            "psr-4": {
                "Slack\\": "src"
            }
        },
        "autoload-dev": {
            "psr-4": {
                "Slack\\Tests\\": "tests"
            }
        },
        "minimum-stability": "dev",
        "prefer-stable": true
    }
    
    0 讨论(0)
  • 2020-12-14 00:42

    For others having the same issue, these changes are best done using composer itself instead of manually modifying the composer.json file. Just run the following commands in the console:

    $ composer config minimum-stability dev

    $ composer config prefer-stable true

    Now you can require and update the package:

    $ composer require --no-update "vendor/package-name:version"

    $ composer update

    Available options (in order of stability) are dev, alpha, beta, RC, and stable

    0 讨论(0)
  • 2020-12-14 00:50

    i had the error in a symfony4 project with own bundles.

    my-foo-bundle dev-master requires ramsey/uuid-doctrine ^1.5 -> satisfiable by ramsey/uuid-doctrine[1.5.0, 1.6.0] but these conflict with your requirements or minimum-stability.
    

    the solution, i search for "ramsey/uuid-doctrine" in my bundles and i found different requirements "ramsey/uuid-doctrine ^1.5" (in my-foo-bundle) and "ramsey/uuid-doctrine dev-master" (in my app-configuration). So i delete the requirement in the app/composer.json.

    This worked for me.

    0 讨论(0)
  • 2020-12-14 00:52

    You should never manually edit the composer.lock file - it is an automatically generated file.

    It looks like you've shown the composer.json file of the package you're trying to require rather than your own project's composer.json. The prefer-stable and minimum-stability properties should be added to your project root's composer.json file:

    {
      "name": "xFlare/slack-bot",
      "description": "xFlare's Slack bot project",
      "authors": [
        {
          "name": "xFlare"
        }
      ],
      "minimum-stability": "dev",
      "prefer-stable": true,
      "require": {
        "php": ">=5.5",
        "coderstephen/slack-client": "^0.3.0"
      }
    }
    
    0 讨论(0)
  • 2020-12-14 00:53

    You should add the minimum-stability in your composer.json not in the composer.lock. The option exists see https://getcomposer.org/doc/04-schema.md#minimum-stability

    0 讨论(0)
  • 2020-12-14 00:57

    Usually, this issue has nothing to do directly with minimum-stability or prefer-stable option, but the case is just that you already use some library directly or indirectly, that is needed in another library you use but in a higher version.

    My case: I installed Codeception, but had required PHPUnit 4, but Codeception needed at least phpunit 6 - up to 8. Whereas phpunit 6 only supported php7.0 , so I had to explicitly increase my used version of phpunit from 4 to 6, so that the library codeception could work with it.

    You might ask if it might affect your project which already relies on the lower version of the library, perhaps there could be some breaking change, but I don't know if there could be some workaround for using one version for dependency and another version for own project.

    Edit: I also had to issue remove composer command for phpunit, otherwise I was not able to increase my phpunit version directly

    0 讨论(0)
提交回复
热议问题