Error "No such remote 'composer'" when updating linked package

[gopi-ar]

Thanks for this package - really helpful for local dev!

Getting this error when updating linked packages (happens on both upgrades and downgrades):

- Upgrading [package] (v1.0.1 => v1.0.2): Checking out abc123 from cache
  Update failed (Failed to execute git remote set-url composer -- git@<ssh_hostname_alias>:<org>/<repo>.git
fatal: No such remote 'composer'
)
  Would you like to try reinstalling the package instead [yes]? 

Selecting "yes" works fine - reinstalls the version then relinks to local. Is this error expected behavior?

I'm on composer 2.8.x

[SanderSander]

@gopi-ar Hey thanks for reporting this issue.

This is not expected behavior, it should never crash with a fatal error, or interfere normal upgrade/downgrade behavior.

Could you provide a bit more information? How did you link the package, and how it's defined in your composer.json?
And what command did you ran when updating?

[gopi-ar]

How did you link the package

The custom package lives in the parent directory.
composer link ../package

how it's defined in your composer.json

Here's how the composer.json looks (package name etc changed to publish here). This is a private package that is included via composer's "repositories". I wonder if that's the reason for the error.

    "name": "org/project-that-uses-package",
    "require": {
        "org/package": "1.0.2"
    },
    "repositories": [{
        "type": "vcs",
        "url": "git@<sshalias or bitbucket.org>:org/package.git"
    }],
    "require-dev": {
        "sandersander/composer-link": "^0.4.1"
    },
    "config": {
        "allow-plugins": {
            "sandersander/composer-link": true
        }
    }
}

Detailed logs

root@server:/var/www/project# composer update org/package -vv
Loading composer repositories with package information
Reading composer.json of org/package (v1.0.0)
Importing tag v1.0.0 (1.0.0.0)
Reading composer.json of org/package (v1.0.1)
Importing tag v1.0.1 (1.0.1.0)
Reading composer.json of org/package (v1.0.2)
Importing tag v1.0.2 (1.0.2.0)
Reading composer.json of org/package (master)
Importing branch master (dev-master)
Updating dependencies
Dependency resolution completed in 0.000 seconds
Analyzed 140 packages to resolve dependencies
Analyzed 242 rules to resolve dependencies
Dependency resolution completed in 0.000 seconds
Lock file operations: 0 installs, 1 update, 0 removals
Updates: org/package:v1.0.2
- Upgrading org/package (v1.0.1 => v1.0.2) from vcs repo (git git@host:org/package-repo.git)
Writing lock file
Installing dependencies from lock file (including require-dev)
Package operations: 0 installs, 1 update, 0 removals
Updates: org/package:v1.0.2
- Syncing org/package (v1.0.2) into cache
- Upgrading org/package (v1.0.1 => v1.0.2): Checking out abc123d86eb63a743a4db17109514afe3fe24192 from cache
 Update failed (Failed to execute git remote set-url composer -- git@host:org/package-repo.git
fatal: No such remote 'composer'
)
 Would you like to try reinstalling the package instead [yes]?
- Removing org/package (v1.0.1)
- Installing org/package (v1.0.2): Cloning abc123d86eb63a743a4db17109514afe3fe24192 from cache
Generating autoload files
40 packages you are using are funding.
Use the `composer fund` command to find out more!
> post-update-cmd: ComposerLink\Plugin->linkLinkedPackages
- Removing org/package (v1.0.2)
- Installing org/package (dev-master): Symlinking from ../package-repo
Found 1 security vulnerability advisory affecting 1 package.
Run "composer audit" for a full list of advisories.

[SanderSander]

This is a private package that is included via composer's "repositories". I wonder if that's the reason for the error.

I think it's, what happens is that on the first install we have a package in /vendor/org/package which is a git repo.
After the install, the plugin symlinks to your development directory.

After the next update/downgrade composer tries to set the remote "composer" to an url, but the remote doesn't exists because it's the symlinked directory? But I'm not sure because I have a similar setup here and it works fine. The only difference is that I have the plugin installed globally.

I need to dive a bit deeper into it, but I think I have enough information to replicate this issue 👍🏻