update-package-present-in-lock-but-not-in-remote.test

--TEST--
Update package which is in lock file but not in remote repo in the correct version should show this error correctly
--COMPOSER--
{
    "minimum-stability": "dev",
    "repositories": [
        {"type": "package", "package": [
            {"name": "main/dep", "version": "1.0.0", "require": {"locked/dep": "^2.1"}},
            {"name": "locked/dep", "version": "2.0.5"}
        ]}
    ],
    "require": {
        "main/dep": "*"
    }
}
--LOCK--
{
    "packages": [
        {
            "name": "main/dep", "version": "1.0.0",
            "require": {"locked/dep": "^2.1"},
            "type": "library"
        },
        {
            "name": "locked/dep", "version": "2.1.0",
            "type": "library"
        }
    ],
    "packages-dev": [],
    "aliases": [],
    "minimum-stability": "dev",
    "stability-flags": [],
    "prefer-stable": false,
    "prefer-lowest": false,
    "platform": [],
    "platform-dev": []
}
--RUN--
update main/dep --with-all-dependencies

--EXPECT-EXIT-CODE--
2

--EXPECT-OUTPUT--
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires main/dep * -> satisfiable by main/dep[1.0.0].
    - main/dep 1.0.0 requires locked/dep ^2.1 -> found locked/dep[2.0.5] but it does not match your constraint and is therefore not installable. Make sure you either fix the constraint or avoid updating this package to keep the one present in the lock file (locked/dep[2.1.0]).

--EXPECT--