Conflict with zend-diactoros about laminas-diactoros HOT 4 CLOSED

laminas-diactoros packages are marked to replace zend-diactoros packages; Composer does not install the original package if a package marked as a replacement is already installed. When testing prior to creating the Laminas packages, we were able to confirm this Composer behavior, which is why we chose to mark them as replacements.

So, now the question is: how did you get them to install side-by-side?

• What version of Composer did you use to install dependencies?
• What versions of (a) zend-diactoros, and (b) laminas-diactoros are installed?
• Are they being installed as project dependencies? If not, can you provide the results of composer why, using each package as an argument, please?

Perhaps that combination of information will allow us to attempt to reproduce the issue.

from laminas-diactoros.

Thanks a lot, that clued me in to the root cause. I think you are right that Composer should prevent this. But in our case we have symlinked a separate composer package (via a Composer path repo) into the first one. The linked package has its own vendor directory with the zend version, and somehow PHPUnit is seeing both vendor directories.

I'm still not exactly sure how to fix this, but it doesn't seem like a bug in this package. Cheers.

from laminas-diactoros.

For anyone else experiencing this (since I've received support requests), you should look through your vendor directory to see where the two sets of classes (zend and laminas) are coming from. They shouldn't both be present unless you've hacked Composer, are doing some funky autoloading, or using Composer path repositories as I mentioned above.

from laminas-diactoros.

@danepowell There was a bug recently fixed in composer 2.0 which also installed two versions of the same package. I've referenced it in composer/composer#8838 but couldn't find a way of abstracting my project to a "working" example to reproduce that behavior.

Luckily, another github user provided an example which produced exactly that behavior: composer/composer#8902

So, if you're already using composer v2 (which is not stable at this time btw), you might have a package installed which is meant to be replaced by another package (which is installed aswell).

composer fixed that issue with composer/composer#8916.

from laminas-diactoros.