eltrino / diamantedesk-application

DiamanteDesk
http://diamantedesk.com/
Other
118 stars 42 forks source link

Requires composer-plugin-api 1.0.0 -> no matching package found. #43

Open Impyus opened 7 years ago

Impyus commented 7 years ago

Hi

I have tried to set up DiamanteDesk many times now on both Centos 7 and Ubuntu 16.10.2 and following your documentation to the letter.

I always get hit with this error:

Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Installation request for eloquent/composer-npm-bridge 2.1.1 -> satisfiable by eloquent/composer-npm-bridge[2.1.1].
    - eloquent/composer-npm-bridge 2.1.1 requires composer-plugin-api 1.0.0 -> no matching package found.
  Problem 2
    - eloquent/composer-npm-bridge 2.1.1 requires composer-plugin-api 1.0.0 -> no matching package found.
    - diamante/front-bundle dev-master requires eloquent/composer-npm-bridge ~2 -> satisfiable by eloquent/composer-npm-bridge[2.1.1].
    - Installation request for diamante/front-bundle dev-master -> satisfiable by diamante/front-bundle[dev-master].

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.

Any ideas what I'm doing wrong and why this keeps happening?

Sully

odi-um commented 7 years ago

Hi Impyus,

What version you trying to install ? Have verified the last stable 2.0.3 and no such issue.

kafarr commented 7 years ago

This is a real problem. I'm using the latest version of composer and can reproduce it. Somewhere in the dependency tree there is a package that relies on composer-plugin-api 1.0.0

I haven't been able to find which package has this dependency. (annoyingly most dependency traversal tools require you to have a successful installation) The common solution to this problem is to update to the latest version of whatever package is causing the problem.

I believe updating to the latest version of composer should allow you to reproduce the issue.

odi-um commented 7 years ago

@kafarr i a;ways update my composer so it probably same as you have. Could you specify you composer version (hash in case it is dev version) so we will have same version ?

lghamie commented 7 years ago

@kafarr The problem for me was that I was following the instructions blindly. The instructions say that you should "clone -b 1.0 " which will download 1.0 branch and that branch has the broken dependency.

You should clone without the " -b 1.0" and then checkout the 2.0.3 tag with "git checkout tags/2.0.3" and then install deps with composer.

Hope that helps.