1
0
Fork 0

Update troubeshooting.md to suggest clearing Composer's cache.

pull/3095/head
Amy Boyd 2014-07-05 13:53:31 +01:00
parent 6f80b26c32
commit 126495e3c8
1 changed files with 6 additions and 0 deletions

View File

@ -21,6 +21,8 @@ This is a list of common pitfalls on using Composer, and how to avoid them.
possible interferences with existing vendor installations or `composer.lock` possible interferences with existing vendor installations or `composer.lock`
entries. entries.
5. Try clearing Composer's cache - `rm -r ~/.composer/cache`.
## Package not found ## Package not found
1. Double-check you **don't have typos** in your `composer.json` or repository 1. Double-check you **don't have typos** in your `composer.json` or repository
@ -38,6 +40,10 @@ This is a list of common pitfalls on using Composer, and how to avoid them.
your repository, especially when maintaining a third party fork and using your repository, especially when maintaining a third party fork and using
`replace`. `replace`.
5. If you are updating to a recently published version of a package, be aware that
Packagist has a delay of up to 10 minutes before new packages are added to it's
index.
## Package not found on travis-ci.org ## Package not found on travis-ci.org
1. Check the ["Package not found"](#package-not-found) item above. 1. Check the ["Package not found"](#package-not-found) item above.