You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I may have found an issue with the displaying of the current installed version of a subdependency after downgrading it.
For example, when I downgrade the symfony-framework-bundle dependency from 2.8 to 2.3, the composer-versions-check display me this for the http-kernel sub-dependency :
symfony/http-kernel (v2.8.2) last version is v3.0.1
The dependecies are well displayed, but the sub-dependencies seems not to be handle well.
The text was updated successfully, but these errors were encountered:
The 2.3 version of symfony/framework-bundle requires php 5.3.3 and symfony/config component ~2.3 (which allows 2.8).
If we take a look at symfony/config component in 2.8 version, it requires php 5.3.9 which is not good at all if we use a server running php 5.3.3 (centOS 6 server for example).
If we launch a composer install with a PHP Client having PHP5.4 (YES it is completly dumb not to use the same php version in dev as in prod), the subdependencies will be installed with the 2.8version and then, a composer install will fail in production environment.
We need to add those lines in the composer.json in order to force the 2.3 version to be installed:
Hi,
I may have found an issue with the displaying of the current installed version of a subdependency after downgrading it.
For example, when I downgrade the
symfony-framework-bundle
dependency from 2.8 to 2.3, the composer-versions-check display me this for the http-kernel sub-dependency :The dependecies are well displayed, but the sub-dependencies seems not to be handle well.
The text was updated successfully, but these errors were encountered: