search

claroline / Claroline

Learning management system
https://www.claroline.com
Other
315 stars 188 forks source link

Composer update errors #308

Closed maxailloud closed 11 years ago

maxailloud commented 11 years ago

This morning I tried to update my vendor with composer update but I get some errors:

Problem 1
    - The requested package xaguilars/bootstrap-colorpicker could not be found in any version, there may be a typo in the package name.
  Problem 2
    - The requested package besimple/sso-auth-bundle could not be found in any version, there may be a typo in the package name.
  Problem 3
    - The requested package hamcrest/hamcrest could not be found in any version, there may be a typo in the package name.
  Problem 4
    - Installation request for jms/twig-js-bundle dev-master -> satisfiable by jms/twig-js-bundle[dev-master].
    - jms/twig-js-bundle dev-master requires jms/twig-js dev-master -> no matching package found.
  Problem 5
    - Installation request for claroline/installation-bundle ~2.0 -> satisfiable by claroline/installation-bundle[2.0.0].
    - claroline/installation-bundle 2.0.0 requires doctrine/data-fixtures dev-master -> no matching package found.
  Problem 6
    - Installation request for claroline/migration-bundle ~1.0 -> satisfiable by claroline/migration-bundle[1.0.0].
    - claroline/migration-bundle 1.0.0 requires doctrine/migrations dev-master -> no matching package found.
  Problem 7
    - claroline/installation-bundle 2.0.0 requires doctrine/data-fixtures dev-master -> no matching package found.
    - claroline/core-installer 1.0.0 requires claroline/installation-bundle ~2.0 -> satisfiable by claroline/installation-bundle[2.0.0].
    - Installation request for claroline/core-installer ~1.0 -> satisfiable by claroline/core-installer[1.0.0].

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.

Maybe it's a composer issue, too many repositories in error is very strange, but I wanted to know if it's only for me or not.

stefk commented 11 years ago

I can't reproduce it. Updates works here on several installations. And yes, some errors in the log are very strange. Have you tried emptying composer's cache (-> ~/.composer/cache) ?

maxailloud commented 11 years ago

Haha I made a huge mistake.

I just launch the command in my CoreBundle directory.

Shame on me^^