Closed PatrickRose closed 3 years ago
does it also happen if you use packagist rather than a custom repository ?
@stof no, just happens with our satis repo.
then maybe the Satis repo contains some corrupted metadata.
And this also means we cannot reproduce the issue to debug it.
The fact that satis has returned the wrong value is a bug with satis, but why is composer saying that my version is outdated when it isn't?
Well, I suspect that all releases of league/flysystem
newer than 1.0.70
have been removed from your Satis repo (which might not even be a bug in Satis but an effect of your config, as Satis allows to select a subset of the packagist versions when mirroring them).
regarding the fact that it says it is outdated, the composer outdated
command does not actually deal properly with the case where the installed version is newer than the latest available version in the repository (which should never happen anyway if you don't filter the repository after installing the package). It will consider it outdated when the versions are different.
Yeah this doesn't really seem like something we need to address.
My
composer.json
:Output of
composer diagnose
:When I run this command:
I get the following output:
And I expected this to happen:
league/flysystem
/phar-io/version
(and others) to not report as outdated, as the version I have installed is greater than the version composer is saying is the latest.The problem doesn't manifest itself if I do a bare install without our satis repo - in those cases composer will say that the latest version of
league/flysystem
is2.0.2
,phar-io/version
is up to date etc.