Can not composer install / update -> No version set (parsed as 1.0.0) #342
Comments
Try running |
Also, composer's package version resolution is somewhat non-deterministic. Try removing the vendor folder and composer.lock, then running the command again. |
@GrahamCampbell Thank you for quick reply Cleaning the cache did not fix, still the same error, here the directory after the error:
About the composer package version resolution, from my experience it is more like you need at least this version, but not this version exactly (this version is the one written in the composer.json), so I should be able to pickup a newer releaser with no problem. |
Also I try'ed with the last composer-1.2.4.phar, it return the same error. |
Please paste your composer.json file, and provide your php version. |
Do you have any globally installed packages that could be screwing with this? |
@GrahamCampbell
My php version:
No packages installed globally, I try to avoid that. |
No, what's your composer.json please. I don't need the one from this project copying/pasting here! |
Oh, are you trying to install the dependencies for this project itself? |
Travis itself demonstrates this is broken: https://travis-ci.org/sebastianbergmann/phpunit-mock-objects/builds. |
Interesting it worked fine on master, but failed for the tag just after. |
Yes
If travis agree it should be real, did you test it ?
I confirm it works well on the git tree !
So it seems to be a bug in the release tarball right ? |
Not really. It looks like a fundamental limitation of composer, due to cyclic dependencies. I don't think what you're experiencing can really be classed as bug in this project. |
I am not sure but the error did not occur on the git version, even if you checkout the related tag (3.4.3) so I guess, it could ether a diff in the tarball or a problem with composer, but it is interesting ! @GrahamCampbell Thank you for helping, I will check the diffs tomorrow but I suspect it is related to this error:
|
@sebastianbergmann @GrahamCampbell
It is mysterious to me and, I agree it seems to related to other thing (composer resolution or something else), but not the source, which is the same so it is likely not a bug, and it was not breaking my usage. As I was finding that, I just wanted to report to let you decide, if it is important or not. Thank you for the feedback. |
Someone might find this useful (although the issue is closed). Composer checks for environment variable The way I solved this is with |
Hi there,
I am working on phpunit to package it for gentoo (as a source package not a phar),
and during my test I try 'composer up' sometimes to check if I choose the right dependencies and version, because there are really old dependencies in composer.json.
In the case of phpunit-mock-object, when I 'composer up', I get this error:
I try'ed on different version, with the same error.
composer-1.2.2 / phpunit-5.7.3
The text was updated successfully, but these errors were encountered: