search

zendframework / component-split

Script/utilities for splitting ZF2 components into their own repositories.
17 stars 7 forks source link

composer install on splitted "Stdlib" error #5

Closed samsonasik closed 9 years ago

samsonasik commented 9 years ago

I've just done a split, and try run composer install, and got error : 

$ composer install
Loading composer repositories with package information
Installing dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - zendframework/zend-serializer 2.3.x-dev requires zendframework/zend-json == 2.3.9999999.9999999-dev -> no matching package found.
    - zendframework/zend-serializer 2.3.x-dev requires zendframework/zend-json == 2.3.9999999.9999999-dev -> no matching package found.
    - Installation request for zendframework/zend-serializer == 2.3.9999999.9999999-dev -> satisfiable by zendframework/zend-serializer[2.3.x-dev].

Potential causes:
 - A typo in the package name
 - The package is not available in a stable-enough version according to your minimum-stability setting
   see <https://groups.google.com/d/topic/composer-dev/_g3ASeIFlrc/discussion> for more details.

Read <http://getcomposer.org/doc/articles/troubleshooting.md> for further common problems.

Splitted component pushed at https://github.com/samsonasik/zend-stdlib

samsonasik commented 9 years ago

seems self.version in composer.json need to be updated ?

weierophinney commented 9 years ago

No, it's fine. We don't have dev versions of the current components (as in dev-master, which is what 2.3.9999999.9999999-dev evaluates to); once all are split, that will resolve fine. We'll likely update the "self.version" stuff starting in the split components' master branches to use semantic versions, but not until after the split is completed.