I am trying to install phpdox through composer.
"require": {
"phploc/phploc": "2.0.6",
"phpunit/phpunit": "4.2.4",
"pdepend/pdepend": "2.0.0",
"phpmd/phpmd": "2.0.0",
"squizlabs/php_codesniffer": "2.0.0a2",
"sebastian/phpcpd": "2.0.*#dev",
"theseer/phpdox": "0.6.6.1"
}
Which produces the following:
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Installation request for theseer/phpdox 0.6.6.1 -> satisfiable by theseer/phpdox[0.6.6.1].
- theseer/phpdox 0.6.6.1 requires nikic/php-parser >=1.0.0 -> no matching package found.
Potential causes:
- A typo in the package name
- The package is not available in a stable-enough version according to your minimum-stability setting
However, on the packagist website it says that phpdox has a dependency nikic/php-parser: >=1.0.0 which does not exist.
How do I resolve that?
The package nikic/php-parser has only been tagged as a beta version 1.0, not a stable release.
theseer/phpdox does require that 1.0.0 version, however it has set minimum-stability:dev and prefer-stable:true in it's own composer.json. These settings can only be defined in the root composer.json.
Two ways to fix it:
Require the needed beta version of that package yourself: composer require nikic/php-parser:~1.0#beta would do it.
Also set the settings for minimum stability to at least "beta" and add the prefer-stable flag to avoid getting ALL packages in beta stability.
Reading the installation instructions I get the idea that you are not supposed to require this tool directly via Composer. I can't see a reason why not to do it, but this probably hasn't been anticipated. So optional step 3: Open a ticket on Github to get this issue fixed.
Related
I am trying to download mail_mime through composer but I got this error as illustrated below.
On window command line
C:\xampp\htdocs\google>composer install
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- The requested package pear/mail_mime dev-master exists as pear/mail_mime[1
.10.0, 1.10.1, 1.10.2, 1.8.9, 1.9.0] but these are rejected by your
constraint.
Below is a capture of my composer.json file.
So what is wrong ?
In your composer.json try changining
"pear/mail_mime":"dev-master"
to a stable release for instance 1.10.2 as shown below.
"pear/mail_mime" : "1.10.2"
You should use a specific ( tagged stable at best ) version wherever possible.
Here's more information on how versioning and constraint works in composer.
Does anyone installed Microsoft Azure Client Library to a Laravel 5 project with composer on an Ubuntu server?
When I try to install with Composer (command: composer require microsoft/windowsazure), I got the next error:
Using version ^0.4.1 for microsoft/windowsazure
./composer.json has been updated
> php artisan clear-compiled
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Installation request for microsoft/windowsazure ^0.4.1 -> satisfiable by microsoft/windowsazure[v0.4.1].
- microsoft/windowsazure v0.4.1 requires pear-pear2.php.net/http_request2 * -> no matching package found.
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://getcomposer.org/doc/04-schema.md#minimum-stability> for more details.
Read <https://getcomposer.org/doc/articles/troubleshooting.md> for further common problems.
Installation failed, reverting ./composer.json to its original content.
Does anyone know what am I doing wrong?
Thanks for the help.
The problem was solved by modifying the config of the composer, by setting the secure-http to false
"config": {
"secure-http": "false"
}
I have own package at github I created tag with name: "1.0.0".
composer.json in this tag don not have "minimum-stability" property (I tried with "minimum-stability": "dev" and "minimum-stability": "stable") but same error appears.
Error that I get is:
Your requirements could not be resolved to an installable set of packages.
Problem 1
- The requested package am2studio/laravel-table-sorter 1.* could not be found.
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://getcomposer.org/doc/04-schema.md#minimum-stability> for more details.
Read <https://getcomposer.org/doc/articles/troubleshooting.md> for further common problems.
I am trying to install package with
"comp-x/package-x": "1.*"
in composer and this error appears, with:
"comp-x/package-x": "dev-master"
everything is fine, and composer installs my package. Do you know what is problem here ?
I copied and pasted what was recommended I use from a thread on so.
Am I using a typo?
{
"require" : {
"facebook/php-sdk-v4" : "4.0.*",
"league/oauth2-client": "1.10"
}
}
Here's the full error message I get from composer:
/home/wiseman/public_html$ composer update Loading composer
repositories with package information Updating dependencies (including
require-dev) Your requirements could not be resolved to an installable
set of packages.
Problem 1
- The requested package league/oauth2-client could not be found in any version, there may be a typo in the package name.
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.
If Composer states that a package cannot be found, you have to go to packagist.org, type the package name into the big search field and see what you get.
In this particular case, the highest version released is 1.1.0, so you are missing one dot - or the source you copied it from.
I have a project with multiple packages
Each package is in a private git repository.
Some of the packages have dependencies of each other.
You can check here how my satis http://codepen.io/anon/pen/wBOEQW page looks like.
Now if I clone the project-xpto/core, and run a composer update i get this:
➜ php-core git:(master) composer update
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Installation request for project-xpto/event dev-master -> satisfiable by project-xpto/event[dev-master].
- project-xpto/event dev-master requires project-xpto/activity-streams dev-master -> no matching package found.
Problem 2
- Installation request for project-xpto/tool dev-master -> satisfiable by project-xpto/tool[dev-master].
- project-xpto/tool dev-master requires project-xpto/activity-streams dev-master -> no matching package found.
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.
satis.json => http://pastie.org/private/s0e2rxtnvpv9g7rpp415a
composer.json xpto-core => http://pastie.org/10062586
composer.json xpto-event => http://pastie.org/private/stxe2sbwpja8088knrldq
composer.json xpto-tool =>
http://pastie.org/private/11o9wv94kvfprl5wjfibrq
composer.json
xpto-activity-streams =>
http://pastie.org/private/plieipe2gco1yt4gs0jxg
Isn't suppose to satis resolve all dependencies and all work fine?
What i'm doing wrong?
If you need anything else, just ask i will update here.
Please give this a try:
add "minimum-stability": "dev" to the composer.json of project-xpto/core.
You require a lot of dev-master stability packages, but the default minimum-stability is stable. So they are not resolved to a stable set. You need to lower stability for all packages to dev by setting the above directive in your main projects composer.json.
Alternatively you could use dev-master#dev to lower stability on a specific package. But here it's quite a number of packages, so i would suggest to set minimum-stability dev for the whole project.
You can combine "minimum-stability dev" with "prefer-stable true".
This tells Composer to resolve to stable versions AND ONLY if stable could not be resolved, use a dev dependency. This setting is a good way in the starting phase of a private project, where packages start to grow out of "dev-master" and into "stable versions".
"minimum-stability": "dev",
"prefer-stable" : true