--TEST-- Packages found in a higher priority repository take precedence even if they are not found in the requested version --COMPOSER-- { "repositories": [ { "type": "package", "package": [ { "name": "foo/a", "version": "1.0.0" } ] }, { "type": "package", "package": [ { "name": "foo/a", "version": "2.0.0" } ] } ], "require": { "foo/a": "2.*" } } --RUN-- update --EXPECT-OUTPUT-- Loading composer repositories with package information Updating dependencies Your requirements could not be resolved to an installable set of packages. Problem 1 - The requested package foo/a 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 for more details. - It's a private package and you forgot to add a custom repository to find it Read for further common problems. --EXPECT-- --EXPECT-EXIT-CODE-- 2