neoxygen / neo4j-neoclient

Simple PHP HttpClient for the Neo4j ReST API with Multi DB Support
MIT License
121 stars 138 forks source link

PHP 5.4 composer build error due to Symfony/Config #29

Closed markharding closed 9 years ago

markharding commented 9 years ago

Composer output

 Problem 1

- Installation request for symfony/filesystem 3.0.x-dev -> satisfiable by symfony/filesystem[3.0.x-dev].

- symfony/filesystem 3.0.x-dev requires php >=5.5.9 -> no matching package found.

Problem 2

- Installation request for symfony/filesystem dev-master -> satisfiable by symfony/filesystem[dev-master].

- symfony/filesystem dev-master requires php >=5.5.9 -> no matching package found.

Problem 3

- symfony/filesystem 3.0.x-dev requires php >=5.5.9 -> no matching package found.

- symfony/config 2.7.x-dev requires symfony/filesystem ~2.3|~3.0.0 -> satisfiable by symfony/filesystem[3.0.x-dev].

- Installation request for symfony/config 2.7.x-dev -> satisfiable by symfony/config[2.7.x-dev].
ikwattro commented 9 years ago

I guess you have "minimum-stability":"dev" in your composer.json ?

Running composer install with a stable config does not throw any errors :

{
    "name": "root/testclient",
    "require": {
        "neoxygen/neoclient": "~2.1"
    },
    "authors": [
        {
            "name": "Christophe Willemsen",
            "email": "willemsen.christophe@gmail.com"
        }
    ]
}

Do you confirm generation [yes]?
airbook:testclient ikwattro$ ls
composer.json
airbook:testclient ikwattro$ composer install
Loading composer repositories with package information
Installing dependencies (including require-dev)
  - Installing psr/log (1.0.0)
    Loading from cache

  - Installing monolog/monolog (1.12.0)
    Loading from cache

  - Installing guzzlehttp/streams (2.1.0)
    Loading from cache

  - Installing guzzlehttp/guzzle (4.2.3)
    Loading from cache

  - Installing symfony/event-dispatcher (v2.6.3)
    Loading from cache

  - Installing symfony/dependency-injection (v2.6.3)
    Loading from cache

  - Installing symfony/filesystem (v2.6.3)
    Loading from cache

  - Installing symfony/config (v2.6.3)
    Loading from cache

  - Installing symfony/yaml (v2.6.3)
    Loading from cache

  - Installing symfony/console (v2.6.3)
    Loading from cache

  - Installing neoxygen/neoclient (2.1.0)
    Downloading: 100%

monolog/monolog suggests installing graylog2/gelf-php (Allow sending log messages to a GrayLog2 server)
monolog/monolog suggests installing raven/raven (Allow sending log messages to a Sentry server)
monolog/monolog suggests installing doctrine/couchdb (Allow sending log messages to a CouchDB server)
monolog/monolog suggests installing ruflin/elastica (Allow sending log messages to an Elastic Search server)
monolog/monolog suggests installing videlalvaro/php-amqplib (Allow sending log messages to an AMQP server using php-amqplib)
monolog/monolog suggests installing ext-amqp (Allow sending log messages to an AMQP server (1.0+ required))
monolog/monolog suggests installing aws/aws-sdk-php (Allow sending log messages to AWS services like DynamoDB)
monolog/monolog suggests installing rollbar/rollbar (Allow sending log messages to Rollbar)
symfony/event-dispatcher suggests installing symfony/http-kernel ()
symfony/dependency-injection suggests installing symfony/proxy-manager-bridge (Generate service proxies to lazy load them)
symfony/console suggests installing symfony/process ()
Writing lock file
Generating autoload files
markharding commented 9 years ago

Yes, thats correct. Some people need to require dev though.

ikwattro commented 9 years ago

Do you require ~2.1 or 2.1@dev ?

ikwattro commented 9 years ago

Having minimum stability to dev in your root package can lead to this kind of problems. If you need to have dev versions of other libraries it is better to put a `"otherpackage/otherlibrary":"1.0@dev" to those you want to have in a dev version.

This link can maybe help you : https://igor.io/2013/02/07/composer-stability-flags.html