Requiring a private git Bitbucket repository fails to find valid composer.json

[mcfdn]

I'm trying to reference a private git repository from Bitbucket in my project's composer.json:

{
    "require": {
        "vendor/my-private-package": "dev-master"
    },
    "repositories": [
        {
            "type": "git",
            "url": "git@bitbucket.org:vendor/my-private-package.git"
        }
    ]
}

The remote repository has the following composer.json:

{
    "name": "vendor/my-private-package",
    "autoload": {
        "psr-0": {
            "NS_": "src/"
        }
    }
}

I'm receiving the following error:

[Composer\Repository\InvalidRepositoryException]
No valid composer.json was found in any branch or tag of git@bitbucket.org:vendor/my-private-package.git, could not load a package from it.

Is this expected behavior? My understanding is that I should just be able to reference a remote git repository and have composer install it with or without a remote composer.json.

[Seldaek]

Can you run it with -v? then it should say why the branches/tags were ignored, it should help debugging this.

[mcfdn]

Ok I've discovered the issue, and it's a strange one. I had updated my windows registry to change directory and print out a message at command prompt startup.

Running composer update -v :

Skipped parsing master, ""master":composer.json" does not contain valid JSON
Parse error on line 1:
Autorun message
-^
Expected one of: 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '['

[Composer\Repository\InvalidRepositoryException]
No valid composer.json was found in any branch or tag of git@bitbucket.org:vendor/my-private-package.git, could not load a package from it.

It seems to be including that autorun message in the stream..

I've removed the registry entry and it seems to be working now. I'm not sure if this can be considered a bug as it's quite a weird case.

EDIT:

I just want to add that any registry entry (not just an echo) will cause the error I noted in the first comment. For example I have an entry that runs CD C:\ on startup and I'm now still receiving the error!

[Seldaek]

Yeah it's not really a composer issue it's just the way windows cmd works, if you have any autorun entry it messes things up for php run processes or at least the way we run them they go through a shell and that stuff gets executed. Autorun entries should really be silent.

[aldee07]

I know this is a bit old, but for some that might encounter this issue, this is how it works for me.

Clear the composer cache.

composer clearcache

Rerun the satis build script.

[hisenbergguj]

@aldee07 it doesnt work for me any otheridea?

can you post your private package JSON file?

[jUnG3]

@aldee07
Thx for the idea. I encountered the same problem and the composer clearcache command helped.

[bradleygreen]

'composer self-update' seems to have solved the problem for me. I did try 'composer clearcache' first, and also tried deleting C:\users\username\AppData\Local\Composer*.

The suggestions I found didn't seem to work for me, but updating my composer did. Best of luck to you all!