The release of Symfony 2.1.0 messed up everything, but I have no clue how to fix it :(

[fabpot]

I quite don't understand what's going on, but the current state of the Symfony packages is broken.

The simplest example is Silex:

• clone fabpot/silex
• run composer.phar update --dev
• packages from the require section are installed, but the require-dev packages cannot be resolved as a set of installable packages.

Now

• move all packages from the require-dev section to the require section
• run composer.phar update --dev
• everything is installed as expected.

I'm lost.

[stof]

@fabpot this is because the dependencies between the different Symfony component are very strict: they force using self.version.
But the initial install selects the stable 2.1.0 tag for some components but chooses 2.1.x-dev for HttpKernel. This breaks things later as symfony/security depends on both HttpKernel and HttpFoundation which have been installed with different versions.

[fabpot]

@stof: So, changing all self.version to 2.1.* would fix the issue?

[naderman]

@fabpot Yes that should do the job.

[Seldaek]

Only in the require but not in the replace of the main package though I'd say.